action.doAction(m_dbName);
}
m_derbyServerControl.shutdown();
}
-Original Message-
From: Pavel Bortnovskiy [mailto:pbortnovs...@jefferies.com]
Sent: Friday, January 13, 2012 10:01 AM
To: Derby Discussion
Subject: RE: Shutting down in-memory Derby gracefully
Hello
dbName);
}
m_derbyServerControl.shutdown();
}
-----Original Message-----
From: Pavel Bortnovskiy [mailto:pbortnovs...@jefferies.com]
Sent: Friday, January 13, 2012 10:01 AM
To: Derby Discussion
Subject: RE: Shutting down in-memory Derby gracefully
Hello, Bryan:
Thank
On 1/13/2012 7:01 AM, Pavel Bortnovskiy wrote:
Hello, Bryan:
Thank you for your prompt response. I will report it as per guidelines.
Would you be able to suggest anything that I could do in the meantime?
Hi Pavel, I don't have much experience with in-memory databases. Does it
help to connect w
kinds of alarms.
This is more than just a nuisance, as it's causing havoc in some cases.
Thank you,
Pavel.
-Original Message-
From: Bryan Pendleton [mailto:bpendleton.de...@gmail.com]
Sent: Friday, January 13, 2012 9:58 AM
To: Derby Discussion
Subject: Re: Shutting down in-memory
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 o
