I'm no expert in this by any means so here's some questions that might help debugging your problem:
First, is tomcat actually restarting? catalina.out logs are clean? If tomcat's not restarting then is jk using some lib that was changed between rh8 and enterprise? Could try recompiling jk on the new system. (course you might have already done that...) could some other program be trying to use the port jk uses? try changing the port and retesting... anything unusual about the times when it flakes out? heavy load, etc... i'd check jk_connect.c and see if you can find out more info on what caused the error (61). if it just can't open the socket (as its reporting) then is it timing out or just getting refused? Could a firewall difference in the new system mess something up? i've reached the extent of my limited knowledge in this area. :-) hth, Adrian Lanning ----- Original Message ----- From: "Clute, Andrew" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Tuesday, March 16, 2004 4:39 PM Subject: RE: Sporadic connection loss between Tomcat and Apache though mod_jk I should also mention we are on Apache 2.0.47 -Andrew -----Original Message----- From: Clute, Andrew [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 4:24 PM To: [EMAIL PROTECTED] Subject: Sporadic connection loss between Tomcat and Apache though mod_jk Ever since upgrading the box that our Tomcat server (actually Jboss/Tomcat) resides on from RedHat 8.0 to RedHat Enterprise ES 3.0, we will get very sporadic 500 errors on our JSP pages. When we get one of the errors, if we refresh it right away, the page come back fine. Mod_jk is set up, to the best of knowledge, correctly, as it worked flawlessly for 12 months in production before we changed our production java box (the apache box stayed the same -- nothing about it changed, not even configuration files). Pertinent information: Uname -a = Linux WWW_JBOSS 2.4.21-9.0.1.ELsmp #1 SMP Mon Feb 9 22:26:51 EST 2004 i686 i686 i386 GNU/Linux Java version: Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1) Classic VM (build 1.4.1, J2RE 1.4.1 IBM build cxia321411-20030930 (JIT enabled: jitc)) Jboss3.2.3 with Tomcat 4.1.29 Here is the output from the mod_jk.log file: [Tue Mar 16 13:34:30 2004] [jk_connect.c (203)]: jk_open_socket, connect() failed errno = 61 [Tue Mar 16 13:34:30 2004] [jk_ajp_common.c (676)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 61 [Tue Mar 16 13:34:30 2004] [jk_ajp_common.c (955)]: Error connecting to the Tomcat process. [Tue Mar 16 13:34:30 2004] [jk_ajp_common.c (1309)]: sending request to tomcat failed in send loop. err=1 [Tue Mar 16 13:34:32 2004] [jk_connect.c (203)]: jk_open_socket, connect() failed errno = 61 [Tue Mar 16 13:34:32 2004] [jk_ajp_common.c (676)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 61 [Tue Mar 16 13:34:32 2004] [jk_ajp_common.c (955)]: Error connecting to the Tomcat process. [Tue Mar 16 13:34:32 2004] [jk_ajp_common.c (1309)]: sending request to tomcat failed in send loop. err=2 [Tue Mar 16 13:34:32 2004] [jk_ajp_common.c (1318)]: Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. Failed errno = 61 Thanks for any help! -Andrew --------------------------------------------------------------------- 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]
