Dyre Tjeldvoll <[email protected]> writes: > So, I have never heard about Dukascopy's Forex > Platform before… what is that? > > Based on the callstack you provided it looks like none of Derby’s > heuristics for locating a tmp directory works on this platform. > Arguably it is a bug that you get an NPE, but the alternative would > have been something like “Unable to locate tmp dir”, I think.
The NPE is probably https://issues.apache.org/jira/browse/DERBY-6396, which is fixed in Derby 10.10.2.0 and Derby 10.11.1.1. The underlying issue is that the tmp directory of the database has become inaccessible somehow. Here's what I would try in order to make the database bootable again: 1. Take a copy of the database directory, so that you have a way to go back if something goes wrong. 2. Manually delete the following directory: C:\Program Files\Derby Database\us_copiosus\tmp 3. Start your application. Hopefully, this should be enough to get it going again. The code that runs into the NPE, is trying to clear out temporary files from the previous run. By manually deleting the tmp directory, you prevent that code from running. The tmp directory will be recreated automatically when the database is booted. > > > On 17. sep. 2014, at 19:39, Bob M <[email protected]> wrote: > >> Hi Rick >> >> derby.log >> <http://apache-database.10148.n7.nabble.com/file/n142209/derby.log> >> >> attempting to upload derby.log >> >> Bob M >> >> >> >> -- >> View this message in context: >> http://apache-database.10148.n7.nabble.com/Derby-Error-message-explanation-required-tp142183p142209.html >> Sent from the Apache Derby Users mailing list archive at Nabble.com.
