tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johnny Kewl" <j...@kewlstuff.co.za>
Subject Re: Load Balance sticky_session=True, am I missing something?
Date Fri, 01 Jun 2007 10:46:29 GMT

Tim... it looks almost right, I took snippets from some of my configs that 
work
... where I could see a difference.

Tomcat has has a built in load balancing option... that needs the session 
persistance that
you thinking about... you dont need it for the JK arrangement. They 2 
difference schemes.



----- Original Message ----- 
From: "Tim Alberts" <talberts@msiscales.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Thursday, May 31, 2007 10:52 PM
Subject: Re: Load Balance sticky_session=True, am I missing something?


> Well I found one problem with my workers.properties, but it didn't fix my 
> problem.  I used the deprecated 'balanced_workers' on my load balancer 
> configuration instead of the balance_workers. So I'm still stuck, any 
> suggestions?
>
>
> Tim Alberts wrote:
>> I have two tomcat servers (5.5.23) and running mod_jk (1.2.20) with load 
>> balancing behind apache.  I have a web application that needs to maintain 
>> session information.  What I'm seeing is that the load balance is 
>> alternating requests between the servers equally, as expected, but 
>> sessions are getting lost when going between the servers.  I thought from 
>> reading that the default is sticky_session=True which means the mod_jk 
>> will keep sessions going to the same server (if it is available..).  This 
>> is obviously not happening.  Am I doing something wrong, or is there a 
>> problem?
>>
>> # workers.properties - ajp13
>> #
>> # List workers
>> worker.list=lb,jkstatus
>> #
>> # Define wrkr1
>> worker.wrkr1.port=8009
>> worker.wrkr1.host=msi1
>> worker.wrkr1.type=ajp13
>> worker.wrkr1.socket_timeout=300
>> worker.wrkr1.lbfactor=1
worker.worker1.lbfactor=50
>> #
>> # Define wrkr2
>> worker.wrkr2.port=8009
>> worker.wrkr2.host=msi2
>> worker.wrkr2.type=ajp13
>> worker.wrkr2.socket_timeout=300
>> worker.wrkr2.lbfactor=1

worker.worker1.lbfactor=50

>> #
>> # Define lb
>> worker.lb.type=lb
>> worker.lb.sticky_session=True
>> worker.lb.sticky_session_force=False
>> worker.lb.balanced_workers=wrkr1,wrkr2


#try both these
worker.lb.sticky_session=1
worker.lb.sticky_session=true
worker.lb.sticky_session_force=false


>> #
>> # Define a 'jkstatus' worker using status
>> worker.jkstatus.type=status
>>
>> Second, I see a reference to a Session Manager in the Tomcat 
>> documentation that can maintain session data across multiple servers. 
>> This is the first I've heard about this, is this something Tomcat has 
>> built in that I need to enable, or is this third party or something I 
>> need to write on my own?  (I will be reading more, but quick info from 
>> users is helpful).
>>
>> Thank you for any help.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
> 


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message