You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Ori Tend <or...@fetchbook.info> on 2003/03/13 11:39:28 UTC
mod_jk2 errors
Hi,
I'm sorry I'm posting this to the dev group- but i've tried looking for
answers in any corner of the universe...
im using mod_jk2, tomcat 4.1.18 and apache2.
I'm getting tons of these errors in my apache2 error_log. also, 1 of
every 100 requests handled by tomcat returns 500 error.
Also, from system resources perspective, tomcat is not working hard at
all.
Is anyone familiar with that?
I hope someone saw this before....
Ori.
[Thu Mar 13 01:52:20 2003] [error] channelSocket.receive(): Error
receiving message body -1 2
[Thu Mar 13 01:52:20 2003] [error] workerEnv.processCallbacks() Error
reading reply
[Thu Mar 13 01:52:20 2003] [error] ajp13.service() ajpGetReply
recoverable error 120000
[Thu Mar 13 01:52:22 2003] [error] Error ajp_process_callback - write
failed
[Thu Mar 13 01:52:22 2003] [error] ajp13.service() ajpGetReply
unrecoverable error 3
[Thu Mar 13 01:52:22 2003] [error] ajp13.service() Error forwarding
ajp13:localhost:8009 0 1
[Thu Mar 13 01:52:22 2003] [error] mod_jk.handler() Error connecting to
tomcat 120000
[Thu Mar 13 01:52:36 2003] [error] channelSocket.receive(): Error
receiving message body -1 2
[Thu Mar 13 01:52:36 2003] [error] workerEnv.processCallbacks() Error
reading reply
[Thu Mar 13 01:52:36 2003] [error] ajp13.service() ajpGetReply
recoverable error 120000
[Thu Mar 13 01:52:40 2003] [error] channelSocket.receive(): Error
receiving message body -1 2
[Thu Mar 13 01:52:40 2003] [error] workerEnv.processCallbacks() Error
reading reply
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: mod_jk2 errors
Posted by Ori Tend <or...@fetchbook.info>.
Thanks so much for the reply, Costin. The last week has been very
frustrating ... :-)
I'm using linux 2.4.18-3smp #1. Tomcat gets approx 2 requests / sec.
In terms of cpu, the tomcat load is negligible (can't really see a cpu
spike).
On catalina.out I see many (every 5 seconds or so) of the following:
Mar 11, 2003 11:39:17 PM org.apache.jk.common.ChannelSocket
processConnection
INFO: connection timeout reached
Mar 11, 2003 11:39:20 PM org.apache.jk.common.ChannelSocket
processConnection
INFO: server has been restarted or reset this connection
And also every now and then I get broken pipe exception:
Mar 12, 2003 1:45:24 AM org.apache.jk.server.JkCoyoteHandler action
SEVERE: Error in action code
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at
java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435)
at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627)
at
org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372)
at org.apache.coyote.Response.action(Response.java:222)
at org.apache.coyote.Response.finish(Response.java:343)
at
org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326)
at
org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.j
ava:500)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224)
at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261)
at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360)
at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:
590)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:530)
at java.lang.Thread.run(Thread.java:536)
In general, Costin, would you recommend to downgrade to mod_jk or to
upgrade to latest cvs version?
Also, would any of these errors justify a 500 response code
(intuitively, sounds like only the "unrecoverable" errors should) ?
Thanks,
Ori.
-----Original Message-----
From: news [mailto:news@main.gmane.org] On Behalf Of Costin Manolache
Sent: Thursday, March 13, 2003 8:35 PM
To: tomcat-dev@jakarta.apache.org
Subject: Re: mod_jk2 errors
What OS ?
I added strerror - so if you update you may get better error number on
"receiving message body".
Regarding ajp_process_callback: that's most likely a user hiting "BREAK"
on the browser. I downgraded the message to debug, it is a normal case.
How loaded is tomcat ( number of requests per second, waiting
requests, etc)?
Ori Tend wrote:
> Hi,
>
> I'm sorry I'm posting this to the dev group- but i've tried looking
> for answers in any corner of the universe... im using mod_jk2, tomcat
> 4.1.18 and apache2. I'm getting tons of these errors in my apache2
> error_log. also, 1 of every 100 requests handled by tomcat returns 500
> error. Also, from system resources perspective, tomcat is not working
> hard at all.
>
> Is anyone familiar with that?
>
> I hope someone saw this before....
>
> Ori.
>
> [Thu Mar 13 01:52:20 2003] [error] channelSocket.receive(): Error
> receiving message body -1 2 [Thu Mar 13 01:52:20 2003] [error]
> workerEnv.processCallbacks() Error reading reply
> [Thu Mar 13 01:52:20 2003] [error] ajp13.service() ajpGetReply
> recoverable error 120000
This kind of message indicates a recoverable communication problem.
Something went wrong, so it reconnected.
It shouldn't happen very frequently.
Do you see any errors on tomcat side ?
> [Thu Mar 13 01:52:22 2003] [error] Error ajp_process_callback - write
> failed [Thu Mar 13 01:52:22 2003] [error] ajp13.service() ajpGetReply
> unrecoverable error 3
> [Thu Mar 13 01:52:22 2003] [error] ajp13.service() Error forwarding
> ajp13:localhost:8009 0 1
> [Thu Mar 13 01:52:22 2003] [error] mod_jk.handler() Error connecting
to
> tomcat 120000
I'll debug a bit more on this - it shouldn't generate any message, it's
a normal case.
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: mod_jk2 errors
Posted by Costin Manolache <cm...@yahoo.com>.
What OS ?
I added strerror - so if you update you may get better error number on
"receiving message body".
Regarding ajp_process_callback: that's most likely a user hiting "BREAK"
on the browser. I downgraded the message to debug, it is a normal case.
How loaded is tomcat ( number of requests per second, waiting
requests, etc)?
Ori Tend wrote:
> Hi,
>
> I'm sorry I'm posting this to the dev group- but i've tried looking for
> answers in any corner of the universe...
> im using mod_jk2, tomcat 4.1.18 and apache2.
> I'm getting tons of these errors in my apache2 error_log. also, 1 of
> every 100 requests handled by tomcat returns 500 error.
> Also, from system resources perspective, tomcat is not working hard at
> all.
>
> Is anyone familiar with that?
>
> I hope someone saw this before....
>
> Ori.
>
> [Thu Mar 13 01:52:20 2003] [error] channelSocket.receive(): Error
> receiving message body -1 2
> [Thu Mar 13 01:52:20 2003] [error] workerEnv.processCallbacks() Error
> reading reply
> [Thu Mar 13 01:52:20 2003] [error] ajp13.service() ajpGetReply
> recoverable error 120000
This kind of message indicates a recoverable communication problem.
Something went wrong, so it reconnected.
It shouldn't happen very frequently.
Do you see any errors on tomcat side ?
> [Thu Mar 13 01:52:22 2003] [error] Error ajp_process_callback - write
> failed
> [Thu Mar 13 01:52:22 2003] [error] ajp13.service() ajpGetReply
> unrecoverable error 3
> [Thu Mar 13 01:52:22 2003] [error] ajp13.service() Error forwarding
> ajp13:localhost:8009 0 1
> [Thu Mar 13 01:52:22 2003] [error] mod_jk.handler() Error connecting to
> tomcat 120000
I'll debug a bit more on this - it shouldn't generate any message, it's a
normal case.
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org