1) First of all - check if you - or somebody in your team does not close connection explicitly;) - f.e.: there is some PMD rule about not closing connection and someone could fix this PMD...;) - was a real case in our project;)
2) In our project there was also problem with loosing connection and reconnecting in derby 10.7.x - don't know how about the previous versions, as we didn't use the DB so heavily. Problem disappeared in latest i.e. 10.8 ver. - where some improvements have been made regarding interruption handlings : * Improved interrupt handling - Interrupting connection threads no longer crashes the Derby engine. http://old.nabble.com/-ANNOUNCE--Apache-Derby-10.8.1.2-released-to315235 46.html#a31523546 Hopefully helps!;) .......................... Regards / Pozdrowienia Jan Bartosz My contact info in Phonebook Click to call me by using Softphone -----Original Message----- From: ext bruehlicke [mailto:[email protected]] Sent: Tuesday, February 14, 2012 3:12 PM To: Derby Discussion Subject: Re: Derby Embedded losing connection ? Thanx for you interest. Its version 10.5.3.0 - I will collect more info. No connection pooling by the way. Simple JDBC createConnection. Bernd On Tue, Feb 14, 2012 at 1:24 AM, Bartosz, Jan (NSN - PL/Wroclaw) <[email protected]> wrote: > Which derby version? Can you provide some stacktrace? > > .......................... > Regards / Pozdrowienia > Jan Bartosz > My contact info in Phonebook > Click to call me by using Softphone > -----Original Message----- > From: ext Bryan Pendleton [mailto:[email protected]] > Sent: Tuesday, February 14, 2012 3:19 AM > To: Derby Discussion > Subject: Re: Derby Embedded losing connection ? > >> get reports (and also felt it our self) that our app simply is losing >> its connection to the DB. > > What are the symptoms, exactly? > > That is, what is it that makes you think you are losing your connection? > > One thing that occurs to me is a bit of a long-shot: are you using a > connection pooling framework of some sort? If so, is it possible that > the connection pooling framework is making a mistake and closing a > connection inappropriately? > > thanks, > > bryan >
