AW: [opencms-dev] User Session Information in a clusterdenvironment(logged in or not)

[Nick Panienski]

Well, the cluster module doesn't share this information... we were thinking
about changing the OpenCms code, putting Login information into the session
and telling the other instances (using an event maybe) to update the user
information reading the stuff out of the replicated session.

I just haven't figured out where exactly the login and the checking for
access permissions are handled by OpenCms.
I also don't really want to change the code, otherwise a new distribution
has to be fixed again and again until Alkacon provides a solution...

But thanks anyway...
Nick

> -----Ursprüngliche Nachricht-----
> Von: opencms-dev-bounces at opencms.org 
> [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Jason Trump
> Gesendet: Donnerstag, 12. Januar 2006 18:11
> An: The OpenCms mailing list
> Betreff: RE: [opencms-dev] User Session Information in a 
> clusterdenvironment(logged in or not)
> 
> OpenCms tracks information about logged-in users in a static 
> Hashtable keyed by session id, rather than in the HttpSession 
> object itself.  So, even on a server cluster with session 
> replication, OpenCms's user data is tied to a single server VM.
> 
> I don't know if Alkacon's new commercial clustering module, 
> OCEE, addresses this issue or not.
> 
> Hope that helps.
> 
> jt
> 
> > -----Original Message-----
> > From: opencms-dev-bounces at opencms.org [mailto:opencms-dev- 
> > bounces at opencms.org] On Behalf Of Nick Panienski
> > Sent: Thursday, January 12, 2006 11:57 AM
> > To: 'The OpenCms mailing list'
> > Subject: [opencms-dev] User Session Information in a clusterd 
> > environment(logged in or not)
> > 
> > Hi,
> > 
> > I am looking for a way to share user information between multiple 
> > instances of OpenCms. I have a running cluster with session 
> > replication and non- sticky sessions (this is mandatory for our 
> > costumers demand).
> > 
> > For basic content everything's running fine, but as soon as you log 
> > into a site the information that a specific user just logged in is 
> > only available on the server that handled the specific 
> login request. 
> > With sticky sessions that would be no problem, but without 
> the servers 
> > delivers privileged (the one the user really logged in) and normal 
> > content (all other servers) throughout the cluster.
> > 
> > We have to make sure that all nodes in the cluster are 
> aware of logged 
> > in users.
> > 
> > If there is no such thing already implemented in OpenCms an 
> > explanation of how OpenCms handles User login/logoff would 
> be highly appreciated.
> > 
> > Bye
> > Nick Panienski
> > 
> > --
> > codecentric
> > Grünewalder Str. 29-31
> > 42657 Solingen
> > 
> > Office 0212  24 94 318
> > Mobile 0151 167 06 496
> > panienski at codecentric.de
> > 
> > 
> > _______________________________________________
> > This mail is sent to you from the opencms-dev mailing list 
> To change 
> > your list options, or to unsubscribe from the list, please visit 
> > http://lists.opencms.org/mailman/listinfo/opencms-dev
> 
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list To 
> change your list options, or to unsubscribe from the list, 
> please visit http://lists.opencms.org/mailman/listinfo/opencms-dev
> 
>