IBM Support

PI68743: NULLPOINTEREXCEPTION MAY OCCUR IN ASYNC BEAN CODE

Fixes are available

9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The following NullPointerException with Async beans code may
    occur, which requires null checks:
    
    [8/31/16 9:43:14:332 EEST] 000001f2 TraceBPE      3
    com.ibm.bpe.framework.RestoreThreadContextForStateObserverWorkOb
    ject.run
    (RestoreThreadContextForStateObserverWorkObject.java:233) null
                                     java.lang.NullPointerException
        at
    com.ibm.ws.util.AsynchBeansInvocationTokenImpl.equals(AsynchBean
    sInvocationTokenImpl.java:174)
        at java.util.Hashtable.containsKey(Hashtable.java:468)
        at
    com.ibm.ws.CorrelationSphere.WorkAreaCallbackImpl.registCallback
    (WorkAreaCallbackImpl.java:130)
        at
    com.ibm.ws.CorrelationSphere.WorkAreaHelper.getNewWorkArea(WorkA
    reaHelper.java:228)
        at
    com.ibm.websphere.CorrelationSphere.CorrelationControler.openNew
    CorrelationSphere(CorrelationControler.java:127)
        at
    com.ibm.bpe.monitor.CorrelationSphereHelper.pushECSID(Correlatio
    nSphereHelper.java:114)
        at
    com.ibm.bpe.engine.observer.ActivityInstanceEventTypeHandler.pro
    cessBPELEvent(ActivityInstanceEventTypeHandler.java:1761)
        at
    com.ibm.bpe.engine.observer.CEMSOPContextRestored.activityInstan
    ceEvent(CEMSOPContextRestored.java:165)
    ...
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of the IBM WebSphere Application  *
    *                  Server Asynch Beans component.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Under rare circumstances                *
    *                      ComponentMetaData can fall out of       *
    *                      sync, ultimately leading to a           *
    *                      NullPointerException in code that       *
    *                      tries to check the ComponentMetaData.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When WebSphere Application Server is used with BPM
    ocassionally the ComponentMetaData (CMD) will fall out of
    sync, resulting in null CMD on the thread, which eventually
    leads to an NPE in WorkArea code.
    

Problem conclusion

  • This APAR adds proper null checks to
    AsynchBeansInvocationTokenImpl equals() and toString().
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.13, 8.5.5.12 and 9.0.0.3.  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

    PI68743

  • 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

    2016-09-07

  • Closed date

    2016-12-13

  • Last modified date

    2017-02-21

  • 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

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021