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 "roy mylchreest (JIRA)" <de...@db.apache.org> on 2005/11/07 10:57:20 UTC
[jira] Created: (DERBY-685) Unexpected SQL Error
Unexpected SQL Error
--------------------
Key: DERBY-685
URL: http://issues.apache.org/jira/browse/DERBY-685
Project: Derby
Type: Bug
Versions: 10.0.2.1
Environment: Windows XP Embedded
Reporter: roy mylchreest
We are running Derby on over 20 IBM Revelation shop tills and about once a day we get the message.
ERROR XSLA4: Cannot write to the log, most likely the log is full. Please
delete unnecessary files. It is also possible that the file system is read
only, or the disk has failed, or some other problems with the media
This results in the till having to be re-booted, much to the frustration of the cashier and the customer.
However on investigation everything seems fine, the log is not full and there is plenty of room on the disk.
Could anybody give me some advice on this please as it is becoming a major issue for our retail operations.
thanks
--
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] Created: (DERBY-685) Unexpected SQL Error
Posted by Daniel John Debrunner <dj...@debrunners.com>.
roy mylchreest (JIRA) wrote:
> Unexpected SQL Error
> --------------------
>
> Key: DERBY-685
> URL: http://issues.apache.org/jira/browse/DERBY-685
> Project: Derby
> Type: Bug
> Versions: 10.0.2.1
> Environment: Windows XP Embedded
> Reporter: roy mylchreest
>
>
> We are running Derby on over 20 IBM Revelation shop tills and about once a day we get the message.
>
> ERROR XSLA4: Cannot write to the log, most likely the log is full. Please
> delete unnecessary files. It is also possible that the file system is read
> only, or the disk has failed, or some other problems with the media
>
> This results in the till having to be re-booted, much to the frustration of the cashier and the customer.
>
> However on investigation everything seems fine, the log is not full and there is plenty of room on the disk.
>
> Could anybody give me some advice on this please as it is becoming a major issue for our retail operations.
Is it possible to get the stack trace for this exception and the
exception it nests? This SQLException should have a nested (chained)
exception that represents the original IOException from the file system.
Something like
catch (SQLException sqle)
{
do {
System.out.println("ERROR " + sqle.getSQLState() + " -- " +
sqle.getMessage());
sqle.printStackTrace(System.out);
sqle = sqle.getNextException();
} while (sqle != null)
}
Derby does retry some writes multiple times when it hits an IOException,
to try and ensure it it's not some transient error. The stack trace
would tell if it was one of these multiple write on failure situation.
Thanks,
Dan.
[jira] Updated: (DERBY-685) Unexpected SQL Error
Posted by "roy mylchreest (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-685?page=all ]
roy mylchreest updated DERBY-685:
---------------------------------
Attachment: DerbyStack.txt
Attached is a dump of the stack trace. Any references to: com.triangle.group.jlp.rips... related to our POS application.
> Unexpected SQL Error
> --------------------
>
> Key: DERBY-685
> URL: http://issues.apache.org/jira/browse/DERBY-685
> Project: Derby
> Type: Bug
> Versions: 10.0.2.1
> Environment: Windows XP Embedded
> Reporter: roy mylchreest
> Attachments: DerbyStack.txt
>
> We are running Derby on over 20 IBM Revelation shop tills and about once a day we get the message.
> ERROR XSLA4: Cannot write to the log, most likely the log is full. Please
> delete unnecessary files. It is also possible that the file system is read
> only, or the disk has failed, or some other problems with the media
> This results in the till having to be re-booted, much to the frustration of the cashier and the customer.
> However on investigation everything seems fine, the log is not full and there is plenty of room on the disk.
> Could anybody give me some advice on this please as it is becoming a major issue for our retail operations.
> thanks
--
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-685) Unexpected SQL Error
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-685?page=all ]
Kathey Marsden resolved DERBY-685:
----------------------------------
Resolution: Incomplete
Closing this out as incomplete until a bug can be verified. It can be reopened if established that it is a bug.
> Unexpected SQL Error
> --------------------
>
> Key: DERBY-685
> URL: http://issues.apache.org/jira/browse/DERBY-685
> Project: Derby
> Type: Bug
> Versions: 10.0.2.1
> Environment: Windows XP Embedded
> Reporter: roy mylchreest
> Attachments: DerbyStack.txt
>
> We are running Derby on over 20 IBM Revelation shop tills and about once a day we get the message.
> ERROR XSLA4: Cannot write to the log, most likely the log is full. Please
> delete unnecessary files. It is also possible that the file system is read
> only, or the disk has failed, or some other problems with the media
> This results in the till having to be re-booted, much to the frustration of the cashier and the customer.
> However on investigation everything seems fine, the log is not full and there is plenty of room on the disk.
> Could anybody give me some advice on this please as it is becoming a major issue for our retail operations.
> thanks
--
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-685) Unexpected SQL Error
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-685?page=all ]
Rick Hillegas updated DERBY-685:
--------------------------------
Component: Store
Assigning this to Store component.
> Unexpected SQL Error
> --------------------
>
> Key: DERBY-685
> URL: http://issues.apache.org/jira/browse/DERBY-685
> Project: Derby
> Type: Bug
> Components: Store
> Versions: 10.0.2.1
> Environment: Windows XP Embedded
> Reporter: roy mylchreest
> Attachments: DerbyStack.txt
>
> We are running Derby on over 20 IBM Revelation shop tills and about once a day we get the message.
> ERROR XSLA4: Cannot write to the log, most likely the log is full. Please
> delete unnecessary files. It is also possible that the file system is read
> only, or the disk has failed, or some other problems with the media
> This results in the till having to be re-booted, much to the frustration of the cashier and the customer.
> However on investigation everything seems fine, the log is not full and there is plenty of room on the disk.
> Could anybody give me some advice on this please as it is becoming a major issue for our retail operations.
> thanks
--
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-685) Unexpected SQL Error
Posted by "Suresh Thalamati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-685?page=comments#action_12356975 ]
Suresh Thalamati commented on DERBY-685:
----------------------------------------
Thanks for posting the complete stack trace. By looking at the stack and
related code in Logtofile.java , it appears to me the threads that are doing
the database work might have been interrupted. Does your application interrupts
the threads thare accessing the database ?
I think the reason exception in the stacks ClosedChannelException instead of a
interrupted exception like ClosedByInterruptExceptio is on IO exception derby
log file sync code retries few time before throwing the error. On first
attempt to sync the file , interrupt may have occurred, which closed the
channel, on second attempt the error becomes ClosedChannelException.
There was some discussion on derby-user list about a similar problem when a user
was interrupting the database threads, he was seeing similar errors.
http://article.gmane.org/gmane.comp.apache.db.derby.user/1528/match=flush
Thanks
-suresht
> Unexpected SQL Error
> --------------------
>
> Key: DERBY-685
> URL: http://issues.apache.org/jira/browse/DERBY-685
> Project: Derby
> Type: Bug
> Versions: 10.0.2.1
> Environment: Windows XP Embedded
> Reporter: roy mylchreest
> Attachments: DerbyStack.txt
>
> We are running Derby on over 20 IBM Revelation shop tills and about once a day we get the message.
> ERROR XSLA4: Cannot write to the log, most likely the log is full. Please
> delete unnecessary files. It is also possible that the file system is read
> only, or the disk has failed, or some other problems with the media
> This results in the till having to be re-booted, much to the frustration of the cashier and the customer.
> However on investigation everything seems fine, the log is not full and there is plenty of room on the disk.
> Could anybody give me some advice on this please as it is becoming a major issue for our retail operations.
> thanks
--
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-685) Unexpected SQL Error
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-685?page=comments#action_12360469 ]
Kathey Marsden commented on DERBY-685:
--------------------------------------
Seems like this one might best suited for the derby-user list as it has not yet been established as a bug. Anyone have any objections to closing it out? If I hear nothing I will close it Friday
> Unexpected SQL Error
> --------------------
>
> Key: DERBY-685
> URL: http://issues.apache.org/jira/browse/DERBY-685
> Project: Derby
> Type: Bug
> Versions: 10.0.2.1
> Environment: Windows XP Embedded
> Reporter: roy mylchreest
> Attachments: DerbyStack.txt
>
> We are running Derby on over 20 IBM Revelation shop tills and about once a day we get the message.
> ERROR XSLA4: Cannot write to the log, most likely the log is full. Please
> delete unnecessary files. It is also possible that the file system is read
> only, or the disk has failed, or some other problems with the media
> This results in the till having to be re-booted, much to the frustration of the cashier and the customer.
> However on investigation everything seems fine, the log is not full and there is plenty of room on the disk.
> Could anybody give me some advice on this please as it is becoming a major issue for our retail operations.
> thanks
--
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