Timeout exception in RFC adapter engine

[Former Member]

Hi Experts ,

I have a situation here , its a  SOAP --- > RFC interface   and the messages are failing in the adapter engine and  the error log says :

012-07-17 08:15:58 Error Synchronous timeout exceeded.

2012-07-17 08:15:58 Error The message status was set to FAIL.

2012-07-17 08:20:53 Error Adapter Framework caught exception: while trying to invoke the method com.sap.aii.adapter.rfc.core.config.RfcConfig.getChannel() of an object returned from com.sap.aii.adapter.rfc.core.client.RfcClientPool.getConfig()

2012-07-17 08:20:53 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: java.lang.NullPointerException: while trying to invoke the method com.sap.aii.adapter.rfc.core.config.RfcConfig.getChannel() of an object returned from com.sap.aii.adapter.rfc.core.client.RfcClientPool.getConfig(). Setting message to status failed.

and when i check the J2EE properties for the same , its has the default setting for the  field  " syncMessageDeliveryTimeoutMsec"   as 300000 ms  (i.e 5 mins) .

Could anyone suggest , to how much shall i increase the value for this property in order to solve the issue ?

-Shweta 

[baskar_gopalakrishnan2]

The scenario seems synchronous. That means we are using real time scenario. Then setting timeout to 5 mins or increasing it is not the good decision or approach. First see the root cause of the problem in the function module level and then decide. Also I see null pointer exception in your log message. First test RFC functionality within SAP system and debug the error. Then use the end to end testing. The configuration setting in adapter level would not fix the issue.

[former_member184681]

Hi,

In most cases, 5 minutes should be enough to process a message (which is why that is the default value). Before increasing the value, you should first think about why it takes so long for the message to get processed. Maybe you need to optimize the code of the RFC receiver FM? Or split the data into chunks? Increasing the timeout is only one of the possible solutions, and normally it shouldn't be increased drastically (for instance to 1 hour or so), because it might seriously influence PI's stability.

Also, have a look at this document "How to Investigate Timeouts In Synchronous XI PI Scenarios":

http://scn.sap.com/docs/DOC-16238

Regards,

Greg

[Former Member]

just refer below blogs and might be helpful :

http://scn.sap.com/thread/199490   -> face the same prob and also change to 7

http://scn.sap.com/thread/1673360  -> how to increase

http://scn.sap.com/thread/517352