While our application is shutting down, it is possible that some of its 
components may continue execution or even begin
execution of the queries on the in-memory Derby DB. In such situation, Derby 
starts throwing all kinds of exceptions, including
a Null Pointer Exception (pls see excerpt from our log below).

That looks like a bug to me, and worthy of reporting to the Derby developers.

http://db.apache.org/derby/DerbyBugGuidelines.html

thanks,

bryan


Reply via email to