It looks like a more recent version of GeronimoWorkMnaager shuts down its thread pools in the doStop method - see here: http://www.docjar.com/html/api/org/apache/geronimo/connector/work/GeronimoWorkManager.java.html
Are there any plans to upgrade the the version of geronimo-connector that Jencks 2.1 depends on? I'm more than happy to assist if needed... Cheers, Jerry On Wed, Feb 27, 2008 at 8:55 PM, JerryShea <[EMAIL PROTECTED]> wrote: > > Hi, > > I've cut and pasted the jencks JCA config from > http://jencks.org/Message+Driven+POJOs and if I use it like this: > AbstractApplicationContext ctx = new > ClassPathXmlApplicationContext(new > String[] { > "/spring-jencks.xml", > }); > Thread.sleep(3000); > ctx.destroy(); > > after the spring application context has been created, a number of threads > are started up (JCAContainer.afterPropertiesSet creates a Geronimo work > manager which in turn creates a thread pool). > > When ctx.destroy is called, JCAContainer.destroy gets called which in turn > calls geronimoWorkManager.doStop() which does... nothing! > > Shouldn't something be shutting down the thread pool? The threads that are > created remain alive and prevent my application from closing down. > > Thx, Jerry > > -- > View this message in context: > http://www.nabble.com/Jencks-Message-driven-POJOS-threads-left-running-after-ctx.destroy-tp15709825p15709825.html > Sent from the jencks - user mailing list archive at > Nabble.com<http://nabble.com/> > . > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
