-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dimitar,
On 10/20/2011 11:37 AM, Dimitar Georgievski wrote:
> We have started series of tests to determine the effect of the
> following changes;
>
> 1. Upgrade Apache to 2.2.21 (the latest) 2. Upgrade Tomcat to
> 5.5.34 (the latest in the 5.x series
On Wed, Oct 19, 2011 at 10:27 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dimitar,
>
> On 10/18/2011 10:50 PM, Dimitar Georgievski wrote:
> >> SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1
> > This setting shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 10/19/2011 3:21 AM, André Warnier wrote:
> Next question :
>
>> ProxyPassMatch ^/(.*) ajp://localhost:8009/$1
>
> If you are forwarding *everything* to Tomcat anyway, then why do
> you have an Apache httpd in front ? why not just set up To
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dimitar,
On 10/18/2011 10:50 PM, Dimitar Georgievski wrote:
>> SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1
> This setting should control the mod_http_proxy connections. I
> forgot to mention this Apache server does that.
My reading su
Dimitar Georgievski wrote:
...
Mod proxy settings in Apache
ProxyStatus On
ProxyRequests Off
ProxyTimeout 1800
ProxyPassMatch ^/(.*) ajp://localhost:8009/$1
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
What happens if you just comment out the previous 2 lines ?
Unless I tota
> SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1
This setting should control the mod_http_proxy connections. I forgot to
mention this Apache server does that.
I'll definitely take out these settings, because the http proxy connections
should also be persistent.
Regarding the upgrade o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dimitar,
On 10/18/2011 8:30 PM, Dimitar Georgievski wrote:
> SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1
I'm no expert, but seeing keepalives disabled for a proxy connection
would sure make me think that maybe that setting is disablin
Hi Chris,
Tomcat AJP Connector settings:
Apache MPM worker settings;
StartServers 3
ServerLimit 30
MaxClients 750
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 25
MaxRequestsPerChild 0
Mod proxy settings in Apache
ProxyStatus On
ProxyRequests Off
ProxyTimeout 1800
ProxyPassMatch ^/(
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 10/18/2011 6:17 PM, Pid wrote:
> On 18/10/2011 20:40, Christopher Schultz wrote:
>> Dimitar,
>>
>> On 10/18/2011 2:15 PM, Dimitar Georgievski wrote:
>>> We have a Tomcat 5.5.25 server connected to Apache 2.2.9 over
>>> mod_ajp_proxy. Monitor
On 18/10/2011 20:40, Christopher Schultz wrote:
> Dimitar,
>
> On 10/18/2011 2:15 PM, Dimitar Georgievski wrote:
>> We have a Tomcat 5.5.25 server connected to Apache 2.2.9 over
>> mod_ajp_proxy. Monitoring of the servers shows that AJP proxy
>> connections are not reused but closed and reopened.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dimitar,
On 10/18/2011 2:15 PM, Dimitar Georgievski wrote:
> We have a Tomcat 5.5.25 server connected to Apache 2.2.9 over
> mod_ajp_proxy. Monitoring of the servers shows that AJP proxy
> connections are not reused but closed and reopened. Frequent
>
Hello,
We have a Tomcat 5.5.25 server connected to Apache 2.2.9 over mod_ajp_proxy.
Monitoring of the servers shows that AJP proxy connections are not reused
but closed and reopened. Frequent closing of TCP connections leaves many
connections in TIME_WAIT state and this is something we would pref
12 matches
Mail list logo
