IBM Support

PH14926: DESERIALIZING A SESSION LOADS CLASSES FORM DIFFERENT CLASS LOADERS.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Execute the process of creating a session in the application,
    and restart WAS after the session is stored in the session DB.
    If you then access different URIs of the same application with
    the same session ID, the session deserialization will load
    different classloader classes and an error will occur.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using distributed sessions           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Session deserialization loaded          *
    *                      different classloader may give          *
    *                      java.lang.ExceptionInInitializerError   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When class loader order is PARENT_LAST, session
    deserialization may throw an exception:
    java.lang.ExceptionInInitializerError
    SourceId:com.ibm.ws.session.SessionLoader.loadObject
    java.lang.ExceptionInInitializerError
    at java.lang.J9VMInternals.ensureError(J9VMInternals.java:141)
    at
    java.lang.J9VMInternals.recordInitializationFailure(J9VMInternal
    s.java:130)
    at java.lang.Class.forNameImpl(Native Method)
    at java.lang.Class.forName(Class.java:348)
    

Problem conclusion

  • Code changes were made to extended the application loader in
    session deserialization to avoid the
    java.lang.ExceptionInInitializerError.
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.17 and 9.0.5.2. 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

    PH14926

  • 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

    2019-07-29

  • Closed date

    2019-08-23

  • Last modified date

    2019-08-23

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PH14926

Modified date: 23 August 2019