IBM Support

PH41336: WSGRID JOB SUBMISSION MAY FAIL AFTER APAR PH35447

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

  • WSGRID job submission might fail with
    
    "CWLRB6172E: Could not find URL for Endpoint:"
    An unhandled exception occured on a thread in Threadpool:
    GAPReadyQMonitorDispatcherThreadPool;
    java.lang.NullPointerException
    
    The problem happens when the code is looking for an active
    Endpoint to dispatch to, and logging a message with an
    uninitialized field, which leads to the NPE.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  Java Batch                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Submitting a java batch job for an      *
    *                      application installed but with no       *
    *                      active                                  *
    *                      server results in a                     *
    *                      java.lang.NullPointerException in the   *
    *                      server logs                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When submitting a java batch job, if no server is available that
    has the target application installed, a NullPointerException
    will
    occur and the job submission will halt instead of remaining in
    submitted state until an endpoint becomes active.
    

Problem conclusion

  • A code update has been made to fix the target server checking to
    prevent this issue.
    
    The fix for this APAR is targeted for inclusion in fix pack
    9.0.5.11 and 8.5.5.21. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH41336

  • 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

    2021-10-14

  • Closed date

    2022-01-21

  • Last modified date

    2022-01-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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

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

Document Information

Modified date:
22 January 2022