httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bojan Smojver <>
Subject Re: Apache 1.3.23 On Linux Timeout Issues
Date Fri, 19 Jul 2002 02:40:41 GMT
It's hard to say without knowing your firewall configuration. Anyway, I'd try
the following:

- there is a newer version of mod_jk in CVS, 1.2.0; you might want to try that
- increase the logging (JkLogLevel debug) and watch the messages; it might give
you clues or you might be able to point problems out to Tomcat developers
- watch the logs of your firewall - it might be closing connections after a
while (mod_jk uses persistent connections)
- use 'netstat -an' on both the Apache and Tomcat/JBoss machines to verify which
ports are open and where the connections are actually coming from

I'm guessing you're running Apache 1.3.x... Apache 2.0.x is a slightly different
ball game.

And, of course, you might want to check out if there is a better version of TC
4/JBoss out there. There could be bugs related to mod_jk that were squashed in
the meantime.


Quoting Damian Alonso <>:

> Hi All,
> This problem has us stumped for answers, and I would appreciate any
> feedback
> on this issue.
> Basically we have a set up, where we have deployed an internal app, and
> we
> have the Apache Server sitting on a box outside our firewall, so that it
> is
> accessible over the www, and then the apache box redirects requests
> via
> mod_jk to a tomcat-jboss (Tomcat4.0.1-JBoss2.4.4) bundle sitting inside
> the
> firewall.  On our Apache Box, we also have the following plug-ins:
> - mod_jk/1.1.0
> - mod_ssl/2.8.4
> - OpenSSL/0.9.6b
> The problem we are having is that when clients from the www have tried
> to
> access our application via the Apache Box, sometimes there connection
> to
> Apache Box cannot be maintained, and it times out, never reaching the
> first
> page of the application.  We have found that when someone from within
> our
> firewall then hits the Apache Box (through the same www address as the
> external clients), it seems to 'reset' whatever the problem was for
> the
> external clients, and then THEY can then hit the site no problems, and
> everything is fine.  WEIRD.
> If anyone has seen this kind of problem before, please write back!!!
> Cheers,
> Damian.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message