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
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
Rick,
Thanks for the info. I will try it out.
It is interesting when I look at the config for all of the other
Connectors, they all have a connectionTimeout value.
-John
On Oct 5, 2005, at 7:24 PM, Rick wrote:
We had an issue where it seemed like it would crash using mod_jk, the
trouble
set?
-Rick
-Original Message-
From: John Martyniak [mailto:[EMAIL PROTECTED]
Posted At: Thursday, October 06, 2005 8:43 AM
Posted To: Tomcat Dev
Conversation: Modjk and Tomcat 5.5.4 problem
Subject: Re: Modjk and Tomcat 5.5.4 problem
Rick,
Thanks for the info. I will try it out
, cachesize, or
cache_timeout
set?
-Rick
-Original Message-
From: John Martyniak [mailto:[EMAIL PROTECTED]
Posted At: Thursday, October 06, 2005 8:43 AM
Posted To: Tomcat Dev
Conversation: Modjk and Tomcat 5.5.4 problem
Subject: Re: Modjk and Tomcat 5.5.4 problem
Rick,
Thanks
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=
