[DERBY-4343] ASSERT FAILED calling setTransactionIsolation checking isolation_ == level on pooled connection

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.5.3.1
• Fix Version/s: 10.7.1.1
• Component/s: JDBC, Network Client
• Labels: derby_backport_reject_10_5 derby_backport_reject_10_6
• Issue & fix info: High Value Fix, Newcomer, Patch Available, Repro attached
• Assignee: Lily Wei
• Reporter: Katherine Marsden
• Created: 07/Aug/09 00:16
• Updated: 25/Aug/11 22:20
• Resolved: 25/Aug/11 22:20

Description

For DERBY-4314, I thought I would do a little testing to understand the server round trips in various scenarios for pooled connections. So I wrote the small attached program ConnReuse.java and hit this assertion in client:

Exception in thread "main" org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED
at org.apache.derby.shared.common.sanity.SanityManager.ASSERT(SanityManager.java:98)
at org.apache.derby.client.am.Connection.setTransactionIsolationX(Connection.java:987)
at org.apache.derby.client.am.Connection.setTransactionIsolation(Connection.java:915)
at org.apache.derby.client.am.LogicalConnection.setTransactionIsolation(LogicalConnection.java:253)
at TestConnReuse.main(TestConnReuse.java:32)
---------------

To run the program on trunk:
java org.apache.derby.drda.NetworkServerControl start
java TestConnReuse.

This needs more investigation, but I thought I would go ahead and log the bug. I tried this only on trunk. I have not yet

• Tried it on the branches.
• Tried it with Lily's DERBY-4314 patch.
• Tried it with embedded.
• Tried actually doing something with the prior logical connection which might be related.

Issue Links

• relates to: DERBY-4314 With derby client setTransactionIsolation executes and commits even if isolation has not changed