I think the most common form of load balancing (apache/tomcat) includes
"sticky sessions" which means that once a user is assigned to a tomcat,
all subsequent requests will go to that tomcat until the user logs out.
When they log in again, they will again be assigned to a server
(perhaps a different one) where their requests will go until they again
log out.
/kurt
Manisha Sathe wrote:
I am using form based Datasource Realm for
authentication and authorization. Also need to
consider clustering/loadbalancing of web server (in
this case Tomcat). In docs it is written for Realm as
follows
"Once a user has been authenticated, the user (and his
or her associated roles) are cached within Tomcat for
the duration of the user's login. ....
The cached user is not saved and restored across
sessions serialisations."
I am worried about last line - whether it means that
it does not support loadbalance techniques ? So if
next request from user (who is logged in previously)
goes to another server, then user needs to login
again? What is the solution for this?
Thanks in advance,
regards
Manisha
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
