Skip to Content
avatar image
Former Member

Synchronous time out error in Receiver SOAP Adapter

Hi All,

I have a proxy to soap scenario, where sender is the ecc and the receiver is a webservice. While testing the scenario, I am unable to get the response from the web service and the receiver soap channel errors out with the following error:

Synchronous timeout exceeded.

Received XI System Error. ErrorCode: GENERAL ErrorText: Message 0fb8cad6-4ff9-11e2-813f-000002b613ca(INBOUND) expired ErrorStack: null

When we test the web service alone using the soap ui, we are able to get the response from the service.

I read in few of the blogs, where it is mentioned that the time out parameter in the channel should be increased.

I have used the parameter XMBWS.Timeout in the channel and have set it to 600000.

But the channel still errors out with the same error.

Kindly help.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Dec 27, 2012 at 08:21 AM

    Hi Pradan,

    We faced the same situation timeout exception thrown by PI if the response from web service wasn't received within 1 minute.

    First check whether the configured url for connecting to web service is proper or not with the concerned team.

    If it is proper then share the input payload to target system folks and ask them to test it from there end (they will have their own test suite for testing).

    In our case back end d/b connecting to web service is having some issue ,so the delay is happening ;they fix the issue by fine tuning it.

    If the above are not help full then go for increasing timeout parameter.



    Add comment
    10|10000 characters needed characters exceeded

    • >When I test it end to end in PI, the request I send is not received by the webservice.

      Check with firewall/network team and see any network slowness happening between PI and the receiver target system. This might be a problem. You dont need to increase timeout for 6 mins which is not good anyway for the real time/synchronous scenario.