[DERBY-3379] "No Current connection" on PooledConnection.getConnection() if pooled connection is reused during connectionClosed processing

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1
• Fix Version/s: 10.3.3.0, 10.4.1.3, 10.5.1.1
• Component/s: Network Client
• Assignee: Kristian Waagan
• Reporter: Katherine Marsden
• Created: 01/Feb/08 19:52
• Updated: 04/May/09 18:22
• Resolved: 31/Mar/08 09:51

Description

This is the client version of bug DERBY-2142. It can be reproduced by enabling the test, DataSourceTest.testPooledReuseOnClose() for client. I am opening a new issue for client as the embedded fix was backported to 10.1 and I am guessing the client fix won't be backported that far. Better to keep it as a separate issue.

Issue Links

• depends upon: DERBY-3421 Remove unused code for caching of connect bytes
• is related to: DERBY-2142 NullPointerException while using XAConnection/PooledConnection in a heavily contended multithreaded scenario