on 2012 Apr 13 2:00 PM
Hi All ,
Have encounter an issue , wherein sender is SOAP and receiver is RFC .
Its like two interfaces using the same RFC receiver channel and both the interfaces failed and says :
Error messages says :
For 1st interface :
Error Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Sync application request expired.. Setting message to status failed
For 2nd interface :
Error Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: resource error: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception:(106) JCO_ERROR_RESOURCE: Connection pool RfcClient[CC_XXXXXXX] is exhausted. The current pool size limit(max connections) is 1 connections.. Setting message to status failed.
Can any one suggest , how to resolve this issue ?
Currently the Max connection is 1 , if we increase the value for Max Connection to 2 or 5 in the receiver adapter , will this solves the issue ? Please suggest.
-Shweta
Request clarification before answering.
Solution to max connection: increaase value to 25 like that , RFC adapter can handle max connetcion more than 30 at a time.
Solution to Time Out issue: Fisrt debug why your target system is taking that much time to give response, debug your BAPI and implement best coding syandards to get response withing time,.
Then think about chnaging RFC time out parameter value
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
I have a synchronous SOAP to RFC scenario. I am getting ‘Message (OUTBOUND) expired’ exception error.
When I checked my adapter engine my SOAP sender channel is failed with above error.
In my receiver RFC channel max connection is already set to 20. Also I have increased the value of timeout parameter in NWA to 5 minutes from default 3 minutes.
I am still getting the same timeout error. I have asked my ABAP team to check for the response time of the BAPI. And there is no code optimization required as the BAPI used is a standard BAPI.
Please help to further troubleshoot this problem.
| User | Count |
|---|---|
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.