• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Sticky session not working (Load Balancing)

 
Ranch Hand
Posts: 1710
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

It looks most often question in the web. I searched for the similar problem and solution here in the JavaRanch forum but couldn't get much out of them.

I want sticky session to work in the environment where two JBoss servers running on two machines.
node name is attached to the JSESSIONID as .node1 but it doesn't work as the further next requests
for the same user is not consistently forwarded to the same jboss server.
I am using mod_jk.

I have already done following stuffs:


1- I have set jvmRoute in the JBoss server.xml
2- Set useJK=true in META-INF/jboss-service.xml
3- I tried session_cookie = JSESSIONID & session_path=;jsessionid in workers.properties in Apache
but with my version of mod_jk it complaints it doesn't support these two.

Is there any configuration setup that I am missing in Apache Web server or JBoss please let me know.



Thanks in advance.
 
Saloon Keeper
Posts: 27762
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You probably should have asked this in the JBoss forum.

As far as it goes, a balanceable webapp really shouldn't care which server in a load-balanced cluster handles a given HTTP request. Gluing a user to a single server interferes with the blancing functionality.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic