RFC Client Exception

[Former Member]

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

[Former Member]

increase max connection in receiver rfc comm channel to 15 or 20 and see if it works.

[Former Member]

Rajeev ,

Yea will do that , one more thing wanted to check here .

There was an option in NWA  --- > under Java Service  --- > under RFC adapter  as syncMessageDeliveryTimeoutMsec  , normally this  can be increased to solve this kind of  issues. But I can't see this parmeter in  PI 7.1 .

Can some one tell me where is this parameter maitained in 7.1 ??

[Former Member]

increasing the above timeout parameter will enable to get response even if it is delayed slightly. But if two or more reqs come simultaneously, then this parameter though resolving first error, will still lead to second error if the max connections are not increased.