On Thu, May 22, 2008 2:36 pm, Scott Courtney wrote: > There really are only two solutions: > > 1. Modify your application so that RequestFacade is not stored in the > session > object. You probably won't learn much from the stack trace, because > that is > tracing the replication process that failed, not the application code > that > stored the object. Look for a Serializable object in your app which has > a > reference to RequestFacade, perhaps in a member variable. Find a way > not to > use that reference, or not to store your containing object in the > session. > > 2. Modify the Echo2 or Catalina source code so that RequestFacade is > declared > Serializable. I would be *very* cautious about doing that, because just > declaring the Serializable interface doesn't mean that your object can > be sensibly serialized -- it just means *you* think it can. As someone > else > suggested, read up on the serialization process before trying this. And > in > any case, this means forking a library module, which is usually a > horrible > idea. > > As others have said, this question is really more related to Tomcat than > it > is to Apache, so you will probably have better luck on the Tomcat forums. > I'm > hoping the above hints will give you a headstart on a Google search of > those > forums and/or a closer look at your application code. There's actually a 3rd option -- if you need to hang on to a request object, mark it transient. It makes NO sense to move a request object around the cluster; I wouldn't recommend trying to make that work. (Sorry about the formatting...:) ) -- Eric Lennon Bowman Bobo Company Ltd ebowman@xxxxxxxxx --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|