db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajesh Kartha (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-894) checkDataSource test fails with a 10.1 derbytesting.jar and a 10.2 engine.
Date Sat, 15 Jul 2006 01:52:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-894?page=comments#action_12421264 ] 
            
Rajesh Kartha commented on DERBY-894:
-------------------------------------

I have not been able to reproduce this issue either. Tried with different jvms (IBM/Sun -
Java 1.5/1.4.2) on Win 2000. The codeline used were:
10.2.0.4 alpha - (420028)
10.1.3.2 - (420033)

So I presume this is no longer an issue, hence plan on closing it.  Send a mail to the list
if there are any concerns.

Regards,
Rajesh


> checkDataSource test fails with a 10.1 derbytesting.jar and a 10.2 engine.
> --------------------------------------------------------------------------
>
>                 Key: DERBY-894
>                 URL: http://issues.apache.org/jira/browse/DERBY-894
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.1.2.2
>         Environment:  10.2.0.0 alpha - 372715 (except derbyTesting.jar) and 10.1 derbyTesting.jar
file
> OS: Windows 2000, JVM: sun jdk 142
>            Reporter: David Van Couvering
>            Priority: Minor
>
> The test fails because the test complains that two connections from same pooled connection
have separate unique ids.  But actually the only difference is the id of the wrapping BrokeredConnection,
the underlying EmbedConnection is the same.  I'm not sure why this only occurs with a 10.1
testing jar and a 10.2 client, but perhaps we changed the way we do pooled connections to
allocate a separate BrokeredConnection object within the lifetime of a pooled connection.
> Anyway, the functionality is fine, and the test should be fixed in the 10.1 codeline.
 I searched for the string "Two connections from the same pooled connection" in the trunk
and couldn't find it, so I think this is old test code that has since been removed.  Once
I figure out how to get access to the 10.1 codeline I'll try to find the original code and
add a suggestiong as to how to fix it.
> Here is the test output:
> > java.lang.Exception: Two connections from the same pooled connection have diff
> erent string values: org.apache.derby.iapi.jdbc.BrokeredConnection30@19492125, W
> rapped Connection = org.apache.derby.impl.jdbc.EmbedConnection30@22199751 (XID =
>  164), (SESSIONID = 33), (DATABASE = wombat), (DRDAID = null) , org.apache.derby
> .iapi.jdbc.BrokeredConnection30@12231451, Wrapped Connection = org.apache.derby.
> impl.jdbc.EmbedConnection30@22199751 (XID = 164), (SESSIONID = 33), (DATABASE =
> wombat), (DRDAID = null)
> > java.lang.Exception: Two connections from the same pooled connection have diff
> erent string values: org.apache.derby.iapi.jdbc.BrokeredConnection30@19492125, W
> rapped Connection = org.apache.derby.impl.jdbc.EmbedConnection30@22199751 (XID =
>  164), (SESSIONID = 33), (DATABASE = wombat), (DRDAID = null) , org.apache.derby
> .iapi.jdbc.BrokeredConnection30@12231451, Wrapped Connection = org.apache.derby.
> impl.jdbc.EmbedConnection30@22199751 (XID = 164), (SESSIONID = 33), (DATABASE =
> wombat), (DRDAID = null)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message