Sticky sessions isn't working through Apache httpd load balancer when passing the root context to another
Issue
-
Sticky sessions are not being properly maintained when we're routing requests from the root context on httpd to the application context on our JBoss backend, for example:
ProxyPass / balancer://mycluster/appContext/ stickysession=JSESSIONID -
The session cookie is not being properly pass along with subsequent requests, and JBoss is creating a new cookie with each request.
-
When an empty path cookie is present and used in the request with mod_cluster, it fails after immediate errors saying that all workers are in error state.
-
What does the SessionCookie path does?
Environment
- JBoss Enteprise Application Platform (EAP)
- JBoss Enterprise Web Server (EWS)
- 1.0.x
- Apache httpd
- mod_cluster
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
