IBM Support

IT45256: FOR EMBEDDED LISTENERS THE QUEUECAPACITY VALUE IS BEING IGNORED ON AIX.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • In IBM App Connect Enterprise the HTTP Listener parameter
    QueueCapacity value is being ignored in AIX for embedded
    listeners.
    
    Example:
    
    We have the below HTTP Connector configurations for the
    integration server.
    
    MaxConnections = 5
    QueueCapatiy = 2
    QueueWait = 5000
    
    When we send an HTTP request to the client the 1st request will
    be processed by the flow, 2nd request and 3rd request will be
    stored in the queue as QueueCapacity is 2. The 4th and 5th
    request should result in HTTP503 because If the queue remains
    full until the QueueWait interval expires, an HTTP 503 Service
    Unavailable message is returned to the client.
    
    On AIX platform this was not working as expected.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise using the HTTP listener
    parameter - QueueCapacity for the embedded listeners on AIX
    platform
    
    
    Platforms affected:
    AIX
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    For the embedded HTTP Listener, the parameter QueueCapacity
    value is being ignored on AIX platform
    
    Example:
    
    Consider following configuration for HTTP Connector
    
    MaxConnections = 5
    QueueCapatiy = 2
    QueueWait = 5000
    
    When a client makes multiple http requests to the message flow
    with Http Input node,  the first request will be processed by
    the flow, second request and third request will be stored in the
    queue as QueueCapacity is 2. The fourth and fifth request should
    result in HTTP 503 error because if the queue remains full until
    the QueueWait interval expires.
    
    On AIX platform this is not working as expected.
    

Problem conclusion

  • The product has been modified such that the correct error code
     HTTP 503 is returned to the client on AIX platform.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0
    v12.0      12.0.12.0
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT45256

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-01-11

  • Closed date

    2024-01-29

  • Last modified date

    2024-01-29

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
29 January 2024