Skip to Content
author's profile photo Former Member
Former Member

connection timeout error in the Response side

Hello Experts,

I am getting the connection timeout error in an RFC -PI -SOAP synchronous scenario.

"com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out"

I have gone through several blogs but didn't find convincing answers for such problems. I went through a time out document , which stated that for the receiver SOAP when the receiver application takes much longer to process the request message and give back the response to the receiver adapter, SOAP on the receiver side can get timed out. The solution for this is to increase this value by setting parameter XMBWS by value more than 5min ie by default it is set to 5 min or 300000msec. I had increased it to 600000msec ie 10 min, but the error persists.

Other scenarios configured for the same wsdl is working fine.

Can anybody share the solution for this type of scenario.

Thanks

Regards

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Posted on Jun 26, 2012 at 06:46 AM

    Hi,

    how long does it take before it times out ?

    Regards,

    Michal Krawczyk

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Michal Krawczyk

      Hi Michal,

      I saw your blog it is speaking about time out. I have increased the time of HTTP_TIMEOUT of the Integration Engine from 3000000 to 6000000. Apart from these can you suggest me why this SOAP receiver response is giving time out. Where should I handle this error?

      Thanks

      Regards

  • Posted on Jun 26, 2012 at 07:07 AM

    HI SRM_ADMIN

    Synchronous scenario should be the more interactive as possible. Personally, when a sync scenario is "heavier" i'd rather to convert it in asynchronous scenario with the communocation control in the endpoints.

    Regards.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 28, 2012 at 06:58 AM

    Hello,

    The problem is solved . The outgoing proxy server was having the problem. When proxy issue was resolved, the timeout error got faded.

    Regards

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.