Costin Manolache wrote:
Remy Maucherat wrote:
Rainer Jung wrote:
Am I right, that by design TC 5 only fully supports one Coyote JK pool at the moment?
I enabled JMX HTTP adaptor via mx.enabled=true. Obviously org.apache.jk.common.JkMX tries to initialize the JMX HTTP adaptor not only once, but for every Coyote JK pool configured in server.xml. For the second pool I get an exception when starting tomcat (see below).
When trying to stop TC, the Coyote HTTP pool is shut down correctly, and one of the two JK pools doesn't listen any more, but the second JK pool still listens and TC does not shut down. Retrying shutdown does not help, the process is still alive.
Any plans (or work already done) to refactor JkMain/JkMX for 5.next?
Yes: use JDK 1.5 JMX instead of this code.
Are we going to switch to JDK1.5 ???
I missed this one.
Actually, I posted that we could consider switching to JDK 1.5, yes (I do really like that JDK). The idea is that I'm tweaking the API, so I would use the new stuff when rewriting code. I don't think it'll happen in the end, since not many people seem to be in favor of it.
Here, I was mentioning that using JDK 1.5 would be a workaround (as the connector registration moves out of the JVM).
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
