Jetspeed puts a lot of objects in the session that are not serializable. I plan on trying to fix this next week. Wish it were as simple as just adding the 'serializable' interface, but I believe there will be complications. I tried this once before, and found out that Tomcat was aborting serialization of all session objects after failing to serialize one object. > -----Original Message----- > From: S�bastien Amielh [mailto:[EMAIL PROTECTED]] > Sent: 20 September 2002 10:33 > To: JetSpeed Jakarta > Subject: Failover > > > Hello, > I want to use JetSpeed as the presentation side of a > distributed architecture. In order to support web server load > balancing I look at Http session and it is not serialisable, > many non-serialisable classes come from JetSpeed > (ClientCapabilityMap, MetaData, VelocityPortletController ... ) > but others come from others apache projects > (org.apache.ecs.filter.NullFilter, ... ). Is anybody here able > to give me some advice to how make JetSpeed support failover? > > Is that means that the web server can't passivate the session? > > Thanks, > Sebastien >
BBCi at http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system, do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
