db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Myrna van Lunteren <m.v.lunte...@gmail.com>
Subject test jdbcapi/blobclob4BLOB...
Date Sat, 17 Sep 2005 10:43:37 GMT
 The master for the test jdbcapi/blobclob4BLOB includes a number of 
'FAIL...unexpected exception...' tests.
For instance, clobTest94 results in:
ERROR XJ073: The data in this BLOB or CLOB is no longer available. The BLOB 
CLOBs transaction may be committed, or its connection is closed.
 stack is like this:
 at org.apache.derby.iapi.error.StandardException.newException(
at org.apache.derby.impl.jdbc.EmbedClob.noStateChangeLOB(EmbedClob.java:794)
at org.apache.derby.impl.jdbc.EmbedClob.getCharacterStream(EmbedClob.java
at org.apache.derby.impl.jdbc.EmbedClob.length(EmbedClob.java:151)
This is after the 3rd row, from the while loop doing rs.getInt and 
 Does anyone know what is going on here? 
 I did find one reference in the old Cloudscape tracking system mentioning 
that the output of the test should get updated, as this is 'expected' 
because this test 'has always had this problem'. With this comment '[these] 
are tests to make sure that java.sql.Blob [and Clob] objects cannot be used 
over commit borders'.
I don't see how a commit gets involved in getting a clob from a resultset, 
so I don't know why these errors would be expected?
 (Note - I'm trying to analyze a NullPointerException in this test on OS390, 
but the canon for linux/windoze never even gets as far as the test on that 
other platform.)

View raw message