IBM Support

PI78153: OTMA CLIENT TIMEOUT CANNOT BE CONFIGURED FOR WOLA

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If an IMS region is unable to process a WOLA request for some
    reason, such as the target IMS transaction is not available,
    there is no way to cancel the request to IMS.  The connection
    wait timeout provided in the managed connection factory or
    connection specification is not honored for requests to IMS
    using OTMA.
    

Local fix

  • In some instances a dispatch timeout or transaction timeout can
    be used to terminate the offending servant region,
    CAVEAT:::  But this can lead to frequent recycling of servant
    regions if the IMS region is configured incorrectly.  So it is
    offered with caution.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 and V9.0                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: The OTMA request timeout is not         *
    *                      honored when submitting requests via    *
    *                      WOLA.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The connection wait timeout provided on the WebSphere
    Optimized Local Adapters (WOLA) connection factory is not
    honored when submitting OTMA requests to IMS.  There is no
    way to interrupt an OTMA request after a fixed amount of time
    has elapsed.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI78153

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-14

  • Closed date

    2017-05-24

  • Last modified date

    2017-05-24

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021