Thanks....I will look at 5.5.8. I know it is in alpha status right now, but I am just testing and by the time I deploy my application, 5.5.8 will probably be stable.
Thanks Randall -----Original Message----- From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 8:55 AM To: Tomcat Users List Subject: RE: Tomcat clustering and NotSerializableException Randall, I know that session replication works in Tomcat 5.5.7 and it may also works in 5.0.x (no experience). But to get failover restart to work properly (i.e. restarting a failed node) I had to use Tomcat 5.5.7 with a developer-supplied patch. This patch will be available with Tomcat 5.5.8. HTH- Richard Randall Svancara wrote: > But do those session objects replicate to the other tomcat > instances??? I have been testing session objects that implement > java.io.serializable and I have not yet been able to see these objects > when fail over occurs to another instance?? > > Thanks, > > Randall > > -----Original Message----- > From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED] > Sent: Monday, February 28, 2005 8:13 AM > To: Tomcat Users List > Subject: RE: Tomcat clustering and NotSerializableException > > As Matt said its probably your applications objects. When we switched > to clustering I was surprised at how many of my session objects I > needed to add serializable to. But it was easy work and quickl done. > > HTH - Richard > > Dale, Matt wrote: >> I would guess that this means you have an object in your session that >> does not implement the serializable interface. >> >> Ta >> Matt >> >> -----Original Message----- >> From: Sng Wee Jim [mailto:[EMAIL PROTECTED] >> Sent: 28 February 2005 09:21 >> To: tomcat-user@jakarta.apache.org >> Subject: Tomcat clustering and NotSerializableException >> >> >> >> Hi, >> >> >> >> >> >> I am using Tomcat 5.0.28 on MS Win2k server. >> >> >> >> >> After I have uncommented the "Cluster" element in server.xml, I get >> the following exceptions on the tomcat console for some actions that >> are using displaytag. >> >> >> >> >> Is it a tomcat bug, since >> org.apache.coyote.tomcat5.CoyoteRequestFacade >> is involved? >> >> >> >> >> >> >> >> >> (DeltaManager.java:813)- Unable to serialize delta request >> >> java.io.NotSerializableException: >> org.apache.coyote.tomcat5.CoyoteRequestFacade >> >> at >> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054) >> >> >> >> >> at >> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java >> >>> 1332) >> >> at >> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13 >> >> 04) >> >> at >> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav >> >> a:1247) >> >> at >> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) >> >> >> >> >> at >> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278) >> >> at >> org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeE >> >> xternal(DeltaRequest.java:300) >> >> at >> org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaR >> >> equest.java:217) >> >> at >> org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(D >> >> eltaManager.java:393) >> >> at >> org.apache.catalina.cluster.session.DeltaManager.requestCompleted(Del >> >> taManager.java:782) >> >> at >> org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationVa >> >> lve.java:203) >> >> at >> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv >> >> eContext.java:102) >> >> at >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j >> >> ava:118) >> >> at >> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv >> >> eContext.java:102) >> >> at >> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav >> >> a:520) >> >> at >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal >> >> ve.java:109) >> >> at >> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv >> >> eContext.java:104) >> >> at >> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav >> >> a:520) >> >> at >> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) >> >> >> >> >> at >> org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16 >> >> 0) >> >> at >> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300) >> >> >> >> >> at >> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374) >> >> at >> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743) >> >> at >> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja >> >> va:675) >> >> at >> org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) >> >> at >> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP >> >> ool.java:683) >> >> at java.lang.Thread.run(Thread.java:534) >> >> >> >> >> >> >> >> >> >> >> - Jim >> >> >> >> > ************************************************************************ >> The information in this email is confidential and is intended solely >> for the addressee(s). Access to this email by anyone else is >> unauthorized. If you are not an > >> intended recipient, please notify the sender of this email >> >> immediately. You should not copy, use or disseminate the >> >> information contained in the email. >> Any views expressed in this message are those of the individual >> sender, except where the sender specifically states them to be the >> views of Capco. >> >> http://www.capco.com/ >> >> > ************************************************************************ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
