db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: Erroneous "Cannot write to log" exception?
Date Thu, 10 Feb 2005 18:09:46 GMT
The log should not "get full" if there is room on the file system
where it resides.  This error may result if other errors have
occurred which derby have determined to so severe that the system
needs to be shut down without allowing any more logging activity -
to insure that restart recovery will bring the system back to
a consistent state.  In such a case there will be more information
in the derby.log file about the other errors.

Barnet Wagman wrote:

> Can a log fill if the disk it's on is not full?
> On a couple of occasions, I got the exception
>     SQL Exception: 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.
> The filesystem where Derby resides is definitely not full or read only. 
> This occurred during shutdown of my app, although I cannot tell whether
> it happened before, during or after my
> DriverManager.getConnection("jdbc:derby:;shutdown=true") call.  It does
> not occur consistently and I haven't found a way to force it to occur.
> Thanks,
> bw

View raw message