We are using the defaults for both the Tomcat AJP listener and mod_jk in Apache.
No errors in the mod_jk logs. No errors in the apache error logs. We had issues with the timeouts because frequently the midtier did not respond in the time allotted, so the connection was severed; this caused all kinds of issues with the midtier session tracking and other things. On Tue, Jul 27, 2010 at 3:16 AM, John Baker <[email protected]>wrote: > Axton, > > This exception: > > RuntimeExceptionjava.lang.IllegalStateException > at > > org.apache.catalina.connector.ResponseFacade.sendRedirect(ResponseFacade.java:435) > > Can occur when Tomcat tries to write to a stream that has been closed - > perhaps mod_jk is not configured correctly? I would suggest you look at > the connection_pool_timeout attribute in the workers.properties, and the > connectionTimeout attribute on the AJP Connector within Tomcat's > server.xml file. > > connection_pool_timeout: Specify a value in seconds. > connectionTimeout: Specify a value in milliseconds. > > Both values must be the same (i.e. 60 on connection_pool_timeout, and > 60000 on connectionTimeout). > > You may also wish to set the socket_timeout in workers.properties to a > higher value if it's set (not set means 'wait forever', I believe). > > > John > > -- > Java System Solutions > http://www.javasystemsolutions.com/jss/ssoplugin > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
