[ 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
