Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <3021203.249671278543652394.JavaMail.jira@thor>
Date: Wed, 7 Jul 2010 19:00:52 -0400 (EDT)
From: "Mike Matrigali (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4343) ASSERT FAILED calling
 setTransactionIsolation checking isolation_ == level   on  pooled
 connection
In-Reply-To: <543555074.1249604174777.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mike Matrigali updated DERBY-4343:
----------------------------------


this looks like just a test for a change that is not being backported, so probably should not be backported.


> 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.5.3.1
>            Reporter: Kathey Marsden
>            Assignee: Lily Wei
>            Priority: Minor
>             Fix For: 10.7.0.0
>
>         Attachments: _cpds_0, DERBY-4343-2-testcase.diff, DERBY-4343-3-testcase.diff, DERBY-4343-4-trunk.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.