Our webMethods software translates EDI data to SAP IDoc.
We are often getting JCO_ERROR_REQUEST_CANCELLED error from IS.
Also, we are getting the following error on the server.log.
‘Available Thread Pool Warning Threshold Exceeded: 14% available’
These two errors are related?
Can anyone advise me what are the causes and how to fix it?
I’d appreciate if any information you could give me.
[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service pub.sap.transport.ALE:OutboundProcess.
[SAP.102.9000] JCo error: (112) JCO_ERROR_REQUEST_CANCELLED - connection with handle 4  closed after cancel
As you recommended, I set the watt.server.clientTimeout value from 10 to 15, however there was no setting for watt.sap.rfc.callDuration on server.cnf.
Can you suggest a desirable initial value for that?
Our IS service restarts by itself once in three or four days or more often sometimes after exhausting all the threads.
Below is our adapter specification.
Description:webMethods SAP Adapter
JCA Spec Version:1.0
Vendor Name:Software AG
Try these settings on your sandbox or test servers, also check the fix readme, the details matches the issue that you are currently facing.
webMethods SAP Adapter transaction processing fails with the following error:
During long-running SAP client calls, SAP Adapter may abort the processing with
a JCO_ERROR_REQUEST_CANCELLED error message. The error occurs when JCo is
checking for the Integration Server session associated with the call,
but the Integration Server session has already timed out. As a result, JCo
aborts the client call to SAP with an error. This can happen if you have a
lengthy task, such as sending out 10,000 IDocs, and the task takes longer than
the Integration Server session timeout. An easy and direct solution would be to
increase the watt.server.clientTimeout parameter value (to perhaps 30 mins or
more). However, this might not be desirable in some installations.
This issue is resolved. When it is not desirable to increase the value of
watt.server.clientTimeout, SAP Adapter provides a new configuration parameter,
watt.sap.rfc.callDuration. With the new parameter, you prevent premature
Integration Server session timeouts during SAP client calls.
Set the maximum duration of SAP client calls (in minutes) directly so that the
associated Integration Server session cannot timeout and expire during the
execution of an SAP client call.
For example, to set the call duration to 30 minutes, specify:
The parameter has a default value equal to the Integration Server session
timeout value as specified in watt.server.clientTimeout. The minimum value of
the parameter is 10 (minutes). There is no maximum value.
For information about setting server configuration parameters and working with
extended settings, see Administering webMethods Integration Server.
Also, try to set the watt.sap.jco.timeout and watt.sap.listener.session.timeout to a higher value from the default 10 minutes.
After changing the configuration, I do not see the JCO_ERROR_REQUEST_CANCELLED error so far, however I am getting the following errors.
Looks like these errors are related to the change I made. These were thrown by different threads and different time. I think we are pushing too many requests to SAP and to Database server now.
Any suggestions on these?
[SQLServer JDBC Driver]Login has timed out.
An error occurred while attempting to retrieve a connection from rbxsapconn.connections:connNode_SAPPRD
A connection was not available for request in pool
Caused by: com.wm.adk.error.AdapterServiceException: [ART.117.4012] Adapter Runtime (Adapter Service): Unable to run adapter service. Error occurred when connecting to resource rbxsapconn.connections:connNode_SAPPRD.
What is your wM version? You might need to open a SR if the SAG if you have the support contract with them.
Can we now try to revert the settings added (as this setting should resolve the issue explained with the current SAP fix level), and install the latest SAP and IS fix levels on your sandbox and perform another round of tests? or go with the said settings with some fine tuning on IS memeory and threads.
Please share the log file if you encounter any issues.