0004926: Database commit/rollback on max-active-time timeout

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0004926

[Resin]

feature

always

01-18-12 12:34

04-10-12 18:55

Reporter

cowan

View Status

public

Assigned To

alex

Priority

high

Resolution

fixed

Status

closed

Product Version

3.1.12

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()

Additional Information

Rep by T. Fukuda

Customer requests change in Resin 3.1.x

Attached Files

Relationships

Notes
(0005741) alex 04-10-12 18:55	server/152n server/152o

Issue History
Date Modified	Username	Field	Change
01-18-12 12:34	cowan	New Issue
04-10-12 18:55	alex	Status	new => assigned
04-10-12 18:55	alex	Assigned To	=> alex
04-10-12 18:55	alex	Status	assigned => closed
04-10-12 18:55	alex	Note Added: 0005741
04-10-12 18:55	alex	Resolution	open => fixed
04-10-12 18:55	alex	Fixed in Version	=> 3.1.13

Mantis 1.0.0rc3[^]

29 total queries executed.
26 unique queries executed.