Hi Marcus, >> idle connections running for hours and hours That was our problem as well, with those idle connections just sitting there, as I said, I wasn't sure if my solution was the correct one.. Just telling you, it seemed to work for us. I would say give it a try, the only issue we have, is a large amount of log messages in catalina.out about the timeouts. For some reason I can't get the default java.util.logging to catch them.
-Rick -----Original Message----- From: Marcus Franke [mailto:[EMAIL PROTECTED] Posted At: Thursday, October 06, 2005 4:11 AM On Wed, Oct 05, 2005 at 04:24:08PM -0700, Rick wrote: > We had an issue where it seemed like it would crash using mod_jk, the > trouble was the connections were not letting go. By default, I think > the timeout is infinite, so after setting the property: > connectionTimeout, in the server.xml's connector descriptor as > follows, > > <Connector port="nnnn" protocol=""AJP/1.3" connectionTimeout="60000" > .../> > > The old connections would get cleaned up and we stopped having > problems, however, I'm not sure this was the "correct" way to do this, seems to work. > Hi, but concerning to the documentation connectionTimeout is the amount of time between opening the session and receiving the URI to process. So your connector would wait 60 seconds for an empty request before it would cut off the connection. I for example have the interesting behaviour that I have idle connections running for hours and hours which I would like to end but do not know how. Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
