Re: jk 1.2.6 and Tomcat 3.3.2
- Original Message -
From: Henri Gomez [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 11:55 PM
Subject: Re: jk 1.2.6 and Tomcat 3.3.2
The code in 3.3.2 was :
Nov 17, 2004 8:42:25 AM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
in org.apache.jk.common.HandlerRequest :
public int invoke(Msg msg, MsgContext ep )
throws IOException
{
int type=msg.getByte();
default:
log.info(Unknown message + type);
}
return OK;
}
It seems we grab a byte from AJP link which is zero (0x00) but it's
not a valid AJP command so there is something weird there. Any idea ?
Mladen, JF, Bill ?
As I said, the ChannelSocket code for 3.3.2 is buggy. The above is called
from line 653 of ChannelSocket by:
MsgAjp endM = new MsgAjp();
endM.reset();
endM.appendByte((byte)HANDLE_THREAD_END);
next.invoke(endM, ep);
which is wrong (and results in type == 0 :). Back then, the JMX Request
registration was the responsibility of HandlerRequest. This design proved
unworkable, so in CVS HEAD it is now the responsibility of Channel*.
However, without JMX enabled, the only thing that this bug does is to print
a message to the log :). If you want to find out more about why the
connection is dropping, you'll probably have to log ChannelSocket at DEBUG
level.
On Wed, 17 Nov 2004 08:46:11 +0100, Henri Gomez [EMAIL PROTECTED]
wrote:
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]
This message is intended only for the use of the person(s) listed above as the
intended recipient(s), and may contain information that is PRIVILEGED and
CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or
distribute this message or any attachment. If you received this communication
in error, please notify us immediately by e-mail and then delete all copies of
this message and any attachments.
In addition you should be aware that ordinary (unencrypted) e-mail sent through
the Internet is not secure. Do not send confidential or sensitive information,
such as social security numbers, account numbers, personal identification
numbers and passwords, to us via ordinary (unencrypted) e-mail.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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. Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk 1.2.6 and Tomcat 3.3.2
- 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. Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk 1.2.6 and Tomcat 3.3.2
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]
Re: jk 1.2.6 and Tomcat 3.3.2
The code in 3.3.2 was :
Nov 17, 2004 8:42:25 AM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
in org.apache.jk.common.HandlerRequest :
public int invoke(Msg msg, MsgContext ep )
throws IOException
{
int type=msg.getByte();
default:
log.info(Unknown message + type);
}
return OK;
}
It seems we grab a byte from AJP link which is zero (0x00) but it's
not a valid AJP command so there is something weird there. Any idea ?
Mladen, JF, Bill ?
On Wed, 17 Nov 2004 08:46:11 +0100, Henri Gomez [EMAIL PROTECTED] wrote:
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]
