--
View this message in context:
http://old.nabble.com/mod_jk-stability-issues-tp28662097p28855964.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
On 11.06.2010 16:28, LES wrote:
Well, your suggested changes worked...until today. It was absolutely rock
solid. Then, the last two days, with no load I started receiving errno=110
again. It didn't last all day, only a couple of hours yesterday and a
couple today. I have added a socket
,
Rainer
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
--
View this message in context:
http://old.nabble.com/mod_jk-stability-issues
/modjk_log_files.tar.gz
modjk_log_files.tar.gz
--
View this message in context:
http://old.nabble.com/mod_jk-stability-issues-tp28662097p28858465.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users
On 11.06.2010 20:06, LES wrote:
I only added socket_timeout in after looking at the included file in 1.2.30.
I was hoping that there was something in that file that I was missing.
I attached the log files that you asked for. Looking through them, I don't
see any notable increases in response
On 24.05.2010 23:36, LES wrote:
I am having some trouble keeping a mod_jk setup stable. At this point, I
feel like I am too far into trial and error mode and would like some help
figuring out how to identify the problem.
My current setup involves, two linux (RHEL 5) server each running two
--
View this message in context:
http://old.nabble.com/mod_jk-stability-issues-tp28662097p28667920.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
On 25.05.2010 14:48, LES wrote:
I can't believe I missed the millisecond thing. :)
No problem, it's our fault not using consistent time units. The latest
1.2.30 has a useful default configuration in the src tarball. But yours
looks good too.
Regards,
Rainer
): (tomcat01-instance1)
can't receive the response header message from tomcat, network problems or
tomcat (192.168.60.156:8009) is down (errno=104)
--
View this message in context:
http://old.nabble.com/mod_jk-stability-issues-tp28662097p28662097.html
Sent from the Tomcat - User mailing list archive
