tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Gomez <hgo...@apache.org>
Subject Re: Problems with stress tested apps
Date Wed, 07 Apr 2004 06:26:24 GMT
Bill Barker wrote:
> ----- Original Message -----
> From: "Henri Gomez" <hgomez@apache.org>
> To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
> 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.

Thanks Bill.

I made a TC 3.3.3-dev from the CVS and it seems to works great (add 
since it has been build with common-modeler, more JMX support is included).


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message