[
http://jira.jboss.com/jira/browse/JBAS-5080?page=all ]
Dimitris Andreadis updated JBAS-5080:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
(was: JBossAS-5.0.0.Beta3)
(was: JBossAS-4.2.3.GA)
Moving to CR1. If there is a problem with this, please contact me.
Need to check transaction status on SQL operations
--------------------------------------------------
Key: JBAS-5080
URL:
http://jira.jboss.com/jira/browse/JBAS-5080
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.2.GA
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.CR1
In 4.2.x the transaction timeout rollsback the transaction rather than marking it
rollback only.
This means that for the local transaction datasource the connection has effectively moved
onto the next
transaction.
Actual code:
Connection c = datasource.getConnection();
// tx timeout here
Statement s = createStatement();
s.executeUpdate(); // should not work
Actual Code executed in 4.0.x
Connection c = pool.getConnection();
// tx timeout here
transaction.setRollbackOnly();
Statement s = createStatement();
s.executeUpdate();
tx.rollback(); // Rollsback the update
Actual Code executed in 4.2.x
Connection c = pool.getConnection();
// tx timeout here
transaction.rollback();
Statement s = createStatement();
s.executeUpdate(); // happens "in the next local transaction"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira