Seam portlet throws exceptions in a clustered EPP environment

Solution Unverified - Updated -

Issue

We are seeing exceptions like the following every time a request (GET/POST) is made on the portal:

ERROR  [org.jboss.web.tomcat.service.session.JBossCacheService] IOException occurred marshalling value
java.io.NotSerializableException: javax.portlet.PortletMode
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
        at java.util.HashMap.writeObject(HashMap.java:1000)

and

ERROR [CacheMarshaller300] Error while marshalling object: ReplicateCommand{...} 
java.io.NotSerializableException: org.jboss.web.tomcat.security.login.WebAuthentication 
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) 

The portlet has been created using Seam and JBoss Portlet Bridge 2. We only see this in a clustered environment

Environment

  • JBoss Enterprise Portal Platform (EPP)
    • 4.3 CP 05 (and earlier)
    • 5.0.1 (and earlier)
  • Portlets based on Seam 2
  • Clustered environment

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.