[ https://issues.apache.org/jira/browse/DERBY-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581862#action_12581862 ]
Knut Anders Hatlen commented on DERBY-3379: ------------------------------------------- J2EEDataSourceTest ran cleanly in my environment, and testPooledReuseOnClose was invoked twice (embedded and client). > "No Current connection" on PooledConnection.getConnection() if pooled > connection is reused during connectionClosed processing > ----------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-3379 > URL: https://issues.apache.org/jira/browse/DERBY-3379 > Project: Derby > Issue Type: Bug > Components: Network Client > Affects Versions: 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 > Reporter: Kathey Marsden > Assignee: Kristian Waagan > Attachments: derby-3379-1a-enforce_no_chaining.diff, > derby-3379-1a-enforce_no_chaining.diff, > derby-3379-1a-enforce_no_chaining.stat, > derby-3379-1a-enforce_no_chaining.stat, > derby-3379-1b-enforce_no_chaining.diff, > derby-3379-1c-enforce_no_chaining.diff, > derby-3379-1c-enforce_no_chaining.stat, > derby-3379-2a-comment_and_JavaDoc.diff, > derby-3379-3a-minimal_fix_and_test_enabling.diff > > > 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. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.