java.io.NotSerializableException: org.apache.catalina.connec

[jinhuang]

System: Redhat Linux, SQL Server
JBoss 4.0.3SP1

I have jboss clustering with session failover setup correctly and it works fine. But I can still see lots of NotSerializableExceptions in the server log for org.apache.catalina.connector.RequestFacade. As I understand, JBoss 4.0.3 enforces serializable for session variables, otherwise you will get NotSerializableException. We already made all our own session variables serializable, and my question is that org.apache.catalina.connector.RequestFacade is out of our control. Is there any way to get rid of the exception or is there a new version of RequestFacade that is serializable?

*************************************************************
2006-03-07 13:59:50,608 INFO [STDOUT] java.io.NotSerializableException: org.apache.catalina.connector.RequestFacade
2006-03-07 13:59:50,608 INFO [STDOUT] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
2006-03-07 13:59:50,608 INFO [STDOUT] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
2006-03-07 13:59:50,609 INFO [STDOUT] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
2006-03-07 13:59:50,609 INFO [STDOUT] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
2006-03-07 13:59:50,609 INFO [STDOUT] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
2006-03-07 13:59:50,609 INFO [STDOUT] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
2006-03-07 13:59:50,609 INFO [STDOUT] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
2006-03-07 13:59:50,610 INFO [STDOUT] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
2006-03-07 13:59:50,610 INFO [STDOUT] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
2006-03-07 13:59:50,610 INFO [STDOUT] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
2006-03-07 13:59:50,610 INFO [STDOUT] at java.util.LinkedList.writeObject(LinkedList.java:685)
2006-03-07 13:59:50,611 INFO [STDOUT] at sun.reflect.GeneratedMethodAccessor134.invoke(Unknown Source)
2006-03-07 13:59:50,611 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2006-03-07 13:59:50,611 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:324)
2006-03-07 13:59:50,611 INFO [STDOUT] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
2006-03-07 13:59:50,611 INFO [STDOUT] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
2006-03-07 13:59:50,612 INFO [STDOUT] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
2006-03-07 13:59:50,612 INFO [STDOUT] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
2006-03-07 13:59:50,612 INFO [STDOUT] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
2006-03-07 13:59:50,612 INFO [STDOUT] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
2006-03-07 13:59:50,612 INFO [STDOUT] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
2006-03-07 13:59:50,613 INFO [STDOUT] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
2006-03-07 13:59:50,613 INFO [STDOUT] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
2006-03-07 13:59:50,613 INFO [STDOUT] at java.util.HashMap.writeObject(HashMap.java:978)
2006-03-07 13:59:50,613 INFO [STDOUT] at sun.reflect.GeneratedMethodAccessor122.invoke(Unknown Source)
2006-03-07 13:59:50,614 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2006-03-07 13:59:50,614 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:324)
2006-03-07 13:59:50,614 INFO [STDOUT] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
2006-03-07 13:59:50,614 INFO [STDOUT] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
2006-03-07 13:59:50,614 INFO [STDOUT] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
2006-03-07 13:59:50,615 INFO [STDOUT] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
2006-03-07 13:59:50,615 INFO [STDOUT] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
2006-03-07 13:59:50,615 INFO [STDOUT] at org.jboss.web.tomcat.tc5.session.SessionBasedClusteredSession.writeExternal(SessionBasedClusteredSession.java:288)
2006-03-07 13:59:50,615 INFO [STDOUT] at org.jboss.web.tomcat.tc5.session.JBossCacheService.externalizeSession(JBossCacheService.java:771)
2006-03-07 13:59:50,616 INFO [STDOUT] at org.jboss.web.tomcat.tc5.session.JBossCacheService.putSession(JBossCacheService.java:229)
2006-03-07 13:59:50,616 INFO [STDOUT] at org.jboss.web.tomcat.tc5.session.SessionBasedClusteredSession.processSessionRepl(SessionBasedClusteredSession.java:165)
2006-03-07 13:59:50,616 INFO [STDOUT] at org.jboss.web.tomcat.tc5.session.JBossCacheManager.processSessionRepl(JBossCacheManager.java:606)
2006-03-07 13:59:50,616 INFO [STDOUT] at org.jboss.web.tomcat.tc5.session.JBossCacheManager.storeSession(JBossCacheManager.java:375)
2006-03-07 13:59:50,616 INFO [STDOUT] at org.jboss.web.tomcat.tc5.session.InstantSnapshotManager.snapshot(InstantSnapshotManager.java:38)
2006-03-07 13:59:50,617 INFO [STDOUT] at org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:91)
2006-03-07 13:59:50,617 INFO [STDOUT] at org.jboss.web.tomcat.tc5.session.JvmRouteValve.invoke(JvmRouteValve.java:73)
2006-03-07 13:59:50,617 INFO [STDOUT] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
2006-03-07 13:59:50,617 INFO [STDOUT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
2006-03-07 13:59:50,618 INFO [STDOUT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
2006-03-07 13:59:50,618 INFO [STDOUT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
2006-03-07 13:59:50,618 INFO [STDOUT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
2006-03-07 13:59:50,618 INFO [STDOUT] at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:307)
2006-03-07 13:59:50,618 INFO [STDOUT] at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385)
2006-03-07 13:59:50,619 INFO [STDOUT] at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748)
2006-03-07 13:59:50,619 INFO [STDOUT] at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678)
2006-03-07 13:59:50,619 INFO [STDOUT] at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871)
2006-03-07 13:59:50,619 INFO [STDOUT] at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
2006-03-07 13:59:50,620 INFO [STDOUT] at java.lang.Thread.run(Thread.java:534)

[brian.stansberry]

In one of your session attributes you are storing a LinkedList which has a reference to org.apache.catalina.connector.RequestFacade.

Your objects not only have to be Serializable, they can't have any non-transient fields that have a chain of non-transient references to non-serializable objects.

Or, as the French say it, Non! Non! Non! ;)

[zeroman]

I looked into several threads about issue:
http://jboss.com/index.html?module=bb&op=viewtopic&t=36184
http://jboss.com/index.html?module=bb&op=viewtopic&t=61228
and have such question.

We have a big project which has been run in cluster envr some time ago. We solved many NotSerializableException errors in code since that but... there are still similar errors happen sometimes.
The problem is. There are many places that potentially can put into session something with illegal references but code quantity is big to find such cases fats and easy. The things get worse because most of errors happen on clustered production servers and not on test servers.

Are there way to log/trace the putting objects into HTTPSession? Is it possible to make such logging/tracing using config params? I'd like to know where HTTPSession is aletered, that class doing that, where in the code objects with illegal references are put.

Are there any way to accomplish that?

[brian.stansberry]

Simplest for you would be to code up an implementation of javax.servlet.http.HttpSessionAttributeListener, and add it your web.xml. You'll then get a callback whenever an attribute is added, removed or replaced. From there you can do what you want to analyze the attribute, current call stack, etc.

[zeroman]

Thanks a lot, Brian!
I think it's a suitable approach for our purpose.