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.

Background of the issue:

• Initially we had observed the attached issue in SAP queue, but those transactions were executed successfully in the retry job (which is auto scheduled for every 55 mins at SAP) or when we re-execute manually.
• Issue was not so often it occurred occasionally(1 txn for 30 mins , 2-3 for 1 hour, sometimes none) and will be identified when we closely monitor the SM58 queues for every few minutes. 
  

Could you please help us to fix this issue and let us know if you need any other information from our end.

Thanks,

Kumar

Good morning Kumaraswamy! My Regards from Brazil to you!!

I faced the same issue a month ago.

To fix it, I had to install the latest SAP JCo library 3.1.12 instead of the 3.1.11 in our Integration Server.

Let me know if I can help you with more information.

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.

Background of the issue:

• Initially we had observed the attached issue in SAP queue, but those transactions were executed successfully in the retry job (which is auto scheduled for every 55 mins at SAP) or when we re-execute manually.
• Issue was not so often it occurred occasionally(1 txn for 30 mins , 2-3 for 1 hour, sometimes none) and will be identified when we closely monitor the SM58 queues for every few minutes. 
  

Could you please help us to fix this issue and let us know if you need any other information from our end.

Thanks,

Kumar

Hi Renan,

Thanks for the response!

I have already installed the latest SAP JCo library 3.1.12 and still I'm facing this issue.

Can you please confirm which SAP Fix version you installed in webMethods?

Thanks,

Kumar

Good morning Kumaraswamy! My Regards from Brazil to you!!

I faced the same issue a month ago.

To fix it, I had to install the latest SAP JCo library 3.1.12 instead of the 3.1.11 in our Integration Server.

Let me know if I can help you with more information.

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.

Background of the issue:

• Initially we had observed the attached issue in SAP queue, but those transactions were executed successfully in the retry job (which is auto scheduled for every 55 mins at SAP) or when we re-execute manually.
• Issue was not so often it occurred occasionally(1 txn for 30 mins , 2-3 for 1 hour, sometimes none) and will be identified when we closely monitor the SM58 queues for every few minutes. 
  

Could you please help us to fix this issue and let us know if you need any other information from our end.

Thanks,

Kumar

Dear Gorra,

We're using the latest SAP adapter update: SAP_10.1_Fix14

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners.

Hi Renan,

Thanks for the response!

I have already installed the latest SAP JCo library 3.1.12 and still I'm facing this issue.

Can you please confirm which SAP Fix version you installed in webMethods?

Thanks,

Kumar

Good morning Kumaraswamy! My Regards from Brazil to you!!

I faced the same issue a month ago.

To fix it, I had to install the latest SAP JCo library 3.1.12 instead of the 3.1.11 in our Integration Server.

Let me know if I can help you with more information.

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.

Background of the issue:

• Initially we had observed the attached issue in SAP queue, but those transactions were executed successfully in the retry job (which is auto scheduled for every 55 mins at SAP) or when we re-execute manually.
• Issue was not so often it occurred occasionally(1 txn for 30 mins , 2-3 for 1 hour, sometimes none) and will be identified when we closely monitor the SM58 queues for every few minutes. 
  

Could you please help us to fix this issue and let us know if you need any other information from our end.

Thanks,

Kumar

Hi Renan,

Please find below details.

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version  --> we are on latest IDoc Library Version 3.1.4 (2025-05-26) which is shared by SAP.
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0. --> Yes, SAP connection polling is enabled and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners. --> The current Number of Threads we configured for Listener is 15

We have placed SAP jars in the below places.

Please let me know if we need to change anything.

Thanks,

Kumar

Dear Gorra,

We're using the latest SAP adapter update: SAP_10.1_Fix14

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners.

Hi Renan,

Thanks for the response!

I have already installed the latest SAP JCo library 3.1.12 and still I'm facing this issue.

Can you please confirm which SAP Fix version you installed in webMethods?

Thanks,

Kumar

Good morning Kumaraswamy! My Regards from Brazil to you!!

I faced the same issue a month ago.

To fix it, I had to install the latest SAP JCo library 3.1.12 instead of the 3.1.11 in our Integration Server.

Let me know if I can help you with more information.

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.

Background of the issue:

• Initially we had observed the attached issue in SAP queue, but those transactions were executed successfully in the retry job (which is auto scheduled for every 55 mins at SAP) or when we re-execute manually.
• Issue was not so often it occurred occasionally(1 txn for 30 mins , 2-3 for 1 hour, sometimes none) and will be identified when we closely monitor the SM58 queues for every few minutes. 
  

Could you please help us to fix this issue and let us know if you need any other information from our end.

Thanks,

Kumar

Hi Gorra,

Maybe the new version of the IDoc Library triggers the error "Connection to partner '...' broken" again? This setup does work for me:

• IntegrationServer/instances/default/lib/libsapjco3.so  (= SAP Java Connector 3.1.12)
• IntegrationServer/instances/default/packages/WmSAP/code/jars/static/sapjco3.jar  (= SAP Java Connector 3.1.12)
• IntegrationServer/instances/default/packages/WmSAP/code/jars/static/sapidoc3.jar  (= SAP Java IDoc Library 3.1.3)

Best regards,
Theo

Hi Renan,

Please find below details.

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version  --> we are on latest IDoc Library Version 3.1.4 (2025-05-26) which is shared by SAP.
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0. --> Yes, SAP connection polling is enabled and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners. --> The current Number of Threads we configured for Listener is 15

We have placed SAP jars in the below places.

Please let me know if we need to change anything.

Thanks,

Kumar

Dear Gorra,

We're using the latest SAP adapter update: SAP_10.1_Fix14

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners.

Hi Renan,

Thanks for the response!

I have already installed the latest SAP JCo library 3.1.12 and still I'm facing this issue.

Can you please confirm which SAP Fix version you installed in webMethods?

Thanks,

Kumar

Good morning Kumaraswamy! My Regards from Brazil to you!!

I faced the same issue a month ago.

To fix it, I had to install the latest SAP JCo library 3.1.12 instead of the 3.1.11 in our Integration Server.

Let me know if I can help you with more information.

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.

Background of the issue:

• Initially we had observed the attached issue in SAP queue, but those transactions were executed successfully in the retry job (which is auto scheduled for every 55 mins at SAP) or when we re-execute manually.
• Issue was not so often it occurred occasionally(1 txn for 30 mins , 2-3 for 1 hour, sometimes none) and will be identified when we closely monitor the SM58 queues for every few minutes. 
  

Could you please help us to fix this issue and let us know if you need any other information from our end.

Thanks,

Kumar

Hi Kumarswamy,

This is known issue for IBM, after applying the SAP_10.1_Fix14. Please take help from your SAP Basis and get the latest jars with Hotfix.

Below is the comment from IBM.

As part of the latest SAP Adapter 10.1 Fix14, you can see that the upgrade to SAP JCo 3.1.11 is necessary. SAP has detected a bug in their new version of JCo library which can cause connectivity issues. So, please create a case with SAP Support about this issue to get a Hotfix from SAP to resolve this issue.

Hi Gorra,

Maybe the new version of the IDoc Library triggers the error "Connection to partner '...' broken" again? This setup does work for me:

• IntegrationServer/instances/default/lib/libsapjco3.so  (= SAP Java Connector 3.1.12)
• IntegrationServer/instances/default/packages/WmSAP/code/jars/static/sapjco3.jar  (= SAP Java Connector 3.1.12)
• IntegrationServer/instances/default/packages/WmSAP/code/jars/static/sapidoc3.jar  (= SAP Java IDoc Library 3.1.3)

Best regards,
Theo

Hi Renan,

Please find below details.

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version  --> we are on latest IDoc Library Version 3.1.4 (2025-05-26) which is shared by SAP.
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0. --> Yes, SAP connection polling is enabled and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners. --> The current Number of Threads we configured for Listener is 15

We have placed SAP jars in the below places.

Please let me know if we need to change anything.

Thanks,

Kumar

Dear Gorra,

We're using the latest SAP adapter update: SAP_10.1_Fix14

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners.

Hi Renan,

Thanks for the response!

I have already installed the latest SAP JCo library 3.1.12 and still I'm facing this issue.

Can you please confirm which SAP Fix version you installed in webMethods?

Thanks,

Kumar

Good morning Kumaraswamy! My Regards from Brazil to you!!

I faced the same issue a month ago.

To fix it, I had to install the latest SAP JCo library 3.1.12 instead of the 3.1.11 in our Integration Server.

Let me know if I can help you with more information.

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.

Background of the issue:

