db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1108) The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Date Wed, 15 Mar 2006 23:58:01 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12370613 ] 

Kathey Marsden commented on DERBY-1108:
---------------------------------------

Yes. It is so much harder when the problem is that you are *not*  throwing the error.   You
have to trace back through the code and figure out what return value was not the value  expected.
  My line numbers don't match up to yours but presumably verifyAllHeldResultSetsAreClosed()
is returning false instead of the expected true value.

If you look at verifyAllHeldResultSetsAreClosed() you can see it is relying on this gc:

// There may be open ResultSet's that are yet to be garbage collected
// let's try and force these out rather than throw an error
		System.gc();
		System.runFinalization();

That would be my first guess as to the cause of the trouble.  Probably this JVM is not garbage
collecting the open resultsets in this case.

In your test case has the resultSet  been explicitly closed or was it left open with the expectation
of garbage collection before the setTransaction isolation call?




> The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
> -------------------------------------------------------------------
>
>          Key: DERBY-1108
>          URL: http://issues.apache.org/jira/browse/DERBY-1108
>      Project: Derby
>         Type: Bug
>   Components: Regression Test Failure
>     Versions: 10.2.0.0
>  Environment: java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20051104)
> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-2005110
> 3 (JIT enabled)
> J9VM - 20051027_03723_lHdSMR
> JIT  - 20051027_1437_r8
> GC   - 20051020_AA)
> JCL  - 20051102
>     Reporter: Manjula Kutty

>
> The test  jdbcapi/setTransactionIsolation.java fails with ibmjvm15.  I think the cause
of this failure is , the jvm is not throwing an exception while trying to change the transaction
isolation when there is holdable cursor on  a resultset. Other jvms like sun jdk1.5, ibm142
throws the expected exception. while ibm15 does allow to change the transaction isolation
when there is a hold cursor on a result set.
> Already reported this issue with the ibmjvm people and they are looking in to it

-- 
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