db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1265) Different behavior of Connection.close() on xp vs. linux
Date Mon, 01 May 2006 16:22:50 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1265?page=all ]

Rick Hillegas updated DERBY-1265:

    Attachment: bug1265_01_sortMethods.diff

Committed bug1265_01_sortMethods.diff at subversion revision 398630. This addresses the instability
in this test. The problem was that Class.getMethods() does not return methods in a standard
order. Now the test sorts the methods before invoking them.

> 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:
>     Reporter: Rick Hillegas
>     Priority: Minor
>      Fix For:
>  Attachments: bug1265_01_sortMethods.diff
> 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:
For more information on JIRA, see:

View raw message