[ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12416825 ]
Kathey Marsden commented on DERBY-1108: --------------------------------------- Thanks Army for the comment. I think I understand escape analysis better now and how it relatest to this issue and I think 1) The JVM is ok. It should garbage collect and finalize rs and all its innards because they can never really be used again. 2) Derby is ok. setTransactionIsolation() does not need to consider a ResultSet that can never be used again . 3) The test is not ok. To test what it wants to test, that we can't change the isolation in the middle of retrieving results on a held cursor, it should have code to use rs after setTransactionIsolation, e.g. add an rs.next() after setTransactionIsolation() Does that sound right? > 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 > Attachments: test.java > > 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
