|Anonymous | Login | Signup for a new account||10-14-2019 18:28 PDT|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Simple Details [ Jump to Notes ]||[ View Advanced ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0004663||[Resin]||minor||always||07-08-11 13:47||10-04-11 14:59|
|Summary||0004663: Oracle rollback connection pool issue|
Two setting for connection. commit and autocomit.
If we we close a connection which returns it to the pool.
It seems like , it is always doing a rollback. This causes resource issues on our Oracle boxes.
We do a commit, We do a close, then Resin does a rollback if it is not in autocommit. The workaround is he puts autocommit on. This happens with Oracle.
PostgreSQL ignores the rollback if no updates in progress.
The problem is with Oracle only because of the resource hit as Oracle tries to do a real rollback even if there were no changes.
|07-08-11 13:47||rickHigh||New Issue|
|09-01-11 11:52||ferg||Project||Quercus => Resin|
|10-04-11 14:59||ferg||Note Added: 0005534|
|10-04-11 14:59||ferg||Assigned To||=> ferg|
|10-04-11 14:59||ferg||Status||new => closed|
|10-04-11 14:59||ferg||Resolution||open => fixed|
|10-04-11 14:59||ferg||Fixed in Version||=> 4.0.24|
|10-04-11 14:59||ferg||Description Updated|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
30 total queries executed.|
26 unique queries executed.