|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4663 | minor | always | 07-08-11 13:47 | 10-04-11 14:59 | |
|
|
|||||
| Reporter: | rickHigh | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.24 | ||
|
|
|||||
| 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: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||