IBM Support

PH06301: CWLRB6179E: FAILED TO INVOKE ENDPOINTCRMBEAN

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If customer is not using/not setup to use Compute Grid but
    needs to set  'provisionComponents =true'  then Compute Grid
    processing will attempt to use access EndpointCRMBean three
    times and then throw a Null Pointer Exception on the fourth
    attempt.   This slows down processing and occasionally can
    delay initialization completion on the non first servant in a
    multi-servant environment.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Java batch                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: When "Start components as needed" is    *
    *                      enabled on the endpoint server hosting  *
    *                      a batch application, batch jobs can     *
    *                      not be submitted successfully on zOS.   *
    *                      Additionally, this can cause a minor    *
    *                      delay in server startup.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    With "Start components as needed" enabled on a server,
    WebSphere Java batch will attempt to access the
    EndpointCRMbean three times, followed by a
    NullPointerException on the fourth attempt.  This retry
    processing can cause a minor delay in server startup.
    On zOS only, enabling this for an endpoint server running a
    batch application also prevents the necessary batch runtime
    components from starting.  This causes batch job submissions
    to fail for any batch applications running on that server.
    

Problem conclusion

  • The metadata for the com.ibm.ws.batch.runtime.jar plugin has
    been updated to properly indicate which components need to be
    started in the servant and control region processes when
    runtime provisioning is enabled.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.5.0 and 8.5.5.16  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

    PH06301

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-12-07

  • Closed date

    2019-04-29

  • Last modified date

    2019-04-29

  • 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 FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
14 October 2021