httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Galić <>
Subject Re: [users@httpd] debugging mod_proxy performance with WireShark
Date Mon, 18 Oct 2010 22:02:29 GMT

----- "Dustin Chesterman" <> wrote:

> Thanks Igor for the reply. Sorry for not knowing quite enough to be
> specific with some of this. When I say it hangs, I mean every once in
> a while it takes 15-20 seconds to respond. When I have a direct Tomcat
> connection setup it doesn't happen.

Usually the case is vice-versa, with tomcat not being able to handle
as many connections as httpd can reverse-proxy.

> mod_status was a great suggestion I did not realize was there. I'm not
> sure how I can use it though to debug this type of problem when many
> of the requests go though fine and one does not once in a while.

See for an example,
maybe paste your scoreboard here.

> I removed everything that was default per your suggestion. This is my
> new configuration:

I just find it more readable this way -- other people like to explicitly
name it -- whatever floats your boat!

> <VirtualHost 192.168.XXX.XXX:80>
> RewriteEngine On
> RewriteCond %{HTTPS} off
> RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
> </VirtualHost>
> <VirtualHost 192.168.XXX.XXX:443>
> ServerName 192.168.XXX.XXX
> ProxyPreserveHost On
> SSLEngine On
> SSLCertificateFile /etc/httpd/ssl/jirassl-pem.crt
> SSLCertificateKeyFile /etc/httpd/ssl/jirassl.key
> ProxyPass / http://localhost:8080/ disablereuse=off
> ProxyPassReverse / http://localhost:8080/
> </VirtualHost>
> I also added the diablereuse key.

Considering that you're back, I suppose it did not help your case.

> I have not used the AJP connection since the warning message about an
> open proxy scared me off. Would this be an issue for a reverse proxy?

The same is true for HTTP connections but not in reverse-proxy mode.

> Would this cause issues that last a long as I am seeing?

I don't know. I would need deeper insight in your httpd configuration,
things like Timeout and MPM settings.

Also, I don't know what your Tomcat app is doing.

Maybe it was just stuck in a GC at that point? See:

For more info

> I have a capture of the problem in a wireshark log. Is there something
> I can look for in there that would point me in the right direction to
> filtering his down?

I wouldn't know off-hand. If the wireshark capture doesn't contain
any data that is confidential, I suggest you attach it to your next
mail, and see if anyone springs at any of its gory details.

> Thanks again for your help and patience :)

You're very welcome.

> -Dustin


Igor Galić

Tel: +43 (0) 664 886 22 883

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message