[ 
https://issues.apache.org/jira/browse/DERBY-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806567#action_12806567
 ] 

Jim Rayfield commented on DERBY-2286:
-------------------------------------

I have a testcase that reproduces this behavior on 10.5.3.0:

INFO: Unexpected error
java.sql.SQLException: nospc.U
        at 
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown 
Source)
        at 
org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown 
Source)
        at 
org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown 
Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown 
Source)
        at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown 
Source)
        at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown 
Source)
        at 
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown 
Source)
        at 
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown Source)
        at NoSpaceBug$ThreadRunner.run(NoSpaceBug.java:100)
        at java.lang.Thread.run(Thread.java:811)
Caused by: ERROR nospc: nospc.U
        at org.apache.derby.impl.store.raw.data.StoredPage.logRow(Unknown 
Source)
        at 
org.apache.derby.impl.store.raw.data.UpdateOperation.writeOptionalDataToBuffer(Unknown
 Source)
        at org.apache.derby.impl.store.raw.data.UpdateOperation.<init>(Unknown 
Source)
        at 
org.apache.derby.impl.store.raw.data.LoggableActions.actionUpdate(Unknown 
Source)
        at 
org.apache.derby.impl.store.raw.data.StoredPage.doUpdateAtSlot(Unknown Source)
        at org.apache.derby.impl.store.raw.data.BasePage.updateAtSlot(Unknown 
Source)
        at 
org.apache.derby.impl.store.access.conglomerate.GenericConglomerateController.replace(Unknown
 Source)
        at org.apache.derby.impl.sql.execute.RowChangerImpl.updateRow(Unknown 
Source)
        at 
org.apache.derby.impl.sql.execute.UpdateResultSet.collectAffectedRows(Unknown 
Source)
        at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown 
Source)
        at 
org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source)
        at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown 
Source)
        ... 5 more

It needs to be run for a while (an hour for me) on a modern multiprocessor 
linux system.  I could not reproduce it on a Windows laptop running overnight.

------------------ Java Information ------------------
Java Version:    1.5.0
Java Vendor:     IBM Corporation
Java home:       /opt/ibm/java2-i386-50/jre
Java classpath:  derby.jar
OS name:         Linux
OS architecture: x86
OS version:      2.6.18-128.el5xen
Java user name:  root
Java user home:  /root
Java user dir:   /root/cvs/ccache
java.specification.name: Java Platform API Specification
java.specification.version: 1.5
--------- Derby Information --------
JRE - JDBC: J2SE 5.0 - JDBC 3.0
[/root/cvs/ccache/derby.jar] 10.5.3.0 - (802917)
------------------------------------------------------
----------------- Locale Information -----------------
------------------------------------------------------

I'll attach the source file.


> Exception NoSpaceOnPage does not provide SQLState or exception text
> -------------------------------------------------------------------
>
>                 Key: DERBY-2286
>                 URL: https://issues.apache.org/jira/browse/DERBY-2286
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.1.3.1, 10.2.1.6, 10.2.2.0
>            Reporter: Andrew McIntyre
>            Priority: Minor
>
> Originally reported on the derby-user list in this post:
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200701.mbox/%[email protected]%3e
> The user encountered an impl.store.raw.data.NoSpaceOnPage exception during a 
> batch update. The exception currently does not provide a SQLState or 
> exception text explaining the cause of the error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to