Version 5

    Common Use Cases

    Session replication in a clustered environment


    Example log file entry:

    2007-04-18 14:33:23,758 ERROR [com.icesoft.faces.facelets.D2DFaceletViewHandler] Problem in 
    renderResponse: /facelets/template/Center.xhtml @20,36 locale="#{session.locale}" setAttribute: 
    Non-serializable attribute


    Exception stack trace that usually accompanies such logging:


    java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute
    at org.jboss.web.tomcat.tc5.session.ClusteredSession.setAttribute(
    at org.apache.catalina.session.StandardSessionFacade.setAttribute( 


    Remote EJB Call


    Example log file entry:

    2007-04-18 14:27:33,250 ERROR [STDERR] Caused by: org.jboss.serial.exception.SerializationException: 
    Could not create instance of java.util.logging.Logger - java.util.logging.Logger



    One or more references in the object graph are not serializable. To be serializable, an object must:

    1. Implement the Serializable interface or inherit that implementation from its object hierarchy.

    2. Have all nonserializable fields marked as transient.



    Following are possible techniques that can be used to help identify the nonserializable class causing the error:

    1. Search your code base for instances of the class referenced in the log file.

    2. Change the org.jboss.serial logging level to DEBUG in log4j.xml.

    3. If you are using JDK 1.6 set the following JVM property to add serialization information to the stack trace:

    4. Attached is a utility class diagnostic.  It can be deployed via web.xml as a listener (see class javadoc) and will attempt to serialize any object passed as a value to HttpSession.setAttribute(), logging any issues to System.out.  If the passed in value is a Collection or Map, it also analyzes the contents, to help pinpoint the issue.