You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Michael Harrison <go...@alumni.princeton.edu> on 2003/04/22 21:50:57 UTC

mod_jk errors: "network problems"

I've seen some things about this problem in the list archive, but no
definitive explanation or solution. Can anyone update me?

 

I'm running Tomcat 4.1.18 with Apache 2.0.44 and mod_jk on RedHat 8.0.
Like some other people on this list, I find the following set of error
messages in my mod_jk log:

 

[Tue Apr 22 09:03:40 2003]  [jk_ajp_common.c (681)]: ERROR: can't
receive the response message from tomcat, network problems or tomcat is
down.

[Tue Apr 22 09:03:40 2003]  [jk_ajp_common.c (1050)]: Error reading
reply from tomcat. Tomcat is down or network problems.

[Tue Apr 22 09:03:40 2003]  [jk_ajp_common.c (1187)]: ERROR: Receiving
from tomcat failed, recoverable operation. err=0

[Tue Apr 22 09:03:40 2003]  [jk_ajp_common.c (681)]: ERROR: can't
receive the response message from tomcat, network problems or tomcat is
down.

[Tue Apr 22 09:03:40 2003]  [jk_ajp_common.c (1050)]: Error reading
reply from tomcat. Tomcat is down or network problems.

[Tue Apr 22 09:03:40 2003]  [jk_ajp_common.c (1187)]: ERROR: Receiving
from tomcat failed, recoverable operation. err=1

[Tue Apr 22 09:03:40 2003]  [jk_ajp_common.c (681)]: ERROR: can't
receive the response message from tomcat, network problems or tomcat is
down.

[Tue Apr 22 09:03:40 2003]  [jk_ajp_common.c (1050)]: Error reading
reply from tomcat. Tomcat is down or network problems.

[Tue Apr 22 09:03:40 2003]  [jk_ajp_common.c (1187)]: ERROR: Receiving
from tomcat failed, recoverable operation. err=2

[Tue Apr 22 09:03:40 2003]  [jk_ajp_common.c (1198)]: Error connecting
to tomcat. Tomcat is probably not started or is listenning on the wrong
port. Failed errno = 104

 

Each one matches up with a 500 error in the site's catalina log. What's
interesting in my case is that the failures seem to come in intermittent
clusters (the home page returns 500, another page returns 500, and then
both pages, and every other page, come in fine from then on for a long
time)

 

The consensus on the list (at least as of a month ago) is that there's
an issue with the mod_jk connections. Can anyone bring me up to date? Is
there a workaround or patch? Should I try to use mod_jk2 instead?

 

Cheers,

 

Michael