• Initially we had observed the attached issue in SAP queue, but those transactions were executed successfully in the retry job (which is auto scheduled for every 55 mins at SAP) or when we re-execute manually.
• Issue was not so often it occurred occasionally(1 txn for 30 mins , 2-3 for 1 hour, sometimes none) and will be identified when we closely monitor the SM58 queues for every few minutes. 
  

Could you please help us to fix this issue and let us know if you need any other information from our end.

Thanks,

Kumar

Hi Gorra,

Maybe the new version of the IDoc Library triggers the error "Connection to partner '...' broken" again? This setup does work for me:

• IntegrationServer/instances/default/lib/libsapjco3.so  (= SAP Java Connector 3.1.12)
• IntegrationServer/instances/default/packages/WmSAP/code/jars/static/sapjco3.jar  (= SAP Java Connector 3.1.12)
• IntegrationServer/instances/default/packages/WmSAP/code/jars/static/sapidoc3.jar  (= SAP Java IDoc Library 3.1.3)

Best regards,
Theo

Hi Renan,

Please find below details.

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version  --> we are on latest IDoc Library Version 3.1.4 (2025-05-26) which is shared by SAP.
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0. --> Yes, SAP connection polling is enabled and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners. --> The current Number of Threads we configured for Listener is 15

We have placed SAP jars in the below places.

Please let me know if we need to change anything.

Thanks,

Kumar

Dear Gorra,

We're using the latest SAP adapter update: SAP_10.1_Fix14

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners.

Hi Renan,

Thanks for the response!

I have already installed the latest SAP JCo library 3.1.12 and still I'm facing this issue.

Can you please confirm which SAP Fix version you installed in webMethods?

Thanks,

Kumar

Good morning Kumaraswamy! My Regards from Brazil to you!!

I faced the same issue a month ago.

To fix it, I had to install the latest SAP JCo library 3.1.12 instead of the 3.1.11 in our Integration Server.

Let me know if I can help you with more information.

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.

Background of the issue:

• Initially we had observed the attached issue in SAP queue, but those transactions were executed successfully in the retry job (which is auto scheduled for every 55 mins at SAP) or when we re-execute manually.
• Issue was not so often it occurred occasionally(1 txn for 30 mins , 2-3 for 1 hour, sometimes none) and will be identified when we closely monitor the SM58 queues for every few minutes. 
  

Could you please help us to fix this issue and let us know if you need any other information from our end.

Thanks,

Kumar

Hi Gorra,

Maybe the new version of the IDoc Library triggers the error "Connection to partner '...' broken" again? This setup does work for me:

• IntegrationServer/instances/default/lib/libsapjco3.so  (= SAP Java Connector 3.1.12)
• IntegrationServer/instances/default/packages/WmSAP/code/jars/static/sapjco3.jar  (= SAP Java Connector 3.1.12)
• IntegrationServer/instances/default/packages/WmSAP/code/jars/static/sapidoc3.jar  (= SAP Java IDoc Library 3.1.3)

Best regards,
Theo

Hi Renan,

Please find below details.

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version  --> we are on latest IDoc Library Version 3.1.4 (2025-05-26) which is shared by SAP.
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0. --> Yes, SAP connection polling is enabled and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners. --> The current Number of Threads we configured for Listener is 15

We have placed SAP jars in the below places.

Please let me know if we need to change anything.

Thanks,

Kumar

Dear Gorra,

We're using the latest SAP adapter update: SAP_10.1_Fix14

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners.

Hi Renan,

Thanks for the response!

I have already installed the latest SAP JCo library 3.1.12 and still I'm facing this issue.

Can you please confirm which SAP Fix version you installed in webMethods?

Thanks,

Kumar

Good morning Kumaraswamy! My Regards from Brazil to you!!

I faced the same issue a month ago.

To fix it, I had to install the latest SAP JCo library 3.1.12 instead of the 3.1.11 in our Integration Server.

Let me know if I can help you with more information.

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.

Background of the issue:

• Initially we had observed the attached issue in SAP queue, but those transactions were executed successfully in the retry job (which is auto scheduled for every 55 mins at SAP) or when we re-execute manually.
• Issue was not so often it occurred occasionally(1 txn for 30 mins , 2-3 for 1 hour, sometimes none) and will be identified when we closely monitor the SM58 queues for every few minutes. 
  

Could you please help us to fix this issue and let us know if you need any other information from our end.

Thanks,

Kumar

Hi @Theo van Dijk,

Could you please confirm which SAP are you using? I mean it's ECC or S4 system?

Thanks,

