IBM Support

IT22994: HTTP POST FAILS WITH THE CONNECTION CLOSED FROM THE PERIMETER SIDE

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

  • HTTP post fails and the connection closes from the
    Perimeter side with error: "Close code: connection reset".
    
    The following error is noticed in the perimeter.log file.
    
    escription: Alert Received.
    [2017-07-10 17:36:15.224] ERRORDTL <-392272111>
    [1499679375220]com.certicom.net.ssl.c: FATAL
    Alert:BAD_RECORD_MAC - A record was received with an incorrect
    MAC.
    Description: Alert Received.
        at
    com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(U
    nknown Source)
        at
    com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceiv
    ed(Unknown Source)
        at com.certicom.tls.record.alert.a.a(Unknown Source)
        at com.certicom.tls.record.alert.a.a(Unknown Source)
        at com.certicom.tls.record.g.a(Unknown Source)
        at com.certicom.tls.record.g.a(Unknown Source)
        at com.certicom.tls.record.k.h(Unknown Source)
        at com.certicom.tls.record.k.d(Unknown Source)
        at com.certicom.tls.record.k.read(Unknown Source)
        at
    com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.lo
    wLevelRead(SSLByteDataConduit.java:454)
        at
    com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.re
    ceive(SSLByteDataConduit.java:400)
        at
    com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.re
    ceive(SSLByteDataConduit.java:337)
        at
    com.sterlingcommerce.woodstock.services.httpclient.session.Custo
    mConnectAgent.canReceive(CustomConnectAgent.java:279)
        at
    com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.ca
    nReceive(SSLByteDataConduit.java:534)
        at
    com.sterlingcommerce.perimeter.api.conduit.SSLByteConduit.canRec
    eive(SSLByteConduit.java:265)
        at
    com.sterlingcommerce.perimeter.api.conduit.DataConduitApiImpl$4.
    body(DataConduitApiImpl.java:305)
        at
    com.sterlingcommerce.perimeter.api.ContextRunnable.run(ContextRu
    nnable.java:41)
        at
    com.sterlingcommerce.perimeter.api.scheduler.PooledScheduler$Gat
    ingScheduler$1.run(PooledScheduler.java:228)
        at
    com.sterlingcommerce.perimeter.api.scheduler.TaskNode.run(TaskNo
    de.java:62)
        at
    com.sterlingcommerce.perimeter.api.scheduler.DebugPooledExecutor
    $Worker.run(DebugPooledExecutor.java:786)
        at java.lang.Thread.run(Thread.java:795)
    

Local fix

  • Workaround is to remove all GCM ciphers that are being used in
    IBM Sterling B2B Integrator
    
    RTC NO: 554764
    

Problem summary

  • Users Affected:
    All
    
    Problem Description:
    HTTP post fails and the connection closes from the
    Perimeter side with error: "Close code: connection reset".
    Unable to send more than 20 purchase order requests at a time
    which causes delays in the shipments of items.
    
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    
    A code fix is provided.
    
    The issue is in Certicom libraries. You must upgrade the
    certicom libraries for solution.
    A quick workaround - You must remove all the ciphers which are
    GCM ciphers.
    Permanent solution - You must upgrade the Certicom libraries.
    
    DELIVERED IN:
    5020500_18
    5020601_10
    5020602_6
    5020603_6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT22994

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    525

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-11-01

  • Closed date

    2018-01-11

  • Last modified date

    2018-07-15

  • 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

[{"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.5","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
15 July 2018