Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Sat, 22 Oct 2005 20:24:28 -0400
From: Eric Lenio <eric@lenio.net>
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: AntiGC Not Shutting Down
Message-ID: <20051023002428.GA13123@lenio.net>
References: <20051022235910.5006D10FB2C3@asf.osuosl.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051022235910.5006D10FB2C3@asf.osuosl.org>
User-Agent: Mutt/1.5.10i

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.

On Sat, Oct 22, 2005 at 06:58:49PM -0500, Samer Kanjo wrote:
>    I am running Derby server inside my web application which is running
>    in Tomcat 5. I need to run Derby as a server in order to allow batch
>    processes and the web application to access the database. What I have
>    discovered is that shutting down Derby from within my web application
>    does not completely shutdown Derby, the AntiGC thread continues to
>    run.
> 
> 
>    I checked the mailing list archives and found no references to AntiGC.
>    I then checked the derby bugs list and found bug 23 which indicated a
>    memory leak and a suggested fix that was applied. However the bug has
>    been re-opened due to continuing problems. The problems that were
>    identified had to do with the embedded driver. I wanted to mention
>    that I am having problems with the server as well. I was previously
>    using 10.1.1.0 and switched to 10.1.1.1 due to the patch but found
>    that the problem did in fact persist.
> 
> 
>    When I do shutdown Derby the following 2 threads remain:
> 
>    Thread [derby.antiGC] (Running)
> 
>    Thread [derby.rawStoreDaemon] (Running)
> 
> 
>    When Derby is running I see the following threads:
> 
>    Thread [derby.NetworkServerStarter] (Running)
> 
>    Thread [Thread-40] (Running)
> 
>    Thread [DRDAConnThread_41] (Running)
> 
>    Thread [derby.antiGC] (Running)
> 
>    Thread [derby.rawStoreDaemon] (Running)
> 
> 
> 
>    So far the only consequences of this problem for me are the inability
>    to remotely shutdown the application and redeploy using the Tomcat
>    Manager.