Re: Modjk and Tomcat 5.5.4 problem
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= protocol=AJP/1.3 connectionTimeout=6 .../ 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]
RE: Modjk and Tomcat 5.5.4 problem
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= protocol=AJP/1.3 connectionTimeout=6 .../ 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]
Re: Modjk and Tomcat 5.5.4 problem
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 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= protocol=AJP/1.3 connectionTimeout=6 .../ 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. Not sure if this is related to your problem. -Rick -Original Message- From: John Martyniak [mailto:[EMAIL PROTECTED] Posted At: Wednesday, October 05, 2005 3:53 PM Posted To: Tomcat Dev Conversation: Modjk and Tomcat 5.5.4 problem Subject: Modjk and Tomcat 5.5.4 problem Has anyone had any problems with ModJK crashing the server? I haven't been able to fully debug yet, primarily because it doesn't update any logs to state there is a problem, and I can't reliably replicate the problem. I am using Apache 2.0.47, modjk 1.2.5 and tomcat 5.5.4 I think that it has something to do with modjk because when I go directly to the appserver the problem doesn't seem to exist. Any help would be greatly appreciated. Thank you, -John - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Modjk and Tomcat 5.5.4 problem
Hey John, I have been looking into this on my end as well, since I'm not fully satisfied that it's the proper solution. As a question, what does your Apache workers.properties file look like. Do you have any of the properties such as recycle_timeout, socket_timeout, 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 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 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= protocol=AJP/1.3 connectionTimeout=6 .../ 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. Not sure if this is related to your problem. -Rick -Original Message- From: John Martyniak [mailto:[EMAIL PROTECTED] Posted At: Wednesday, October 05, 2005 3:53 PM Posted To: Tomcat Dev Conversation: Modjk and Tomcat 5.5.4 problem Subject: Modjk and Tomcat 5.5.4 problem Has anyone had any problems with ModJK crashing the server? I haven't been able to fully debug yet, primarily because it doesn't update any logs to state there is a problem, and I can't reliably replicate the problem. I am using Apache 2.0.47, modjk 1.2.5 and tomcat 5.5.4 I think that it has something to do with modjk because when I go directly to the appserver the problem doesn't seem to exist. Any help would be greatly appreciated. Thank you, -John - 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] - 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]
Re: Modjk and Tomcat 5.5.4 problem
Rick, I have made the changes and was able to replicate the problem pretty quickly. And again no message in the mod_jk or catalina.out files. It turns out that my workers file has all of those properties. I am including it below. # Define worker using ajp13 worker.list=worker1, worker2 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=300 -John On Oct 6, 2005, at 12:01 PM, Rick wrote: Hey John, I have been looking into this on my end as well, since I'm not fully satisfied that it's the proper solution. As a question, what does your Apache workers.properties file look like. Do you have any of the properties such as recycle_timeout, socket_timeout, 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 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 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= protocol=AJP/1.3 connectionTimeout=6 .../ 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. Not sure if this is related to your problem. -Rick -Original Message- From: John Martyniak [mailto:[EMAIL PROTECTED] Posted At: Wednesday, October 05, 2005 3:53 PM Posted To: Tomcat Dev Conversation: Modjk and Tomcat 5.5.4 problem Subject: Modjk and Tomcat 5.5.4 problem Has anyone had any problems with ModJK crashing the server? I haven't been able to fully debug yet, primarily because it doesn't update any logs to state there is a problem, and I can't reliably replicate the problem. I am using Apache 2.0.47, modjk 1.2.5 and tomcat 5.5.4 I think that it has something to do with modjk because when I go directly to the appserver the problem doesn't seem to exist. Any help would be greatly appreciated. Thank you, -John - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Modjk and Tomcat 5.5.4 problem
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= protocol=AJP/1.3 connectionTimeout=6 .../ 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. Not sure if this is related to your problem. -Rick -Original Message- From: John Martyniak [mailto:[EMAIL PROTECTED] Posted At: Wednesday, October 05, 2005 3:53 PM Posted To: Tomcat Dev Conversation: Modjk and Tomcat 5.5.4 problem Subject: Modjk and Tomcat 5.5.4 problem Has anyone had any problems with ModJK crashing the server? I haven't been able to fully debug yet, primarily because it doesn't update any logs to state there is a problem, and I can't reliably replicate the problem. I am using Apache 2.0.47, modjk 1.2.5 and tomcat 5.5.4 I think that it has something to do with modjk because when I go directly to the appserver the problem doesn't seem to exist. Any help would be greatly appreciated. Thank you, -John - 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]
