webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  Connection to partner broken error in SM58 queue after installed latest SAP Fix14 and new JCO jars

    Posted 6 days ago

    We have observed connection broken errors in SM58 queue transactions towards webMethods. We could see these error after we installed latest SAP_10.1_Fix14 and placing new JCo jars.

    [SAP.102.9000] JCo error: CPIC-CALL: CMRCV(coxread) on convId: 19364789 with rc: 20
     
    ERROR       connection to partner '10.165.130.101:sapgw00' broken
    TIME        Wed Jun 11 16:16:24 2025
    RELEASE     753
    COMPONENT   NI (network interface)
    VERSION     40
    RC          -6
    MODULE      /bas/753_REL/src/base/ni/nixxi.cpp
    LINE        5469
    DETAIL      NiIRead: P=10.165.130.101:3300; L=10.165.68.91:50592
    SYSTEM CALL recv
    ERRNO       104
    ERRNO TEXT  Connection reset by peer
    COUNTER     4
    Could you please someone help us to fix this issue.
    Thanks,
    Kumar


    ------------------------------
    Kumaraswamy Gorra
    ------------------------------


  • 2.  RE: Connection to partner broken error in SM58 queue after installed latest SAP Fix14 and new JCO jars

    Posted 5 days ago

    Dear Gorra, good morning!

    Please check if you can upgrade your SAP JCO Library to 3.1.12 version, that should solve the issue.

    I had the same problem a month ago.



    ------------------------------
    Renan Kaic Lopes
    ------------------------------

    Original Message


  • 3.  RE: Connection to partner broken error in SM58 queue after installed latest SAP Fix14 and new JCO jars

    Posted 5 days ago

    Hi Kumaraswamy Gorra,

    We had the same issue after installing SAP_10.1_Fix14 and JCo 3.1.11. The issue was solved after installing JCo 3.1.12 (https://support.sap.com/en/product/connectors/jco.html).

    Best regards,
    Theo



    ------------------------------
    Theo van Dijk
    ------------------------------

    Original Message


Related Content