Bill Barker wrote: > I know that at one point there was a problem if you enabled the JMX consol > (e.g. set mx.port=9000 in jk2.properties). I don't remember if that's > been fixed.
I think the bug was in our code - i.e. we didn't call stop. I remember fixing it in jk, if you start the adapter using jk2.properties it should work. Costin > > But the short answer is, yes the HttpAdapter creates non-daemon threads. > > ----- Original Message ----- > From: "Tim Funk" <[EMAIL PROTECTED]> > To: "Tomcat Developers List" <[EMAIL PROTECTED]> > Sent: Thursday, June 05, 2003 2:12 PM > Subject: Re: [5.0] More dependencies > > >> When I was testing with the HttpAdapter and Sun's JMX 1.2ri, on shutdown > of >> tomcat the JVM did not die. If I removed the jar - all was OK. (But of > course >> I lost HttpAdapter functionality) Does anyone know if Sun's HttpAdapter >> creates non-daemon threads? Of course the problem might be in tomcat too, > I'm >> sorry for not doing much debugging on this yet. >> >> Unfortunately, I was using cygwin and you can't get JVM stacktraces with > cygwin. >> >> Time permitting, I will try testing this on linux box tonight to see what >> threads are keeping the JVM alive. (Or *gasp* - go back to using the bat > files) >> >> -Tim >> >> Remy Maucherat wrote: >> > >> > JMX: I think we should try to ship with JMX 1.2 + a JSR 160 >> > implementation if possible. I really hope MX4J will be able to provide >> > that. >> > >> > >> > Remy >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
