IBM Support

IT43281: TCPIPINPUT NODES MAY STOP PROCESSING IF THE TCPIP CONNECTION GETCLOSED WHILE THE NODE WAITS FOR DATA.

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

  • When a message flow is reading from an input stream connection
    of a socket and another message flow intentionally closes the
    socket connection, the connection does not get cleared and the
    reading message flow results in an infinite loop. The message is
    not propagated through the close terminal of the node if it is
    connected eventhough the connection is closed and the message
    flow results in a hang like situation.
    
    The service trace shows the following NullPOinterException in
    it :
    'java.lang.NullPointerException at
    com.ibm.broker.plugin.MbException.(MbException.java:229) at
    com.ibm.broker.plugin.MbException.(MbException.java:271) at com
    .ibm.broker.plugin.MbRecoverableException.(MbRecoverableExcepti
    on.java:85)at com.ibm.broker.plugin.MbErrorHandler.throwRecovera
    on(MbErrorHandler.java:115)at com.ibm.broker.tcpip.TCPIPInputStr
    Stream.java:289)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of App Connect Enterprise V12 using TCPIP input nodes.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a message flow is reading from an input stream connection
    of a socket and another message flow intentionally closes the
    socket connection, the connection does not get cleared and the
    reading message flow results in an infinite loop simulating a
    hang like situation.
    

Problem conclusion

  • The product has been modified such that the connection now gets
    cleared when the socket connection is intentionally closed by a
    message flow even when there is another message flow reading
    from the input stream.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v12.0      12.0.10.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

    IT43281

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0560

  • Reported release

    C00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-03-06

  • Closed date

    2023-09-22

  • Last modified date

    2023-09-22

  • 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

    5724J0560

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":"C00","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 September 2023