cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP Receiver Time Out

former_member181962
Active Contributor
0 Kudos

Hi Experts,

  We have a SOAP Lookup from a message mapping using Java code , which uses a SOAP Receiver Channel to make a synchronous SOAP call.

This call is failing due to a time out.

The error says:

2/23/2016 12:56:33 PM

SOAP: Call failed: java.net.ConnectException: Connection timed out

2/23/2016 12:56:33 PM

Failed to call the endpoint: Error in call over HTTP: HTTP 0 null

To rule out the network issue, we have done a successful TELNET(OS level) and a PING from communication channel monitor.

We have other SOAP Receiver channels which have the same Target URL(But async) which are working without issues.

We have also verified that the service is working as expected, by testing it via SOAPUI.

Any ideas?

Best Regards,

Ravikanth Talagana

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member182412
Active Contributor
0 Kudos

Hi Ravi,

The error is when you call the web service PI is waiting for response message from the web service and PI did not receive the response message for specified time out period so blank response received by adapter that is why you are getting HTTP 0 null.

You can enable the TraceHTTP parameter in the soap receiver channel and see the response from the web service.

Regards,

Praveen.

engswee
Active Contributor
0 Kudos

Hi Ravi

I'd suggest you create a dummy scenario that uses this particular SOAP receiver channel and test it end to end. This can help to rule out if it's related to Java code, receiver channel config or network issues.

Regards

Eng Swee

former_member181962
Active Contributor
0 Kudos

Hi,

The Java code is working without issue in production.

This issue is only in our QA environment.

Best Regards,

Ravi

engswee
Active Contributor
0 Kudos

Is telnet working fine in QA? The HTTP null error really looks like a network/firewall issue.

markangelo_dihiansan
Active Contributor
0 Kudos

Hi Ravi,

Are you using HTTP Proxies? If yes, you might need to include it in your java code.

Regards,

Mark

former_member181962
Active Contributor
0 Kudos

We are not using Proxies.

The Java code is working fine in  production.

The issue is only in QA.

Harish
Active Contributor
0 Kudos

Hi Ravi,

What is the message size for timeout issue? Is this big message size as compare to other interface?

regards,

Harish

former_member181962
Active Contributor
0 Kudos

Message size is very small.

Only one record with 2 fields.

Best Regards,

Ravi