IBM Support

IT20407: IBM STERLING B2B INTEGRATOR COPYTOSERVICE GOES INTO AN INFINITE LOOP WITH A TRADING PARTNER AFTER UPGRADE TO V5.2.6.3

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

  • After upgrading to IBM Sterling B2B Integrator V5.2.6.3 and
    testing a particular partner, the Connect:Direct Server
    Adapter(CDSA), acting as the PNODE, CopyToService goes into an
    infinite loop after the connection is established.
    The CDSA Begin session does not restart, but the CopyToService
    retries over even though it always fails with "Connection lost"
    error in the Status Report.
    
    The CDSA is using Secure+.
    
    PSLogger
    
    [2017-04-18 16:49:41,397] COMMTRACE
    data[/<SBIRemotePSIP>:62510=>/<TradingPartnerIP>:1364]: error
    during write: java.io.IOException: An established connection
    was aborted by the software in your host machine.
    [2017-04-18 16:49:41,397] ERROR error during write
    java.io.IOException: An established connection was aborted by
    the software in your host machine.
                at sun.nio.ch.SocketDispatcher.write0(Native Method)
                at
    sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:64)
                at
    sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:106)
                at sun.nio.ch.IOUtil.write(IOUtil.java:78)
                at
    sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:526)
                at
    com.sterlingcommerce.perimeter.net.nio.SocketChannelWrapper.writ
    e(SocketChannelWrapper.java:251)
                at
    com.sterlingcommerce.perimeter.net.nio.SocketChannelWrapper.writ
    e(SocketChannelWrapper.java:238)
                at
    com.sterlingcommerce.perimeter.net.nio.SocketChannelWrapper.writ
    e(SocketChannelWrapper.java:230)
                at
    com.sterlingcommerce.perimeter.dispatcher.DataIPAgent.lowLevelWr
    ite(DataIPAgent.java:660)
                at
    com.sterlingcommerce.perimeter.dispatcher.DataIPAgent.writeNextE
    ntry(DataIPAgent.java:643)
                at
    com.sterlingcommerce.perimeter.dispatcher.DataIPAgent.doWrite(Da
    taIPAgent.java:445)
                at
    com.sterlingcommerce.perimeter.dispatcher.DataIPAgent.internalSe
    nd(DataIPAgent.java:622)
                at
    com.sterlingcommerce.perimeter.dispatcher.DataIPAgent.send(DataI
    PAgent.java:235)
                at
    com.sterlingcommerce.perimeter.external.connection.DataServer.re
    ceivedDataFromCircuit(DataServer.java:124)
                at
    com.sterlingcommerce.perimeter.external.connection.DataServer.re
    ceived(DataServer.java:101)
                at
    com.sterlingcommerce.perimeter.muxrat.relay.Relay.handleCircuitM
    essage(Relay.java:405)
                at
    com.sterlingcommerce.perimeter.muxrat.relay.Relay.handleRuntimeM
    essage(Relay.java:344)
                at
    com.sterlingcommerce.perimeter.muxrat.relay.Relay.handleReceived
    Message(Relay.java:315)
                at
    com.sterlingcommerce.perimeter.muxrat.relay.Relay.received(Relay
    .java:265)
                at
    com.sterlingcommerce.perimeter.dispatcher.DataIPAgent.sendCurren
    tToProtocol(DataIPAgent.java:384)
                at
    com.sterlingcommerce.perimeter.dispatcher.DataIPAgent.doRead(Dat
    aIPAgent.java:348)
                at
    com.sterlingcommerce.perimeter.dispatcher.AbstractIPAgent.select
    ed(AbstractIPAgent.java:142)
                at
    com.sterlingcommerce.perimeter.dispatcher.nio.NioDispatcher.runI
    o(NioDispatcher.java:198)
                at
    com.sterlingcommerce.perimeter.dispatcher.AbstractDispatcher.cal
    lRunIo(AbstractDispatcher.java:452)
                at
    com.sterlingcommerce.perimeter.dispatcher.AbstractDispatcher.doR
    un(AbstractDispatcher.java:427)
                at
    com.sterlingcommerce.perimeter.dispatcher.AbstractDispatcher$2.r
    un(AbstractDispatcher.java:175)
                at java.lang.Thread.run(Thread.java:798)
    [2017-04-18 16:49:41,397] DEBUG
    data[/<SBIRemotePSIP>:62510=>/<TradingPartnerIP>:1364].setState(
    ) -
    CloseCode.WRITE_FAILURE, from: CloseCode.EOF
    [2017-04-18 16:49:41,397] DEBUG
    data[/<SBIRemotePSIP>:62510=>/<TradingPartnerIP>:1364].setState(
    ) -
    combines to: CloseCode.WRITE_FAILURE
    [2017-04-18 16:49:41,397] COMMTRACE
    data[/<SBIRemotePSIP>:62510=>/<TradingPartnerIP>:1364]: close:
    CloseCode.WRITE_FAILURE
    [2017-04-18 16:49:41,397] DEBUG DataServer closed from external
    side: CloseCode.WRITE_FAILURE
    

Local fix

  • STRRTC - 536169
    SB / SB
    
    Circumvention:
    The CDSA connection was set to use TLSv1.0 when the error
    occurred.
    Setting both sides, the PNODE and the SNODE, to use TLSv1.2
    addresses this issue.
    

Problem summary

  • Users Affected:
    IBM Stering B2B Integrator V5.2 Users
    
    Problem Description:
    The CD CopyTo/CopyFrom Service endlessly restarts a session in
    scenarios where a session can be successfully established
    but breaks moments later preventing the session from making any
    progress.  The cause for this session break is the remote
    CD Node's inability to process SSL record fragmentation.
    Fragmentation occurs when Secure+ is configured with TLS 1.0
    and any CBC cipher.  NOTE: TLS 1.2 does not introduce SSL
    fragmentation.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    A code fix is provided.
    
    Delivered In:
    5020603_2
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT20407

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    526

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-28

  • Closed date

    2017-06-01

  • Last modified date

    2017-06-09

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

  • R526 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.6","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
09 June 2017