db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: [jira] Created: (DERBY-685) Unexpected SQL Error
Date Mon, 07 Nov 2005 12:10:11 GMT
roy mylchreest (JIRA) wrote:

> Unexpected SQL Error
> --------------------
>          Key: DERBY-685
>          URL: http://issues.apache.org/jira/browse/DERBY-685
>      Project: Derby
>         Type: Bug
>     Versions:    
>  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 = 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.


View raw message