I believe if there is a severe condition that Derby detects, it will internally restart and output to the log the startup message again. If you don't have the derby.log setting to append it will appear as if the complete engine restarted. If you do have it to append, you might see the severe error that caused the internal restart.
I think it is DRDAConnection.c where this can be seen but I don't have the code in front of me at this moment. -----Original Message----- From: Rick Hillegas [mailto:[email protected]] Sent: Wednesday, April 25, 2012 8:32 AM To: [email protected] Subject: Re: No Connection Exception On 4/24/12 6:49 PM, Tomcat Programmer wrote: > That is a very good question... there is no error message at all. > However, what I did see was a startup message, like when the database > initially starts. Except, I never restarted it! And the machine did > not reboot... are there ever conditions where it auto-restarts itself? Derby engines and databases don't spontaneously reboot as far as I know. This suggests that the engine and/or database are being bounced by code higher up your application stack. Hope this helps, -Rick > > > ---------------------------------------------------------------------- > -- > *From:* Katherine Marsden <[email protected]> > *To:* Derby Discussion <[email protected]> > *Sent:* Tuesday, April 24, 2012 5:06 PM > *Subject:* Re: No Connection Exception > > On 4/24/2012 1:19 PM, Tomcat Programmer wrote: >> Hello, >> >> >> >> The only way to clear this up seems to be restarting the web >> container. Is there some setting in Derby which is causing these >> connections to go stale? Is there any way to trace this and find out >> the cause? >> > Is there an interesting error in the derby.log that might indicate > when you lost the connection? > > >
