tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Deneen" <mden...@gmail.com>
Subject Re: Tomcat 6.0.10 problems with httpd 2.2.4 and mod_proxy_ajp
Date Thu, 17 May 2007 20:52:39 GMT
I just wanted to let anyone else who has experienced this problem that
it appears mod_jk works without any issue at all.  mod_proxy_http
would occasionally corrupt the output stream.  We would see random hex
values sprinkled throughout the servlet response.

Anyway, mod_jk is the winner for now.

Mark

On 5/16/07, Mark Deneen <mdeneen@gmail.com> wrote:
> Hi, I have experienced some issues using mod_proxy_ajp and Tomcat
> 6.0.10 under moderate load.  Occasionally I receive an error 503 in my
> browser when the webapp when we have around 30 - 40 users connected.
>
> First off, here is what I see in our logs:
>
> httpd error_log:
> [Tue May 15 17:45:02 2007] [error] ajp_check_msg_header() got bad signature 420
> [Tue May 15 17:45:02 2007] [error] ajp_ilink_receive() received bad header
> [Tue May 15 17:45:02 2007] [error] ajp_read_header: ajp_ilink_receive failed
> [Tue May 15 17:45:02 2007] [error] (120007)APR does not understand
> this error code: proxy: read response failed from 127.0.0.1:20021
> (localhost)
>
>
> tomcat 6.0.10 catalina.out:
> May 15, 2007 5:45:02 PM org.apache.jk.core.MsgContext action
> WARNING: Error sending end packet
> java.net.SocketException: Connection reset
>         at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96)
>         at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
>         at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531)
>         at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121)
>         at org.apache.jk.core.MsgContext.action(MsgContext.java:301)
>         at org.apache.coyote.Response.action(Response.java:183)
>         at org.apache.coyote.Response.finish(Response.java:305)
>         at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276)
>         at org.apache.catalina.connector.Response.finishResponse(Response.java:486)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:232)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
>         at java.lang.Thread.run(Thread.java:619)
> May 15, 2007 5:45:02 PM org.apache.jk.common.ChannelSocket processConnection
> WARNING: processCallbacks status 2
>
> Apache is running with the prefork MPM, with MaxClients set at the
> default 256.  The AJP connector in Tomcat is configured with
> MaxThreads="175"
>
> For now, I am using mod_proxy_http and have apache connect to the
> Tomcat http connector.  This works well, but I would like to
> understand the issue with the AJP connector.  Any ideas?  Should I use
> mod_jk?
>
> The server is running Centos 4.4 x86_64.
>
> Best Regards,
> Mark Deneen
>

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message