Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 57194 invoked from network); 24 Oct 2005 13:29:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Oct 2005 13:29:43 -0000 Received: (qmail 36162 invoked by uid 500); 24 Oct 2005 13:29:41 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 36134 invoked by uid 500); 24 Oct 2005 13:29:40 -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 36123 invoked by uid 99); 24 Oct 2005 13:29:40 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [24.24.2.56] (HELO ms-smtp-02.nyroc.rr.com) (24.24.2.56) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Oct 2005 06:29:40 -0700 Received: from mail.lenio.net (cpe-66-67-219-192.rochester.res.rr.com [66.67.219.192]) by ms-smtp-02.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id j9ODTGDK009613; Mon, 24 Oct 2005 09:29:16 -0400 (EDT) Received: by mail.lenio.net (Postfix, from userid 500) id 436E845D3B5; Mon, 24 Oct 2005 09:29:16 -0400 (EDT) Date: Mon, 24 Oct 2005 09:29:16 -0400 From: Eric Lenio To: Derby Discussion Cc: Knut Anders Hatlen Subject: Re: AntiGC Not Shutting Down Message-ID: <20051024132916.GA29923@lenio.net> References: <20051022235910.5006D10FB2C3@asf.osuosl.org> <20051023002428.GA13123@lenio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Mon, Oct 24, 2005 at 10:54:37AM +0200, Knut Anders Hatlen wrote: > Eric Lenio writes: > > > I have a similar setup as you, and previously I had witnessed similar > > behavior with AntiGC. I recommend this link if you haven't already seen > > it: > > > > http://www-128.ibm.com/developerworks/db2/library/techarticle/dm-0508bader/ > > > > Be especially sure to put derby.jar in the correct path. In my case the > > AntiGC thread issue went away when derby.jar was placed in > > tomcat/common/lib (like the above article states in the "casual > > scenario" section). The embedded and network drivers worked perfectly > > after I did this. Hope this helps. > > Hi Eric, > > Are you running the official Apache Derby 10.1.1.0 or the patched > version I sent you? > Hi Knut, yes I am indeed using your patched version which has run very stable for me. I've been stress testing my Tomcat application for several weeks now without having to restart Tomcat or Derby even once, whereas before I had to restart several times per hour during heavy development. I would also add that there *may* be another thread issue with DRDAConnThread, I've been monitoring Tomcat with Jconsole for a while now and these types of threads seem to be growing (I've got 11 right now, but haven't touched the database in 24 hours). I have no idea about what DRDAConnThread even does, so maybe what I am witnessing is normal. Eric.