db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4343) ASSERT FAILED calling setTransactionIsolation checking isolation_ == level on pooled connection
Date Thu, 06 May 2010 06:31:48 GMT

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

Lily Wei updated DERBY-4343:

    Attachment: DERBY-4343-testcase.diff

With fix for DERBY-4314, this issue has been resolved also.
I am adding test case with four connections on ClientConnectionPoolDataSource to J2EEDataSource
Test test. From testing structure point of view, it is easier to add to J2EEDataSourceTest
instead of setTransactionIsolationTest.
The case where we execute a statement in local transaction within global transaction is also
added. Thx, Lily

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

View raw message