Martin,
Off the top of my head. If you are going to be relying on HttpSession
failover and in-memory replication you have to call
session.setAttribute(...,...) after changing any of the HttpSession objects.
This pushes changes of a session object to a back up server. If you change
an object in the HttpSession and do not call session.setAttribute( ) then
when you failover to the backup machine the objects in the HttpSession
object will be missing alot of the stuff you changed.
If you are using database persistence then it does not matter because
every call to getSession pulls all of the Ojects from the database and
writes the changes when you are finished. This is also the reason database
session persistence is 10 times slower than in-memory relication.
I don't know if the Struts source code needs to take this into
consideration.
If you are using EJBs there are other things non-struts related that you
will have to be aware of.
--Abraham
> -----Original Message-----
> From: Martin Habermann [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 24, 2001 1:50 AM
> To: [EMAIL PROTECTED]
> Subject: Struts on a WebLogic5.1 Cluster
>
>
> Hi,
>
> has anybody expiriences in running struts on a weblogic5.1 clustered
> environment.I would appreciate any hint or suggestion on that topic...
>
>
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
>
