[ http://issues.apache.org/jira/browse/DERBY-1265?page=all ]
Rick Hillegas updated DERBY-1265:
---------------------------------
Priority: Minor (was: Major)
Dyre has pointed out the likely cause of this discrepancy between the
platforms: The order in which vetObject() traverses the methods is determined
by a HashSet and can be expected to vary by platform. Thanks, Dyre.
> Different behavior of Connection.close() on xp vs. linux
> --------------------------------------------------------
>
> Key: DERBY-1265
> URL: http://issues.apache.org/jira/browse/DERBY-1265
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.2.0.0
> Reporter: Rick Hillegas
> Priority: Minor
> Fix For: 10.2.0.0
>
> I have seen an odd discrepancy in the UnsupportedVetter test when run on xp
> vs. linux against build 81 of jdk1.6. I have commented out the close() on the
> connection in connectionWorkhorse(). On xp this method succeeds. On linux it
> raises an Invalid Transaction State exception. My working theory is that the
> earlier call to vetObject(), which cycles through all the java.sql methods in
> an object and calls them one by one, ends up making the connection invalid
> (perhaps when calling Connection.close() itself). Why this happens on linux
> but not xp puzzles me.
--
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
