Anonymous | Login | Signup for a new account | 12-17-2024 10:44 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ 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 | ||||
Reporter | rickHigh | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 4.0.24 | Product Version | |||||
Product Build | |||||||||
Summary | 0004663: Oracle rollback connection pool issue | ||||||||
Description |
From client.... 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. |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
30 total queries executed. 26 unique queries executed. |