----- Original Message ----- From: "Henri Gomez" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, April 06, 2004 5:08 AM Subject: Re: Problems with stress tested apps
> Henri Gomez wrote: > > > Henri Gomez wrote: > > > >> Hi to all, > >> > >> I've got problems with some highly stressed applications using jk or jk2 > >> and tomcat 3.3.2 (same thing with TC 5.0.x). > >> > >> I see many errors like these in log : > >> > >> in TC 3.3.2 and 5.0.19 : > >> > >> Mar 19, 2004 1:47:51 PM org.apache.jk.common.HandlerRequest invoke > >> INFO: Unknown message 0 > >> > >> > >> in 5.0.19 I've got also : > >> > >> Mar 19, 2004 1:47:51 PM org.apache.jk.common.HandlerRequest decodeRequest > >> WARNING: Error registering request > >> > >> > >> There is something weird in jtc, since the INFO: Unknown message 0 > >> indicate that there is an invalid command on the AJP13 link. > >> > >> The problem appears with both jk and jk2, so I suspect the problem > >> to be on the java side. > >> > >> I'm investigating the problem. > >> > >> > > > > While playing with TC 3.3.3-dev and JTC-dev, I didn't see (yet), the > > INFO: Unknown message 0 but got some : > > > > 6 avr. 2004 08:46:37 org.apache.jk.common.ChannelSocket processConnection > > GRAVE: Error, releasing connection > > java.lang.NullPointerException > > at > > org.apache.coyote.RequestInfo.setGlobalProcessor(RequestInfo.java:52) > > at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:427) > > at > > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:659) > > > > at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:807) > > at > > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:644) > > > > at java.lang.Thread.run(Thread.java:534) > > With the latest TC 3.3.3-dev, I didn't get the : > > Mar 19, 2004 1:47:51 PM org.apache.jk.common.HandlerRequest invoke > INFO: Unknown message 0 > This is BZ #27881. With 3.3.2 (unless you JMX-register the CoyoteConnector yourself :) it doesn't do anything except fill up your log file when threads die. Of course, you can always swap in the JK jar from 5.0.21 if you don't want to see the message. > And didn't see either the java.lang.NullPointerException in > org.apache.coyote.RequestInfo.setGlobalProcessor(RequestInfo.java:52) > > Good for TC 5.0.22 ;) > > > > --------------------------------------------------------------------- > 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]
