> > 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. > Thanks Rick. I certainly assume that they wouldn't normally do that. I was thinking maybe there was a specific trigger situation that might cause it. I'm not sure what else could be in the software stack to cause this. The derby version is 10.8.something (whatever was the most recent as of about a month ago) and its started in Network mode listening only to localhost address. The Apache Tomcat 7 web container is on the same host, with a container-managed connection pool, using the built-in Tomcat connection pool classes. On top of that is eclipselink JPA 2.0. Certainly none of that is something that I would expect to restart the database. The application doesn't have any code written directly against the database, everything goes through JPA. ________________________________ From: Rick Hillegas <rick.hille...@oracle.com> To: derby-user@db.apache.org Sent: Wednesday, April 25, 2012 8:31 AM 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? Hope this helps, -Rick > > > ------------------------------------------------------------------------ > *From:* Katherine Marsden <kmarsdende...@sbcglobal.net> > *To:* Derby Discussion <derby-user@db.apache.org> > *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? > > >
