xom-interest AT lists.ibiblio.org
Subject: XOM API for Processing XML with Java
List archive
- From: Jeroen van Maanen <jeroen AT entreact.com>
- To: xom-interest AT lists.ibiblio.org
- Subject: [XOM-interest] Cleaning up sweeper thread
- Date: Wed, 17 Jan 2007 00:00:35 +0100
I am using XOM and Nux to build a web application that uses XSLT transformations heavily.
Recently I tried to clean up all the stuff that was still lying around after redeploying the application (the application spawns a lot of threads so I implemented close() methods on the owners of those threads to stop them).
The only thread that I cannot get rid of, is the sweeper thread that is constructed in nux.xom.pool.Pool that clears invalid entries from all pools.
Of course it would help to move nux.jar to the common or shared directory of Tomcat, but I'd rather keep everything in one war file. Another possibility I thought of was to initialize the pool in a thread group that is specific to the application and use the deprecated stop() method to kill it. My last option is to patch nux.xom.Pool either with a static close() method or with a separate sweeper for each pool instance.
Any advice on which direction to take would be appreciated.
Jeroen
-
[XOM-interest] Cleaning up sweeper thread,
Jeroen van Maanen, 01/16/2007
- <Possible follow-up(s)>
-
[XOM-interest] Cleaning up sweeper thread,
Jeroen van Maanen, 01/16/2007
-
Re: [XOM-interest] Cleaning up sweeper thread,
Wolfgang Hoschek, 01/16/2007
- Re: [XOM-interest] Cleaning up sweeper thread, Steve Loughran, 01/17/2007
-
Re: [XOM-interest] Cleaning up sweeper thread,
Wolfgang Hoschek, 01/16/2007
Archive powered by MHonArc 2.6.24.