IBM Support

PI57539: "TIMEOUT EXCEEDED" IS DISPLAYED WHEN UPLOADING LARGE FILE TO APPLICATION CENTER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When uploading a large file to IBM Application Center through
    the Application Center Console, an error dialog "Timeout
    exceeded" may be displayed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of the Application Center Console                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When uploading a large file to IBM Application Center        *
    * through the Application Center Console, an error dialog      *
    * "Timeout exceeded" may be displayed even though the          *
    * operation appears properly done. If you check afterwards     *
    * whether the app that corresponds to the large file is stored *
    * in Application Center, you will find the app.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * -                                                            *
    ****************************************************************
    

Problem conclusion

  • The origin of this behavior is the following: The Console
    running in the browser waits for the server to respond after
    uploading the large file. Since it was a large file, the server
    might respond slowly. The console waited only 1 minute, and
    after that, it assumed the server response is missing and hence
    displays the error dialog. However the server might do all the
    work and respond after the 1 minute.
    
    As problem resolution, the 1 minute timeout was increased to 2
    minutes, so that this behavior occurs less frequently.
    
    Overall, a timeout in a client server architecture may happen
    occasionally on high server load and is not fatal, if it does
    not occur frequently. After a timeout message, the same
    operation should be redone and will very often succeed on the
    second attempt, under the assumption that the load of the server
    is well balanced and the high server load happened only
    temporary. Hence, even with the increase of the timeout to 2
    minutes, the behavior can still occur, but should now be very,
    very rare.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI57539

  • Reported component name

    MFPF/WORKLIGHT

  • Reported component ID

    5725I4301

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-18

  • Closed date

    2016-02-18

  • Last modified date

    2016-02-18

  • 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

    MFPF/WORKLIGHT

  • Fixed component ID

    5725I4301

Applicable component levels

  • R710 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSZH4A","label":"IBM Worklight"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 October 2021