Daniel Noll writes: > What If I put a container around Derby and force all queries through that, > blocking queries which occur after shutdown has started, it does appear to > fix the issue. > > My theory is that some event was being fired on another thread and then that > resulted in a query which occurred at the same time as shutdown. Derby > mustn't handle this situation by denying that query or terminating it, but > what ends up happening is the shutdown continues and completes some random > time *after* the call to getConnection("...shutdown") returns (in the middle > of the next unit test.) Interesting. I will see if I can reproduce it. Dag