|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4926 | feature | always | 01-18-12 12:34 | 04-10-12 18:55 | |
|
|
|||||
| Reporter: | cowan | Platform: | |||
| Assigned To: | alex | OS: | |||
| Priority: | high | OS Version: | |||
| Status: | closed | Product Version: | 3.1.12 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.13 | ||
|
|
|||||
| Summary: | 0004926: Database commit/rollback on max-active-time timeout | ||||
| Description: |
When a Connection is over max-active-time, the Connection is closed without Commit or RollBack. Therefore Connection.Close is dependent on the specification of JDBC. In case of Oracle, it is Commit. If you can, I want Resin to change like below. Resin does Commit or RollBack before Connection.close depended on Connection#getAutoCommit(). In other words, in com.caucho.sql.ManagedConnectionImpl#destroy(), 1. check Connection.getAutoCommit() 2. do commit or rollback 3. PoolConnection#close() and Connection#close() |
||||
| Steps To Reproduce: | |||||
| Additional Information: |
Rep by T. Fukuda Customer requests change in Resin 3.1.x |
||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||