You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2010/05/10 21:08:31 UTC

[jira] Commented: (DERBY-4343) ASSERT FAILED calling setTransactionIsolation checking isolation_ == level on pooled connection

    [ https://issues.apache.org/jira/browse/DERBY-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865870#action_12865870 ] 

Kathey Marsden commented on DERBY-4343:
---------------------------------------

Lily, thank you for the patch, but I tried it on 10.5 and it passes there.  Do you know why?


> ASSERT FAILED calling setTransactionIsolation checking isolation_ == level   on  pooled connection
> --------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4343
>                 URL: https://issues.apache.org/jira/browse/DERBY-4343
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.6.1.0
>            Reporter: Kathey Marsden
>            Assignee: Lily Wei
>            Priority: Minor
>         Attachments: _cpds_0, DERBY-4343-2-testcase.diff, DERBY-4343-testcase.diff, TestConnReuse.java, TestConnReuse.java
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.