On 15.10.2010 12:32, King Holger (CI/AFP2) wrote:
it's a pity - but the clocks are in sync (using NTP). On both Tomcats and the
Apache2 instances.
Good to know.
According to the following command output:
grep -i "52C326B80A73EFF19CEE49B013533F06" localhost_access_log.2010-10-14.log
the last
D=B3C4AABB5F983A0E9D6478C42C88A5C4.rb-wcmstc1; Path=/"
This POST throws a 500 status code.
-Original Message-
From: Rainer Jung [mailto:rainer.j...@kippdata.de]
Sent: Freitag, 15. Oktober 2010 10:58
To: users@httpd.apache.org
Subject: Re: [us...@httpd] "proxy_balancer"
Hi Holger,
On 14.10.2010 16:16, King Holger (CI/AFP2) wrote:
Unfortunately, after having activated the:
- Tomcat-AccessLog
- custom-LogFormat using Cookie-OutPut in Apache2 2.2.16
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\" \"%{Cookie}i\"
\"%{JSESSIONID}C\" \"%{S
ot; can be excluded (according to the tomcat GC-logs)!
The whole proxy balancer configuration you can see below.
We wonder:
- why does it happen, although "rb-wcmstc2" seems to be physically available?
- how to determine the root-cause?
Any ideas?
-Original Message-
From: Rainer
On 29.09.2010 16:53, King Holger (CI/AFP2) wrote:
Dear mailing list,
currently, we use the Apache2 version:
- Apache2 2.2.16 64bit
- standard "mod_proxy_balancer" module
with the following V-HOST configuration including a proxy balancer directive
(with two Apache Tomcat instances behind):
> Kind regards,
> Holger
>
>
> -Original Message-
> From: Thomas [mailto:apache.org-li...@darkwhole.de]
> Sent: Mittwoch, 29. September 2010 23:31
> To: users@httpd.apache.org
> Subject: Re: [us...@httpd] "proxy_balancer" | stickysession
>
> Hi H
,
why that happens on Apache2-side? How?
Kind regards,
Holger
-Original Message-
From: Thomas [mailto:apache.org-li...@darkwhole.de]
Sent: Mittwoch, 29. September 2010 23:31
To: users@httpd.apache.org
Subject: Re: [us...@httpd] "proxy_balancer" | stickysession
Hi Holger,
On 0
Hi Holger,
On 09/29/2010 04:53 PM, King Holger (CI/AFP2) wrote:
> In production environment, we discover connection switches from
> "rb-wcmstc1" to "rb-wcmstc2" and vice versa (documented in the
> Tomcat-Logs) for the same Session-ID:
[...]
> Although, the "stickysession" attribute is set properly
Dear mailing list,
currently, we use the Apache2 version:
- Apache2 2.2.16 64bit
- standard "mod_proxy_balancer" module
with the following V-HOST configuration including a proxy balancer directive
(with two Apache Tomcat instances behind):
BalancerMember ajp://rb-wcmstc1.xx.x.xxx:8009 l
