On Tue, 16 Nov 2004 10:09:44 -0800, Bill Barker <[EMAIL PROTECTED]> wrote: > > > > ----- Original Message ----- > From: "Henri Gomez" <[EMAIL PROTECTED]> > To: "Discussion about Tomcat dev" <[EMAIL PROTECTED]> > Sent: Tuesday, November 16, 2004 4:42 AM > Subject: jk 1.2.6 and Tomcat 3.3.2 > > > Hi to all, > > > > I wonder if some of you still get this message in Tomcat 4.1.x and > 5.0.x/5.5.x : > > > > XXX unknowon type 0 > > > > I'm using Apache 2.0.50 and Tomcat 3.3.2 with jk 1.2.6 and got this > > message sometimes. > > > > As result Tomcat close the AJP connection and jk should recreate a new > socket. > > > > Actually, the message is when Tomcat is going to otherwise close the AJP > connection anyway, and is attempting to unregister the Request with JMX > (which has to be explicitly enabled in 3.3.2). Of course, you can make it > go away by grabbing the Jk jars from a more recent release of 4.1.x or 5.x, > but the message is pretty harmless itself.
Strange I didn't set JMX support in my tomcat 3.3.2 settings. no modules, nothing in server.xml or modules.xml. Also I wonder why Tomcat close the AJP connection from its own initiative since Apache 2 didn't ask for (it seems). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
