[DERBY-1004] Client should not require user to rollback the active transaction before call to PooledConnection.getConnection()

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.1.3.1, 10.2.1.6
• Fix Version/s: 10.1.3.1, 10.2.1.6
• Component/s: Network Client
• Assignee: David Van Couvering
• Reporter: Katherine Marsden
• Created: 18/Feb/06 09:14
• Updated: 01/Jul/06 07:41
• Resolved: 09/Jun/06 04:29

Description

For a PooledConnection.getConnection() the connection gets closed.
Embedded automatically rolls back any activity on the connection.
Client requires the user to rollback and gives an SQLException
java.sql.Connection.close() requested while a transaction is in progress

The test jdbcapi/checkDataSource.java shows this bug. A boolean needRoolbackBeforePCGetConnection has been added to the test and explicit rollback has been added to the test to get it to run with client.

To reproduce take out instances of the explicit rollback for client from the test e.g.

if (needRollbackBeforePCGetConnection)
c1.rollback();