-
Bug
-
Resolution: Done
-
Major
-
JBossAS-4.2.2.GA
-
None
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"
- blocks
-
JBAS-7195 On executing readonly query, WrappedConnection.checkTransactionStatus throws exception when transaction is marked for roll back
-
- Closed
-
- incorporates
-
-
- Resolved
-
-
JBAS-5278 Need to check transaction status on SQL operations
-
- Closed
-
- is related to
-
JBAS-5083 Add the transaction active check to the jdbc resource adapter
-
- Closed
-
