Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 56673 invoked from network); 14 Apr 2009 20:07:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Apr 2009 20:07:08 -0000 Received: (qmail 76545 invoked by uid 500); 14 Apr 2009 20:07:07 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 76447 invoked by uid 500); 14 Apr 2009 20:07:07 -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 76439 invoked by uid 99); 14 Apr 2009 20:07:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Apr 2009 20:07:07 +0000 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 (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Apr 2009 20:06:58 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Ltotx-0005EY-3P for derby-user@db.apache.org; Tue, 14 Apr 2009 13:06:37 -0700 Message-ID: <23046970.post@talk.nabble.com> Date: Tue, 14 Apr 2009 13:06:37 -0700 (PDT) From: pawan2009 To: derby-user@db.apache.org Subject: Derby take a long time to start MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: psingh@fnfr.com X-Virus-Checked: Checked by ClamAV on apache.org Hi We are seeing that occasionally, when our application starts (it uses derby to store data), derby database can be connected to quickly - but on the very first query to the database, it takes a long time for derby to come back and respond. It is as if derby is doing some house work recovering data or indexing or something. If we let our application run for 20-30 minutes, the query does complete and after that everything works fine. We see it only occasionally. Any ideas on what could be causing this? -- View this message in context: http://www.nabble.com/Derby-take-a-long-time-to-start-tp23046970p23046970.html Sent from the Apache Derby Users mailing list archive at Nabble.com.