IBM Support

PI77076: WHEN ENABLE "START COMPONENTS AS NEEDED", CAN'T SUBMIT JOB FROM OTHER CLUSTER MEMBER NOT HOST THE SCHEDULER.

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

  • when enable "start components as needed", The Scheduler works
    as expected for applications running on the same Cluster as
    hosts the Scheduler.  However, we're not able to submit Jobs
    from applications running in other Clusters in the same cell.
    

Local fix

  • Disable "start components as needed" for the issue server can
    fix the issue.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  Java Batch                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Java Batch job submission fails when    *
    *                      dynamic provisioning is enabled         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When dynamic provisioning ("Start components as needed") is
    enabled on a WebSphere application server, component loading is
    deferred from startup to runtime. In a Java Batch environment,
    an
    endpoint server may fail to submit a job when dynamic
    provisioning
    is enabled, and the following message may be found in the server
    output:
    EndpointComponentImpl.initializePGC() return exception...PGC is
    not initialized.
    This occurs because not all of the Batch runtime's dependencies
    are correctly specified, so a necessary service may not have
    been
    initialized in time to process the job submit request.
    

Problem conclusion

  • The dependencies of the Batch runtime have been updated to inclu
    all necessary services. This will ensure these services are load
    in time to prevent this issue.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.13 and 9.0.0.6, and Compute Grid 8.0.0.6.  Pleas
    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

    PI77076

  • 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

    2017-02-22

  • Closed date

    2017-10-03

  • Last modified date

    2017-11-03

  • 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

  • R850 PSY

       UP

  • R900 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI77076

Modified date: 03 November 2017


Translate this page: