db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "?ystein Gr?vlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1058) derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed.
Date Fri, 17 Mar 2006 09:33:59 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1058?page=comments#action_12370797 ] 

Øystein Grøvlen commented on DERBY-1058:

Patch looks good.  I have verified that the added test fails without the fix and succeeds
with the fix.  However, derbyall fails on this test when running the derbynetmats.  I get
this error for all test cases:

null userid not supported

> derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate
1,141,037,436,752 is closed.
> ----------------------------------------------------------------------------------------------------------------------
>          Key: DERBY-1058
>          URL: http://issues.apache.org/jira/browse/DERBY-1058
>      Project: Derby
>         Type: Bug
>   Components: SQL, Store
>     Versions:
>  Environment: All
>     Reporter: Andreas Korneliussen
>     Assignee: Andreas Korneliussen
>  Attachments: DERBY-1058.diff, DERBY-1058.stat, DERBY-1058v2.diff, DERBY-1058v2.stat,
HoldabilityIssue.java, derbyall_report.txt
> If the ResultSet is so big that the scrollable resultset needs to back the hashtable
to disk, and the resultset is not fully populated before a commit(),
> a call to next() will fail with:
> ak136785@khepri35:/<3>db-derby-> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:./derby.jar
> ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed.
>         at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
>         at org.apache.derby.impl.store.access.btree.BTreeController.insert(Unknown Source)
>         at org.apache.derby.impl.store.access.btree.index.B2IController.insert(Unknown
>         at org.apache.derby.iapi.store.access.DiskHashtable.put(Unknown Source)
>         at org.apache.derby.iapi.store.access.BackingStoreHashtable.spillToDisk(Unknown
>         at org.apache.derby.iapi.store.access.BackingStoreHashtable.add_row_to_hash_table(Unknown
>         at org.apache.derby.iapi.store.access.BackingStoreHashtable.put(Unknown Source)
>         at org.apache.derby.impl.sql.execute.ScrollInsensitiveResultSet.addRowToHashTable(Unknown
>         at org.apache.derby.impl.sql.execute.ScrollInsensitiveResultSet.getNextRowFromSource(Unknown
>         at org.apache.derby.impl.sql.execute.ScrollInsensitiveResultSet.getNextRowCore(Unknown
>         at org.apache.derby.impl.sql.execute.BasicNoPutResultSetImpl.getNextRow(Unknown
>         at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown Source)
>         at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)
>         at derbytest.HoldabilityIssue.runTest1(HoldabilityIssue.java:72)
>         at derbytest.HoldabilityIssue.main(HoldabilityIssue.java:91)
> ak136785@khepri35:/<3>db-derby->
> The BtreeController is always initialized as non-holdable, and if this is changed, Derby
has the following assert in closeForEndTransaction(..):
>    SanityManager.THROWASSERT("There is currently no requirement for a held btree conglomerate
> A simple test program is attached which reproduces this failure. It fails in the trunk
and on the release

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