db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <de...@segel.com>
Subject RE: Troubleshooting
Date Wed, 23 Sep 2009 14:16:17 GMT

> -----Original Message-----
> From: Myrna van Lunteren [mailto:m.v.lunteren@gmail.com]
> Sent: Tuesday, September 22, 2009 10:02 PM
> To: Derby Discussion
> Subject: Re: Troubleshooting
> It sounds like the application 'crashes' when it's trying to
> initialize the database...i.e. the jvm (your 'java' process) stops for
> some reason.
> You said, "most of derby.log says 'unknown'". Does it say 'Unknown
> Source'? If so, that likely just means you're running with normal -
> not debug - derby jar files (the exact line number in the source are
> unknown).
> What would help us is the contents of the derby.log - any errors, and
> the stack of called methods at the time of the error if it's there.
> And just in case - do you have a backup of the database (i.e. a copy
> of the database directory) when it was still working? Would be
> interesting to see if you can get things going with that backup.
> Regards,
> Myrna

Just out of curiosity, even if you've got an embedded Derby database within
an app, and its not set up as a networked copy, if the application is down,
couldn't you use IJ to connect to the database for debugging purposes?

This will help reduce the problem set and let you verify that the database
is 'sane' or uncorrupted.

Or am I missing something?


View raw message