Kumar

Hi Gorra,

Maybe the new version of the IDoc Library triggers the error "Connection to partner '...' broken" again? This setup does work for me:

• IntegrationServer/instances/default/lib/libsapjco3.so  (= SAP Java Connector 3.1.12)
• IntegrationServer/instances/default/packages/WmSAP/code/jars/static/sapjco3.jar  (= SAP Java Connector 3.1.12)
• IntegrationServer/instances/default/packages/WmSAP/code/jars/static/sapidoc3.jar  (= SAP Java IDoc Library 3.1.3)

Best regards,
Theo

Hi Renan,

Please find below details.

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version  --> we are on latest IDoc Library Version 3.1.4 (2025-05-26) which is shared by SAP.
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0. --> Yes, SAP connection polling is enabled and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners. --> The current Number of Threads we configured for Listener is 15

We have placed SAP jars in the below places.

Please let me know if we need to change anything.

Thanks,

Kumar

Dear Gorra,

We're using the latest SAP adapter update: SAP_10.1_Fix14

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners.

Hi Renan,

Thanks for the response!

I have already installed the latest SAP JCo library 3.1.12 and still I'm facing this issue.

Can you please confirm which SAP Fix version you installed in webMethods?

Thanks,

Kumar

Good morning Kumaraswamy! My Regards from Brazil to you!!

I faced the same issue a month ago.

To fix it, I had to install the latest SAP JCo library 3.1.12 instead of the 3.1.11 in our Integration Server.

Let me know if I can help you with more information.

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.

Background of the issue:

• Initially we had observed the attached issue in SAP queue, but those transactions were executed successfully in the retry job (which is auto scheduled for every 55 mins at SAP) or when we re-execute manually.
• Issue was not so often it occurred occasionally(1 txn for 30 mins , 2-3 for 1 hour, sometimes none) and will be identified when we closely monitor the SM58 queues for every few minutes. 
  

Could you please help us to fix this issue and let us know if you need any other information from our end.

Thanks,

Kumar

Hi Kumar,

We are using S4.

Best regards,
Theo

Hi @Theo van Dijk,

Could you please confirm which SAP are you using? I mean it's ECC or S4 system?

Thanks,

Kumar

Hi Gorra,

Maybe the new version of the IDoc Library triggers the error "Connection to partner '...' broken" again? This setup does work for me:

• IntegrationServer/instances/default/lib/libsapjco3.so  (= SAP Java Connector 3.1.12)
• IntegrationServer/instances/default/packages/WmSAP/code/jars/static/sapjco3.jar  (= SAP Java Connector 3.1.12)
• IntegrationServer/instances/default/packages/WmSAP/code/jars/static/sapidoc3.jar  (= SAP Java IDoc Library 3.1.3)

Best regards,
Theo

Hi Renan,

Please find below details.

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version  --> we are on latest IDoc Library Version 3.1.4 (2025-05-26) which is shared by SAP.
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0. --> Yes, SAP connection polling is enabled and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners. --> The current Number of Threads we configured for Listener is 15

We have placed SAP jars in the below places.

Please let me know if we need to change anything.

Thanks,

Kumar

Dear Gorra,

We're using the latest SAP adapter update: SAP_10.1_Fix14

Please check the following items:

• Your SAP IDoc library is on 3.1.3 (2023-02-24) version
• Connection polling is enabled for the SAP connection and its "Minimum pool size" is 0.
• Increase the number of threads for SAP Listeners.

Hi Renan,

Thanks for the response!

I have already installed the latest SAP JCo library 3.1.12 and still I'm facing this issue.

Can you please confirm which SAP Fix version you installed in webMethods?

Thanks,

Kumar

Good morning Kumaraswamy! My Regards from Brazil to you!!

I faced the same issue a month ago.

To fix it, I had to install the latest SAP JCo library 3.1.12 instead of the 3.1.11 in our Integration Server.

Let me know if I can help you with more information.

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.

Background of the issue:

• Initially we had observed the attached issue in SAP queue, but those transactions were executed successfully in the retry job (which is auto scheduled for every 55 mins at SAP) or when we re-execute manually.
• Issue was not so often it occurred occasionally(1 txn for 30 mins , 2-3 for 1 hour, sometimes none) and will be identified when we closely monitor the SM58 queues for every few minutes. 
  

Could you please help us to fix this issue and let us know if you need any other information from our end.

Thanks,

Kumar