This is what I found in the Tomcat log, and I guess that this is the last
thing that happened before the IIS-Tomcat connection stopped working.
2006-10-16 23:20:29 [EMAIL PROTECTED]:
Exception Processing ErrorPage[errorCode=404, location=/index.jsp]
ClientAbortException: java.net.SocketException: Software caused connection
abort: socket write error
at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java
:373)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:398)
at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:315)
at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:297)
at org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.java
:537)
at org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(
CoyoteResponseFacade.java:238)
at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java
:303)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:147)
at org.apache.catalina.core.StandardValveContext.invokeNext(
StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(
StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java
:520)
at org.apache.catalina.core.StandardEngineValve.invoke(
StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(
StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java
:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java
:675)
at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
2006-10-16 23:20:30 [EMAIL PROTECTED]:
Exception Processing ErrorPage[errorCode=404, location=/index.jsp]
ClientAbortException: java.net.SocketException: Software caused connection
abort: socket write error
at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java
:373)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:398)
at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:315)
at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:297)
at org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.java
:537)
at org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(
CoyoteResponseFacade.java:238)
at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java
:303)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:147)
at org.apache.catalina.core.StandardValveContext.invokeNext(
StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(
StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java
:520)
at org.apache.catalina.core.StandardEngineValve.invoke(
StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(
StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java
:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java
:675)
at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
The config files for AJP are s follows:
worker.ajp15w.type=ajp13
worker.ajp15w.host=xx.xx.xx.xx
worker.ajp15w.port=8009
worker.ajp15w.socket_keepalive=True
worker.ajp15w.socket_timeout=60
#Default connection_pool_size is 10
And from server.xml:
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<Connector port="8009"
enableLookups="false" redirectPort="8443" debug="0"
protocol="AJP/1.3" maxProcessors="150" />
We will try increasing the connection_pool_size to 20, although this seems
like a long shot (there is virtually no traffic).
Could the (redundant) worker.ajp15w.socket_timeout=60 be a problem?
Kind regards,
Peter Olin
2006/10/16, Mladen Turk <[EMAIL PROTECTED]>:
Peter Olin wrote:
> This is what the log says:
>
> [Fri Oct 13 13:08:09 2006] [5788:13544] [error] jk_ajp_common.c (947):
> (ajp15w) can't receive the response message from tomcat, network
> problems or
> tomcat is down (xx.xx.xx.xx:8009), err=-54
This means that Tomcat has closed the AJP connection in the
middle of response.
There must be something in the Tomcat log explaining why
did this happen.
Regards,
Mladen.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Peter Olin
