IBM Support

IT04950: MQSIDEPLOY DOES NOT REPORT TIMEOUT FROM ADMIN AGENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a deploy initiated through the mqsideploy command takes a
    longer time to complete than the configuration timeout values on
    the broker, then the TIME-OUT flag returned by the AdminAgent is
    not correctly processed by mqsideploy and it waits until
    it's own waitTime value (-w) expires.
    

Local fix

  • Use the method described in Apar IC99973 to avoid timeouts where
    deploy operation takes more than 300 seconds to complete.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V9.0 who use CMP API
    applications for deploy operations,
    
    
    Platforms affected:
    MultiPlatform, z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If a deploy operation initiated via a CMP client, like the
    mqsideploy command, takes longer to complete than the default
    timeout value of 300 seconds, the TIME-OUT completion code
    returned by the broker is not recognized by the CMP client.
    Hence it fails to report the correct status of the deploy
    operation. The mqsideploy command continues to wait until it's
    own timeout value expires, as specified by the -w command line
    argument.
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0. For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT04950

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-20

  • Closed date

    2014-11-28

  • Last modified date

    2014-11-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

    INTEGRATION BUS

  • Fixed component ID

    5724J0530

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020