You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Manjula Kutty (JIRA)" <de...@db.apache.org> on 2006/03/14 01:31:41 UTC
[jira] Created: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
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
[jira] Updated: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Manjula Kutty (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ]
Manjula Kutty updated DERBY-1108:
---------------------------------
Derby Info: [Patch Available]
> 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
> Assignee: Manjula Kutty
> Attachments: svn_diff_06_21.txt, svn_stat_06_21.txt, 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
[jira] Updated: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Manjula Kutty (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ]
Manjula Kutty updated DERBY-1108:
---------------------------------
Attachment: svn_stat_06_21.txt
> 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
> Assignee: Manjula Kutty
> Attachments: svn_diff_06_21.txt, svn_stat_06_21.txt, 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
[jira] Updated: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ]
Myrna van Lunteren updated DERBY-1108:
--------------------------------------
Affects Version/s: 10.1.3.1
> The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
> -------------------------------------------------------------------
>
> Key: DERBY-1108
> URL: http://issues.apache.org/jira/browse/DERBY-1108
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.2.1.6, 10.1.3.1
> 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
> Assigned To: Manjula Kutty
> Fix For: 10.2.1.6
>
> Attachments: svn_diff.txt, svn_diff_06_21.txt, svn_stat_06_21.txt, 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
[jira] Updated: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ]
Kathey Marsden updated DERBY-1108:
----------------------------------
Derby Info: (was: [Patch Available])
Thanks Manjula for looking at this issue.
I was not able to apply this patch in Eclipse. The message I got was not in patch format. Looking at the patch it seems that some lines are split like:
--- java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/setTransact
ionIsolation.java (revision 416106)
Maybe that is the trouble. Perhaps a cut and paste of svn diff?
In terms of content it looks like a lot of white space was added. It might be good just to revert add in the rs.next() with the comment and regenerate the patch with svn diff redirected to file. I'll uncheck patch available until a new patch is submitted.
> 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
> Assignee: Manjula Kutty
> Attachments: svn_diff_06_21.txt, svn_stat_06_21.txt, 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
[jira] Commented: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12416665 ]
Kathey Marsden commented on DERBY-1108:
---------------------------------------
I told Manjula I would post the response from the IBM JVM Team and what I know about the issue.
JVM TEAM RESPONSE:
I don't believe this is a bug in the IBM JVM - we are legitimately clearing out objects that are no-longer referenced. The difference is that the IBM JVM at Java 5.0 is more agressive at doing this than it was previously.
The behaviour with BEA JRockit 5.0 is the same.
The IBM Java 5.0 implementation now carries out "escape analysis" - this means that an Object becomes eligable for garbage collection after the last time it is used which can be before you would classically expect it to be "out of scope". Below is a pathological example :
void testMethod{
String myString = new String("MyString");
myString.toLowercase();
System.out.println(myString);
<--- Under Java 5.0 myString is eligable for GC here
for (int i = 0; i < 10; i++){
System.out.println("Count is "+i);
}
}
<-- Under previous versions, myString is eligable for GC here.
WHAT KATHEY KNOWS ABOUT THE ISSUE
>From the behavior we were seeing and the test case, that we did not get an exception for this open result set, when setTransactionIsolation was called, I was under the assumption that it was the ResultSet rs that was getting garbage collected but it must be something else. Someone will have to take a close look at what is getting garbage collected here and try to understand how it correlates to escape analysis. I tried forcing gc() and then using the result set and it seemed to continue to be accessible and retrieve results normally.
The test code:
try {
PreparedStatement ps = conn.prepareStatement("SELECT * from TAB1");
ResultSet rs = ps.executeQuery();
rs.next();
// setTransactionIsolation should fail because we have
// a holdable cursor open
// conn.setTransactionIsolation does a gc/finalization and then checks if there are open holdable result sets.
// should fail because holdable result set is open.
conn.setTransactionIsolation(java.sql.Connection.TRANSACTION_SERIALIZABLE);
} catch (SQLException se)
{
System.out.println("EXPECTED EXCEPTION SQLSTATE:" +
se.getSQLState() + " " +
se.getMessage());
return;
}
Code to check result set status in GenericLanguageConnectionContext, called as part of setTransactionIsolation: (Removing this gc causes setTransactionIsolation to fail as expected. )
// 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();
/* For every activation */
for (int i = acts.size() - 1; i >= 0; i--) {
Activation a = (Activation) acts.elementAt(i);
if (SanityManager.DEBUG)
{
SanityManager.ASSERT(a instanceof CursorActivation, "a is not a CursorActivation");
}
if (!a.isInUse())
{
continue;
}
if (!a.getResultSetHoldability())
{
continue;
}
ResultSet rs = ((CursorActivation) a).getResultSet();
/* is there an open held result set? */
if ((rs != null) && !rs.isClosed() && rs.returnsRows())
{
return(false);
}
> 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
[jira] Commented: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Commented: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Manjula Kutty (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12417208 ]
Manjula Kutty commented on DERBY-1108:
--------------------------------------
I have made a patch with the rs.next after the setTransactionIsolation and the test passes with both ibm1.5 and sun jdk1.5.
> 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
> Assignee: Manjula Kutty
> Attachments: svn_diff_06_21.txt, svn_stat_06_21.txt, 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
[jira] Commented: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Manjula Kutty (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12370576 ]
Manjula Kutty commented on DERBY-1108:
--------------------------------------
The stack trace given by all other jvms other than ibm15 is like this :
ERROR X0X03: Invalid transaction state - held cursor requires same isolation lev
el
at org.apache.derby.iapi.error.StandardException.newException(StandardEx
ception.java:301)
at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.setIs
olationLevel(GenericLanguageConnectionContext.java:2353)
at org.apache.derby.impl.jdbc.EmbedConnection.setTransactionIsolation(Em
bedConnection.java:1163)
at test.main(test.java:57)
null
Does anybody know how to track down which JDBC call is causing the problem so that you can give that information to the jvm team working on the issue?
> 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
[jira] Resolved: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ]
Kathey Marsden resolved DERBY-1108.
-----------------------------------
Fix Version/s: 10.2.0.0
Resolution: Fixed
Tried test on IBM 1.5 SR2 and Sun JDK 1.4.2 Committed svn_diff.txt.
Date: Fri Aug 4 18:50:47 2006
New Revision: 428937
URL: http://svn.apache.org/viewvc?rev=428937&view=rev
Thanks Manjula for the fix.
> The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
> -------------------------------------------------------------------
>
> Key: DERBY-1108
> URL: http://issues.apache.org/jira/browse/DERBY-1108
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects 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
> Assigned To: Manjula Kutty
> Fix For: 10.2.0.0
>
> Attachments: svn_diff.txt, svn_diff_06_21.txt, svn_stat_06_21.txt, 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
[jira] Updated: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Manjula Kutty (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ]
Manjula Kutty updated DERBY-1108:
---------------------------------
Attachment: svn_diff_06_21.txt
> 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
> Assignee: Manjula Kutty
> Attachments: svn_diff_06_21.txt, svn_stat_06_21.txt, 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
[jira] Updated: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Manjula Kutty (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ]
Manjula Kutty updated DERBY-1108:
---------------------------------
Attachment: svn_diff.txt
Hi Kathey,
Thanks for your input. I'm attaching the diff again. Please have a look
> The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
> -------------------------------------------------------------------
>
> Key: DERBY-1108
> URL: http://issues.apache.org/jira/browse/DERBY-1108
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects 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
> Assigned To: Manjula Kutty
> Attachments: svn_diff.txt, svn_diff_06_21.txt, svn_stat_06_21.txt, 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
[jira] Commented: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Commented: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "A B (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12416823 ]
A B commented on DERBY-1108:
----------------------------
I'm not very well acquainted with this code, but based on the example of "escape analysis" posted by the JVM team, I think I understand why this test is failing with IBM 1.5.
If we look at the test program again, we can see that it very closely mimics the example of "escape analysis" offered by the JVM team. In particular:
System.out.println("done creating table and inserting data.");
conn.setTransactionIsolation(Connection.TRANSACTION_READ_COMMITTED);
ResultSet rs = stmt.executeQuery("select * from T1");
==> Under Java 5.0 rs is eligible for GC here...
System.out.println("current isolation level: " + getIsoLevelName(conn.getTransactionIsolation()));
conn.setTransactionIsolation(java.sql.Connection.TRANSACTION_SERIALIZABLE);
System.out.println("current isolation level: " + getIsoLevelName(conn.getTransactionIsolation()));
==> Under previous versions, rs is eligible for GC here...
So with ibm15, rs becomes eligible for GC _prior_ to the call to setTransactionIsolation because it (rs) is no longer referenced after it is created. Then the call to gc() in verifyAllHeldResultSetsAreClosed() does the escape analysis, sees that rs is now eligible for GC and so collects it. As part of that collection process the JVM calls "finalize()", which takes us to EmbedResultSet.finalize(), and there we see this:
/**
JDBC states that a ResultSet is closed when garbage collected.
We simply mark the activation as unused. Some later use
of the connection will clean everything up.
@exception Throwable Allows any exception to be thrown during finalize
*/
protected void finalize() throws Throwable {
super.finalize();
if (finalizeActivation != null) {
finalizeActivation.markUnused();
}
}
Thus finalizeActiviation is now marked as "unused", which means we end up ignoring the activation in the verifyAllHeldResultSetsAreClosed() method:
if (!a.isInUse())
{
continue;
}
And therefore we return "true" from the method and no error is thrown.
To prove this, I added a very simple (albeit meaningless) reference to "rs" after the call to setTransactionIsolation:
System.out.println("done creating table and inserting data.");
conn.setTransactionIsolation(Connection.TRANSACTION_READ_COMMITTED);
ResultSet rs = stmt.executeQuery("select * from T1");
System.out.println("current isolation level: " + getIsoLevelName(conn.getTransactionIsolation()));
conn.setTransactionIsolation(java.sql.Connection.TRANSACTION_SERIALIZABLE);
System.out.println("current isolation level: " + getIsoLevelName(conn.getTransactionIsolation()));
System.out.println(rs); // <== Added by Army
With this simple line, the escape analysis will *not* mark rs eligible for GC prior to setTransactionIsolation, which means we won't call "finalize()", which means the activation will remain "in use", and therefore we'll get the exception.
All of that said, I added System.outs to the test program to see what the object id of "rs" is before the call to setTransactionIsolation, and I also added System.outs to see what the object id of the "rs" is inside verifyAllHeldResultSetsAreClosed(). Not surprisingly, the objects are NOT the same. In the test program we see:
org.apache.derby.impl.jdbc.EmbedResultSet20@d0a0d0a
but in verifyAllHeldResultSetsAreClosed() we see:
org.apache.derby.impl.sql.execute.BulkTableScanResultSet@42484248
So as far as I can tell, the test program no longer references the EmbedResultSet, so it's marked as "eligible for GC" and is garbage collected by escape analysis; however, that EmbedResultSet was in turn referencing another object--BulkTableScanResultSet--that *is* still referenced (by the activation), and that's the result set that should have caused the error--but since we "bailed" on the error checking because the activiation was no longer "in use", we never checked the underlying result set and therefore we didn't throw the exception.
That's my take on it after looking at it briefly. I still don't know for sure who's "at fault" here (the JVM or Derby)--I'd have to look at it more to say one way or the other. But that's my first take on the issue...
Comments/input/feedback are, as always, much appreciated...
Army
> 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
[jira] Commented: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12370621 ]
Kathey Marsden commented on DERBY-1108:
---------------------------------------
Actually maybe I had this backward. Maybe this JVM is being more agressive with the gc(). Anyway, if your resultset is still referenced and the error is supposed to be there, start with commenting out that gc() call and go from there. Good Luck!
> 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
[jira] Reopened: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ]
Myrna van Lunteren reopened DERBY-1108:
---------------------------------------
backporting this fix to 10.1
> The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
> -------------------------------------------------------------------
>
> Key: DERBY-1108
> URL: http://issues.apache.org/jira/browse/DERBY-1108
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.2.1.6
> 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
> Assigned To: Manjula Kutty
> Fix For: 10.2.1.6
>
> Attachments: svn_diff.txt, svn_diff_06_21.txt, svn_stat_06_21.txt, 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
Re: [jira] Commented: (DERBY-1108) The test jdbcapi/setTransactionIsolation.java
fails with ibm jvm1.5
Posted by Manjula G Kutty <ma...@gmail.com>.
A B (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12416921 ]
>
>A B commented on DERBY-1108:
>----------------------------
>
>
>
>
>>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?
>>
>>
>
>Sounds goods to me.
>
>
>
>>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
>>
>>
>
>
>
Hi,
I'm just curious to know that , then why the test was passing without
any problem on Sun Jdk1.5?
Thanks
Manjula
[jira] Commented: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "A B (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12416921 ]
A B commented on DERBY-1108:
----------------------------
> 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?
Sounds goods to me.
> 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
[jira] Closed: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ]
Myrna van Lunteren closed DERBY-1108.
-------------------------------------
> The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
> -------------------------------------------------------------------
>
> Key: DERBY-1108
> URL: http://issues.apache.org/jira/browse/DERBY-1108
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.2.1.6, 10.1.3.1
> 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
> Assigned To: Manjula Kutty
> Fix For: 10.1.3.2, 10.2.1.6
>
> Attachments: svn_diff.txt, svn_diff_06_21.txt, svn_stat_06_21.txt, 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
[jira] Resolved: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ]
Myrna van Lunteren resolved DERBY-1108.
---------------------------------------
Fix Version/s: 10.1.3.2
Resolution: Fixed
merge didn't work, so I applied the change of revision 428937 manually with:
http://svn.apache.org/viewvc?view=rev&revision=477228
Sending java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\
setTransactionIsolation.java
> The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
> -------------------------------------------------------------------
>
> Key: DERBY-1108
> URL: http://issues.apache.org/jira/browse/DERBY-1108
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.2.1.6, 10.1.3.1
> 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
> Assigned To: Manjula Kutty
> Fix For: 10.1.3.2, 10.2.1.6
>
> Attachments: svn_diff.txt, svn_diff_06_21.txt, svn_stat_06_21.txt, 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
[jira] Commented: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Manjula Kutty (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12370623 ]
Manjula Kutty commented on DERBY-1108:
--------------------------------------
Yes Kathey, You are right. When I commented out the gc(), I got the exception. Will be informing the jvm people about this. Thanks for your valuable information
> 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
[jira] Updated: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Manjula Kutty (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ]
Manjula Kutty updated DERBY-1108:
---------------------------------
Attachment: test.java
I'm attaching a simple reproduction. But still there are some gray areas why ibm15 is not throwing the expected exception.
> 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
[jira] Assigned: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Manjula Kutty (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ]
Manjula Kutty reassigned DERBY-1108:
------------------------------------
Assign To: Manjula Kutty
> 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
> Assignee: 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
[jira] Commented: (DERBY-1108) The test
jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
Posted by "Manjula Kutty (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12370615 ]
Manjula Kutty commented on DERBY-1108:
--------------------------------------
No, The test does not close the resultSet explicitly
> 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