On Thursday 30 September 2010 09:54:11 King Holger (CI/AFP2) wrote:
Not only top posting, but also no quoting characters. Please fix that!
> Hi Thomas,
>
> I had to disappoint you, because the relevant excerpt of the Tomcat
> configuration below shows "jvmRoute" setup properly on EACH Tomcat
> instance:
>
> "rb-wcmstc1"
> <Engine name="Standalone" defaultHost="localhost" jvmRoute="rb-wcmstc1">
>
> "rb-wcmstc2"
> <Engine name="Standalone" defaultHost="localhost" jvmRoute="rb-wcmstc2">
>
> So, might it be a BUG in Apache2 2.2.16? Is it possible to identify the
> reason, why that happens on Apache2-side? How?
Do as Thomas recommended and capture the cookies and session ids. The IDs you
have in your first message look a bit unusual for tomcat generated session
IDs.
Additionally, you can set the Apache loglevel to debug for the VirtualHost
that does the loadbalancing. mod_proxy will log details about selecting the
backend worker.
Rainer
>
> Kind regards,
> Holger
>
>
> -----Original Message-----
> From: Thomas [mailto:apache.org-lists@xxxxxxxxxxxx]
> Sent: Mittwoch, 29. September 2010 23:31
> To: users@xxxxxxxxxxxxxxxx
> Subject: Re: "proxy_balancer" | stickysession
>
> 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 using the
> > "JSESSIONID" cookie name and the Apache-Tomcat instances are up and
> > running, the connection SWITCHES. Why?
>
> It looks like you did not set the jvmRoute-Attribute of the Engine tag
> in your Tomcat configuration to "rb-wcmstc1" on the first and
> "rb-wcmstc2" on the second server.
>
> mod_proxy_ajp (used by mod_proxy_balancer) identifies the Tomcat-backend
> holding the session by looking up a suffix added to the JSESSIONID
> cookie value. You can easily check whether the suffix is set or not by
> logging the session id in the Tomcat access log (%S) or by logging
> Cookie and Set-Cookie HTTP headers (logpattern: %{Cookie}i and
> %{Set-Cookie}o) in your httpd access log.
>
> Regards,
> Thomas
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
> " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
> " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|