[
https://issues.apache.org/jira/browse/DERBY-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-4343:
----------------------------
Attachment: TestConnReuse.java
_cpds_0
Thank to Kathey, I turn the tracing with
ClientConnectionPoolDataSource.setTraceDirectory("client"); And, the trace file
is attached. The test first call setTransactionIsolation with
TRANSACTION_READ_COMMITTED. On second connection, the test call
setTransactionIsolation with TRANSACTION_READ_COMMITTED. On the third
connection, test call setTransactionIsolation with TRANSACTION_READ_UNCOMMITTED.
>From tracing, I see the test go through setTransactionIsolation(2) call and
>then go to getTransactionIsolationX. On second connection, the test call
>setTrasactionIsolation(2) and then go to getTransactionIsolationX. On the
>third connection, the test call setTransactionIsolation(1) and go to
>getTransactionIsolationX().
This is done with DERBY-4314 patch.
Thank Kristian for your detail analysis. I believe we should chage isolation =
TRANSACTION_READ_COMMITTED with addtional change.
> 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.0.0
> Reporter: Kathey Marsden
> Priority: Minor
> Attachments: _cpds_0, 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.
