IBM Support

PI72434: NULLPOINTEREXCEPTION IS THROWN WHEN USING A JMS OBJECT WHICH HAS ALREADY BEEN DESTROYED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In some cases, if a JMS object handle has been destroyed and is
    no longer valid, but the application is still using it,
    NullPointerException will be thrown which is not reflecting the
    root cause of the issue.
    
    java.lang.NullPointerException
     at
    com.ibm.ejs.j2c.ConnectionManager.associateConnection(Connection
    Manager.java:2940)
     at
    com.ibm.ejs.jms.JMSSessionHandle.getOpenSession(JMSSessionHandle
    .java:1318)
     at
    com.ibm.ejs.jms.JMSSessionHandle.getOpenUnifiedSession(JMSSessio
    nHandle.java:1347)
     at
    com.ibm.ejs.jms.JMSSessionHandle.createTextMessage(JMSSessionHan
    dle.java:517)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a JMS object handle is no longer     *
    *                      valid but subsequently used, a          *
    *                      NullPointerException will be thrown     *
    *                      which is not reflecting the root cause  *
    *                      of the issue.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If a JMS object handle is no longer valid but subsequently
    used, a NullPointerException will be thrown.  However, an
    IllegalStateException would more accurately reflect the
    failure.
    

Problem conclusion

  • We now ensure an IllegalStateException is thrown to more
    accurately reflect the reason for failure.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.14.  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

    PI72434

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-16

  • Closed date

    2017-02-22

  • Last modified date

    2017-02-22

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
19 October 2021