I recently went through all of Jetspeed code and ensured that every object put into the session is serializable. I then ran tests with Tomcat, going thru a normal shutdown using the Tomcat 4.1 Manager, and restarting. These changes are not yet part of a release, but you can pick them up from the cvs head.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 09, 2002 11:04 PM > To: Jetspeed Users List > Subject: clustering in jetspeed1.4b > > > > Hi, > I tried to deploy jetspeed1.4b on a Weblogic cluster and was not fully > successful. > By not fully successful, I mean, when I kill a server, some information is > retained. I get the Login screen in the top, but the bottom part of the > page (the velocity example and other stuff) retains the info that was > present before killing the server. > I found out that some of the basic requirements for clustering > and failover > are not fulfilled, like > 1. Some objects that are put in session are not serialiazed. > 2. In some places, session.getValue() and session.putValue() has been used > instead of getAttribute() and setAttribute() > Some of these are in turbine that comes along with jetspeed. > > If anybody has attempted something similar and has been successful or > otherwise, please let me know. > > Regards, > Lavanya > > -----------------------Disclaimer------------------------ > > The views of the author may not necessarily reflect those > of the Company. All liability is excluded to the extent > permitted by law for any claims arising as a result of the > use of this medium to transmit information by or to > IT Solutions (India) Pvt. Ltd. > > We have taken precautions to minimize the risk of > transmitting software viruses, but we advise you to > carry out your own virus checks on any attachment to > this message. We cannot accept liability for any loss or > damage caused by software viruses. > > ------------------------Disclaimer------------------------ > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
