IBM Support

PI33328: JAVAX.FACES.APPLICATION.FACESMESSAGE IS NOT SERIALIZABLE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • HTTP session cannot be stored into a session database due to
    the exception: NotSerializableException. This occurs because
    the object implementation javax.faces.application.FacesMessage
    is not serializable.
    
    This seems to occur when JSF flash mode is set to keep messages
    (setKeepMessages(true)). This is required when
    POST-Redirect-GET-principle is in use to avoid the loss of
    faces messages. If the "keep messages" parameter is set to
    false, the user will not see the messages.
    This can be reproduced by selecting the option to "store all
    attributes of the HTTP session" option in WebSphere
    Application Server's session persistence configuration.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Full       *
    *                  Profile versions 8.0 and 8.5.5 and Liberty  *
    *                  Profile version 8.5.5 users of JavaServer   *
    *                  Faces(JSF) MyFaces                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: A java.io.NotSerializableException      *
    *                      will occur when serializing a           *
    *                      javax.faces.application.FacesMessage.Se *
    *                      verity object.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The javax.faces.application.FacesMessage implements the
    java.io.Serializable interface, but its inner class Severity
    is not serializable.
    An exception similar to the following can be observed in the
    log:
    javax.faces.FacesException: java.io.NotSerializableException:
    javax.faces.application.FacesMessage$Severity
    at
    org.apache.myfaces.shared_impl.util.StateUtils.getAsByteArray(St
    ateUtils.java:283)
    at
    org.apache.myfaces.shared_impl.util.StateUtils.construct(StateUt
    ils.java:235)
    at
    org.apache.myfaces.renderkit.html.HtmlResponseStateManager.write
    ViewStateField(HtmlResponseStateManager.java:127)
    ...
    

Problem conclusion

  • The JSF MyFaces code was updated to properly implement
    serialization of the FacesMessage object.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.11 and 8.5.5.6. Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI33328

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-01-22

  • Closed date

    2015-02-19

  • Last modified date

    2015-02-19

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022