Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] RE: Session clustering in Grouper

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] RE: Session clustering in Grouper

Chronological Thread 
  • From: "GW Brown, Information Systems and Computing" <>
  • To: Chris Hyzer <>, "Mahabalagiri, Datta" <>,
  • Subject: Re: [grouper-users] RE: Session clustering in Grouper
  • Date: Tue, 21 Oct 2008 09:38:55 +0100

The UI is pretty standard and does depend on Jsessionid cookies. I doubt it would work straight off in a non sticky application server cluster - I haven't checked to see that all session data is serializable, however, we would be willing to look at making session data serializable.

Terracotta looks interesting, but I've no idea if it would work well with Grouper. Currently this would be out of scope for the core Grouper project, however, if you were undertaking such a project we would be interested to know the results and would try to support you where practical.


--On 20 October 2008 21:37 -0400 Chris Hyzer

I believe it is a pretty standard j2ee webapp. Jsessionid cookie,
standard j2ee sessions. At Penn we do several app servers with sticky
session load balancing... so I think the session failover for you has a
good chance of working, try it out. Btw, it is a struts webapp, so you
might be able to use url session handling or another method, but I
recommend just using the cookie based if possible... Gary might correct
me though... J



From: Mahabalagiri, Datta
Sent: Monday, October 20, 2008 6:43 PM

Subject: [grouper-users] Session clustering in Grouper


How does Grouper UI manage user sessions? Is it cookie based?

We want to run multiple Grouper instances in Production to provide
failover and load balancing. I want to understand how is the session
managed in this case. Can we use a Session clustering product like

I want to know if there is an alternative besides using sticky sessions.



GW Brown, Information Systems and Computing

Archive powered by MHonArc 2.6.16.

Top of Page