IBM Support

PI68708: DEPLOYMENT HANGS WHEN MAX # OF CONCURRENT COMPONENT NOT SET TO -1

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When deploying a version to a large number of resources,  if the
    version has already been deployed and the Max # of concurrent
    jobs for the step is not set to -1, the deployment can hang, and
    the
    server can become temporarily slow. A
    "java.lang.StackOverflowError" will appear in the server logs.
    

Local fix

  • Set the "Max # of concurrent jobs" to -1 for the step.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users using install multpile * steps with max iteration      *
    * count > 0                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When deploying a version to a large number of resources,  if *
    * the                                                          *
    * version has already been deployed and the Max # of           *
    * concurrent                                                   *
    * jobs for the step is set to -1, the deployment can hang, and *
    * the                                                          *
    * server can become temporarily slow. A                        *
    * "java.lang.StackOverflowError" will appear in the server     *
    * logs.                                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fixed in 6.2.4.0.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI68708

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    621

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-09-06

  • Closed date

    2017-03-21

  • Last modified date

    2017-04-28

  • 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

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

  • R621 PSY

       UP

  • R622 PSY

       UP

  • R623 PSY

       UP

  • R624 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"621","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
19 October 2021