基于Apache与JBoss的服务器负载均衡：会话与Cookie保持问题咨询

Got it, let's fix that session persistence issue you're facing with Apache mod_proxy_balancer and your three JBoss instances. The root cause here is that Apache isn't sticking users to the same JBoss node once their session is created—so every new request gets sent to a different server, wiping out their session data. Here's how to resolve this step by step:

First, you need to tell Apache to use sticky sessions tied to JBoss's session cookie. JBoss uses JSESSIONID as its default session cookie name, so add the stickysession parameter to your balancer setup, plus a unique route identifier for each backend node:

<Proxy "balancer://jboss-cluster">
    BalancerMember http://server1:8080 route=server1
    BalancerMember http://server2:8080 route=server2
    BalancerMember http://server3:8080 route=server3
    ProxySet stickysession=JSESSIONID
</Proxy>

The route values (server1/server2/server3) are critical here—they need to match exactly what you configure in each JBoss instance next.

JBoss needs to tag each session ID with the corresponding route value so Apache knows which node to send subsequent requests to. The setup varies slightly by JBoss version:

For JBoss EAP 7+/WildFly: #

Edit your standalone.xml (or domain.xml if using domain mode) and add the route attribute to the <session-cookie-configuration> section of your servlet container:

<servlet-container name="default">
    <session-cookie-configuration route="server1"/> <!-- Use server2/server3 for the other nodes -->
    <jsp-config/>
</servlet-container>

For JBoss AS 5/6: #

Modify server/default/deploy/jbossweb.sar/server.xml and add the jvmRoute attribute to the <Engine> tag:

<Engine name="jboss.web" defaultHost="localhost" jvmRoute="server1">

Make sure each JBoss node has its own unique route/jvmRoute value matching the Apache BalancerMember entries.

Double-check your ProxyPass rules to make sure Apache isn't dropping or mangling the JSESSIONID cookie. Add these directives to keep cookie domains and paths consistent:

ProxyPass /your-app balancer://jboss-cluster/your-app
ProxyPassReverse /your-app balancer://jboss-cluster/your-app
ProxyPassReverseCookieDomain your-loadbalancer-domain.com server1-domain.com server2-domain.com server3-domain.com
ProxyPassReverseCookiePath /your-app /your-app

Adjust the domain and path values to match your actual setup—this ensures the client's browser receives and sends back the correct cookie.

If you want to handle node failures without losing user sessions (so if one JBoss goes down, users get routed to another node with their session intact), enable JBoss session replication:

• Add the <distributable/> tag to each application's web.xml file
• Configure JGroups clustering in JBoss to enable session data sync between nodes

This step is optional but highly recommended for high availability.

Once you've made these changes, restart Apache and all three JBoss instances. Test by visiting your app, checking the JSESSIONID cookie in your browser dev tools—it should look like JSESSIONID=abc123.server1 (with the route suffix). Refresh a few times and verify all requests go to the same JBoss node.

内容的提问来源于stack exchange，提问作者Gian Honório