如何使用 apache mod_proxy_balancer 启用基于会话标识符的粘性负载平衡
下面给出了我们用于向 2 个 JBoss 实例发送请求的代理配置（在 httpd.conf 中）基于 mod_proxy_balancer
<Proxy balancer://mycluster>
Allow from all
BalancerMember http://192.168.1.2:9080
BalancerMember http://192.168.1.2:8080
</Proxy>
ProxyPass /app balancer://mycluster/app
ProxyPassReverse /app http://192.168.1.2:9080/app
ProxyPassReverse /app http://192.168.1.2:8080/app
如何启用基于会话标识符的粘性负载平衡。我是否应该将以下标志设置为代理声明的一部分？似乎没有任何效果。我将如何调试以查看这是否工作正常。
SetEnv BALANCER_SESSION_STICKY JSESSIONID
Our proxy configuration (in httpd.conf) to send requests to 2 JBoss instances are given below is based on mod_proxy_balancer
<Proxy balancer://mycluster>
Allow from all
BalancerMember http://192.168.1.2:9080
BalancerMember http://192.168.1.2:8080
</Proxy>
ProxyPass /app balancer://mycluster/app
ProxyPassReverse /app http://192.168.1.2:9080/app
ProxyPassReverse /app http://192.168.1.2:8080/app
How do I enable sticky load balancing based on session identifiers. Am I supposed to set the following flag as part of the Proxy declaration? It doesn't seem to take any effect. How would I debug to see if this is working fine.
SetEnv BALANCER_SESSION_STICKY JSESSIONID
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
PHP 粘性会话文章读起来很有趣，它引导我寻找 JBoss 特定的解决方案。关键是将路由附加到 jsessionid 参数/cookie 中的会话值。 JBoss（实际上是tomcat）对此有内置支持。
将 jvmRoute="" 添加到每个 server.xml 中的配置。然后将 jboss-service.xml 中的
false 将 mod_proxy 与 JBoss 结合使用中描述了整个设置。
The PHP sticky sessions article was an interesting read, and that lead me to look for a JBoss specific solution. The key is having the route appended to the session value in the jsessionid param/cookie. JBoss (actually tomcat) has builtin support for this.
Add jvmRoute="" to the config in each server.xml. Then change
<attribute name="UseJK">false</attribute>in jboss-service.xml to 'true'.The whole setup is described in Using mod_proxy with JBoss.