Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 81417 invoked from network); 22 Aug 2006 16:54:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Aug 2006 16:54:46 -0000 Received: (qmail 55400 invoked by uid 500); 22 Aug 2006 16:54:43 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 55374 invoked by uid 500); 22 Aug 2006 16:54:43 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 55340 invoked by uid 99); 22 Aug 2006 16:54:43 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Aug 2006 09:54:43 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Aug 2006 09:54:41 -0700 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1GFZW9-000614-6v for activemq-users@geronimo.apache.org; Tue, 22 Aug 2006 09:54:21 -0700 Message-ID: <5929474.post@talk.nabble.com> Date: Tue, 22 Aug 2006 09:54:21 -0700 (PDT) From: dege To: activemq-users@geronimo.apache.org Subject: Re: derby db failing on restart In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <5914237.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Attached is the application log with debugging turned on At line 1657 is where resin starts to unload and then reload the application context as a result of deploying an updated class file to the webapps WEB-INF/classes directory. I looked at the derby.log and it is empty. In terms of configuration we use the org.springframework.web.context.ContextLoaderListener which loads our context file on startup. This context file in turn loads a local broker the config file looks like the following: We also setup a some message driven pojo's pointing to a remote broker that isn't up which is why you see all the other connect errors. In development this is hardly ever up unless we are working on that part of the application. -- View this message in context: http://www.nabble.com/derby-db-failing-on-restart-tf2142524.html#a5929474 Sent from the ActiveMQ - User forum at Nabble.com.