db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3379) "No Current connection" on PooledConnection.getConnection() if pooled connection is reused during connectionClosed processing
Date Mon, 17 Mar 2008 15:43:24 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan updated DERBY-3379:
-----------------------------------

    Attachment: derby-3379-3a-minimal_fix_and_test_enabling.diff

'derby-3379-3a-minimal_fix_and_test_enabling.diff' is a minimal fix (basically a one-liner)
and it also enables the regression test that was commented out.

Seems some other change has somehow changed the characteristics of the problem. Earlier I
got a hang with only the fix for ClientPooledConnection. Now it works fine. Without the CPC-fix,
I get a "No current connection".
It is not clear to me what has caused the change. I have run the test both with and without
statement pooling enabled, and also both with trunk and the 10.4 branch.

Can someone please try this patch out and verify that jdbcapi.J2EEDataSourceTest runs cleanly,
and that the repro is actually run?
I have started the full regression suite, and will report back with the results tomorrow.
If I get the cycles, I'll try to hunt down the commit that made the hang go away. Would be
nice to know...

> "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.


Mime
View raw message