Grouper Users - Open Discussion List

[Chris Hyzer <>]

The WS is stateless, so put a bunch of tomcats there and load balance.  I 
suggest source IP address sticky load balancing to prevent caching issues.
The UI Im not sure you can cluster sessions since there still might be some 
unserializable stuff in the session.  In 2.2 it should be fine.  :)
For now you can put multiple UI tomcats up with no clustering, and sticky 
load balancing based on cookie, it will work fine.  If a server goes down the 
user will need to login again after the load balancer takes the node out of 
the pool.

Thanks,
Chris

-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Adrian Lee
Sent: Monday, October 10, 2011 11:56 PM
To: 

Subject: [grouper-users] HA-ing grouper ...

Hi,

We're currently looking at piloting Grouper and the question has been raised 
about the possibility of a high availability (HA) deployment.   The database
and sources (LDAP in this case) are both HA.  Assuming a load-balancer is 
front-ending Grouper, that just leaves tomcat. Tomcat has clustering recipes 
- anyone tried/thought-about-trying such a configuration for Grouper?    Any 
thoughts on why this might be a bad idea?   Would clustering actually be 
necessary?

Thanks,
Adrian
-----------------
Adrian Lee
Information Technology Services
The University of Queensland