[ http://issues.apache.org/jira/browse/DERBY-894?page=comments#action_12419571 ]
Sunitha Kambhampati commented on DERBY-894: ------------------------------------------- Just wanted to mention: I ran recently the checkDataSource tests with 10.1 derbyTesting.jar and 10.2 server as part of DERBY-1449 and the tests passed OK. http://issues.apache.org/jira/browse/DERBY-1449?page=comments#action_12418530 Is anyone seeing the diff mentioned in this jira ? If not, should we close this issue ? > 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 > Type: Bug > Components: Test > 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: [EMAIL PROTECTED], W > rapped Connection = [EMAIL PROTECTED] (XID = > 164), (SESSIONID = 33), (DATABASE = wombat), (DRDAID = null) , > org.apache.derby > [EMAIL PROTECTED], Wrapped Connection = org.apache.derby. > [EMAIL PROTECTED] (XID = 164), (SESSIONID = 33), (DATABASE = > wombat), (DRDAID = null) > > java.lang.Exception: Two connections from the same pooled connection have > > diff > erent string values: [EMAIL PROTECTED], W > rapped Connection = [EMAIL PROTECTED] (XID = > 164), (SESSIONID = 33), (DATABASE = wombat), (DRDAID = null) , > org.apache.derby > [EMAIL PROTECTED], Wrapped Connection = org.apache.derby. > [EMAIL PROTECTED] (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
