IBM Support

PI66760: FileNotFound exception on agent during log upload causes an empty log file to be uploaded to the server causing a step to hang

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IO exception "Unable to delete" stdOut.txt on the agent during
    process step clean-up. The agent is trying to delete the output
    log file while still uploading the log file, causing the
    automatic version import to not complete.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All agents                                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * "File not found" exception on the agent during log upload    *
    * causes an empty log file to be uploaded to the server or     *
    * "Could not delete file" I/O exception when a process step's  *
    * clean-up action could not delete the log file because        *
    * another thread is uploading the log file to the server.      *
    *                                                              *
    * There is a check to see if the file exists before uploading  *
    * but the file deletion can occur in a different thread after  *
    * the check but before the file is uploaded. When the          *
    * FileNotFound exception occurs we are still posting to the    *
    * LogResource. On the agent side we should correct this race   *
    * condition.                                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Fix will be provided in IBM UrbanCode Deploy 6.2.2.0         *
    ****************************************************************
    

Problem conclusion

  • IBM UrbanCode Deploy 6.2.2.0.  After updating the agents to this
    release, the automatic version imports will update properly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI66760

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-29

  • Closed date

    2017-02-02

  • Last modified date

    2017-02-02

  • 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

  • R600 PSN

       UP

  • R600 PSY

       UP

  • R601 PSN

       UP

  • R601 PSY

       UP

  • R610 PSN

       UP

  • R610 PSY

       UP

  • R611 PSN

       UP

  • R611 PSY

       UP

  • R612 PSN

       UP

  • R612 PSY

       UP

  • R613 PSN

       UP

  • R613 PSY

       UP

  • R620 PSN

       UP

  • R620 PSY

       UP

  • R621 PSN

       UP

  • R621 PSY

       UP

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

Document Information

Modified date:
17 October 2021