Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0C951984B for ; Wed, 25 Apr 2012 13:03:39 +0000 (UTC) Received: (qmail 3938 invoked by uid 500); 25 Apr 2012 13:03:38 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 3904 invoked by uid 500); 25 Apr 2012 13:03:38 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 3893 invoked by uid 99); 25 Apr 2012 13:03:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 13:03:38 +0000 X-ASF-Spam-Status: No, hits=4.7 required=5.0 tests=FREEMAIL_FORGED_REPLYTO,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [98.138.229.119] (HELO nm36-vm7.bullet.mail.ne1.yahoo.com) (98.138.229.119) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 25 Apr 2012 13:03:29 +0000 Received: from [98.138.90.50] by nm36.bullet.mail.ne1.yahoo.com with NNFMP; 25 Apr 2012 13:03:08 -0000 Received: from [98.138.89.166] by tm3.bullet.mail.ne1.yahoo.com with NNFMP; 25 Apr 2012 13:03:08 -0000 Received: from [127.0.0.1] by omp1022.mail.ne1.yahoo.com with NNFMP; 25 Apr 2012 13:03:08 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 516657.34053.bm@omp1022.mail.ne1.yahoo.com Received: (qmail 23962 invoked by uid 60001); 25 Apr 2012 13:03:08 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1335358988; bh=hM/YiEUEx7Oy5xI09Ll7JxUKURmKJZYe7+QY6IJITx8=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=Vp+IOg2olWWg4UR+6SKEiXS+oQ54P33x4vZTqtyj1z45FHBaBM//mB4SfEW8Jaxu8KP6qxeW5t9w/Ont3SZodlNZLc+cjqK5rJHFMoh4UXHo12bieeJDisEyrzcopordVMdWb8koP1MBh6RCgijB30sdJKeu9+ODGrdwWyc4A9E= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=VQIiSpKxmtKDiLs35VP+xIbw/WoaX4itbP/hElO9gqjpv3/2m/64pZgUC4ROlkCthN0RX8LcDXM01K67ntcqNWkqCazgIyfYgWWREn2ztAqQC4gNKXhevxGVKqjVFzPGuNbyvjw3Kow96qgXsuKN+JawpJzH8oLAtKPluRpeTZg=; X-YMail-OSG: AjS8zKUVM1nI4Poj8_WVB5ylUOYO1x.039w07Mpdr8YBJzb tbvcHqisNCtMeTRJGqmjqBzrZSCf_2hF4uBCG43VfurB1LOuQY3IN8dSwJ6A VAhKAAIvI0SBrViidCZaTdRxJtaO_6Kb4L5fV7JQh6qJYndv7CWbb2dPxZkY awlGjsyWUFF.m5b1UkOaSfBtQqC8CPAuqkf9T9ujjzUENZkLkFVxkX0C2NNo 4hQUXKU5y1NGsy21zXFw35DDA70yReckO_W5sw8mvg3xlKniqVpf47v6cafS icFoIm9m9yvxdbq4etqz3nmtpuDOYZyCdzYfou.xH7K3IbIKdvv0yEhNqe5b PloqPHm6falF.d918fDQn2VJX0eiJsKLlYwHm4uwYLuf.QpEuktCja2tqomL wGRlQEl3VTUvfkmpE7bZ_dp3atUwpWSYrqBrf5xttJzr3AON.o8Mqw.3dnaP d_4MLdNZMMTCTuRt7q7606jPW3eFA Received: from [129.33.1.37] by web125402.mail.ne1.yahoo.com via HTTP; Wed, 25 Apr 2012 06:03:08 PDT X-Mailer: YahooMailWebService/0.8.117.340979 References: <4F9185C6.6020203@oracle.com> <4F955021.6060603@oracle.com> <1335298744.13643.YahooMailNeo@web125405.mail.ne1.yahoo.com> <4F9715BD.3030005@sbcglobal.net> <1335318575.26724.YahooMailNeo@web125401.mail.ne1.yahoo.com> <4F97EEB8.5020909@oracle.com> Message-ID: <1335358988.94277.YahooMailNeo@web125402.mail.ne1.yahoo.com> Date: Wed, 25 Apr 2012 06:03:08 -0700 (PDT) From: Tomcat Programmer Reply-To: Tomcat Programmer Subject: Re: No Connection Exception To: Derby Discussion In-Reply-To: <4F97EEB8.5020909@oracle.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-108205657-331249839-1335358988=:94277" ---108205657-331249839-1335358988=:94277 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable >=0A> Derby engines and databases don't spontaneously reboot as far as I kn= ow. =0A=0A> This suggests that the engine and/or database are being bounced= by code =0A=0A> higher up your application stack.=0A=0A>=0A=0A=0AThanks Ri= ck. I=A0 certainly assume that they wouldn't normally do that. I was thinki= ng maybe there was a specific trigger situation that might cause it. I'm no= t sure what else could be in the software stack to cause this. The derby ve= rsion is 10.8.something (whatever was the most recent as of about a month a= go) and its started in Network mode listening only to localhost address.=A0= The Apache Tomcat 7 web container is on the same host, with a container-ma= naged connection pool, using the built-in Tomcat connection pool classes.= =A0 On top of that is eclipselink JPA 2.0.=A0 Certainly none of that is som= ething that I would expect to restart the database.=A0 The application does= n't have any code written directly against the database, everything goes th= rough JPA.=0A=0A=0A=0A=0A=0A=0A________________________________=0A From: Ri= ck Hillegas =0ATo: derby-user@db.apache.org =0ASe= nt: Wednesday, April 25, 2012 8:31 AM=0ASubject: Re: No Connection Exceptio= n=0A =0AOn 4/24/12 6:49 PM, Tomcat Programmer wrote:=0A> That is a very goo= d question... there is no error message at all.=A0 However, what I did see = was a startup message, like when the database initially starts. Except, I n= ever restarted it!=A0 And the machine did not reboot... are there ever cond= itions where it auto-restarts itself?=0A=0AHope this helps,=0A-Rick=0A> =0A= > =0A> --------------------------------------------------------------------= ----=0A> *From:* Katherine Marsden =0A> *To:* = Derby Discussion =0A> *Sent:* Tuesday, April 24, = 2012 5:06 PM=0A> *Subject:* Re: No Connection Exception=0A> =0A> On 4/24/20= 12 1:19 PM, Tomcat Programmer wrote:=0A>> Hello,=0A>> =0A>> =0A>> =0A>> The= only way to clear this up seems to be restarting the web container.=A0 Is= there some setting in Derby which is causing these connections to go stale= ?=A0 Is there any way to=0A>> trace this and find out the cause?=0A>> =0A> = Is there an interesting error in the derby.log that might indicate when you= lost the connection?=0A> =0A> =0A> ---108205657-331249839-1335358988=:94277 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
>
> Derby engines and databases don't spontaneously reboot a= s far as I know.
> This suggests that the engine and/or d= atabase are being bounced by code
> higher up your applic= ation stack.
>

Thank= s 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 d= erby 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 addr= ess.  The Apache Tomcat 7 web container is on the same host, with a co= ntainer-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.&nbs= p; The application doesn't have any code written directly against the datab= ase, everything goes through JPA.




Fr= om: Rick Hillegas <rick.hillegas@oracle.com>
To: derby-user@db.apache.org
<= b>Sent: Wednesday, April 25, = 2012 8:31 AM
Subject: = Re: No Connection Exception

=0AOn 4/24/12 6:49 PM, T= omcat 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!&nbs= p; And the machine did not reboot... are there ever conditions where it aut= o-restarts itself?

Hope this helps,
-Rick
>
>
&g= t; ------------------------------------------------------------------------=
> *From:* Katherine Marsden <kmarsdenderby@sbc= global.net>
> *To:* Derby Discussion <derby-us= er@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 som= e 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 indica= te when you lost the connection?
>
>
>



=
---108205657-331249839-1335358988=:94277--