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

[Former Member]

Hi,

I am working on XI to SOAP scenario.

The message in SXMB_MONI is successfully processed but the receiver system is not getting the same.

When I checked Communication channel monitoring in RWB, it is giving the following error:

Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out.

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

Please help..

Regards,

Sriparna

[Shabarish_Nair]

confirm your settings - /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

[former_member200962]

Is the target web-service functioning properly.....if you try to post request to the web-service directly (from SOAP UI) is it able to execute properly.

[Former Member]

Another possibility is that the firewall hasn't been correctly configured. For example: the PI server is not allowed to make a connection to the SOAP server.

[Former Member]

Hi Iddo,

how to test the connection between PI server and SOAP server?

[Former Member]

Hi Abhishek,

I tested the WSDL through Altova XML Spy and could successfully post the data to the receiver system

[Former Member]

Logon to the OS of the PI server, and enter the URL of the SOAP service in your internet browser.

[former_member200962]

I tested the WSDL through Altova XML Spy and could successfully post the data to the receiver system

Ask your Network team to open the port from which XI sends the message to the SOAP application.

[Former Member]

Hi,

How do we know the exact port that needs to get opened.....

Regards,

Sriparna

[former_member200962]

The target application-developers or admin should be able to tell you the corresponding port

[Former Member]

Sriparna--

The issue is:

a) The port is blocked (the firewall issue others are describing, although there can be other causes for the port to be blocked as well)

b) The Web service is taking too long to process (or failing) on the receiving end.

It sounds like your testing in XML Spy probably shows it's not B, but did it take awhile for XML Spy to get the response back? PI has a lot of timeouts in it that are set by default to 60 seconds. If XML Spy took longer than 60 seconds to get a response back, "B" could still be your problem.

To definitively check A:

Step 1. Identify what port number the SOAP adapter is calling on the receiving system.

You can find the port number by looking at the URL you've configured for calling the Web service (or buried in the WSDL you imported). The format is "http://[hostname].mycompany.com:[port]/blah/blah/blah" The number after the colon is the port number. If there is no port number (i.e. it's a simple URL like http://www.ebay.com/mypage), then the port number defaults to 80 for HTTP, and 443 for HTTPS.

Step 2. Check if the port is open

Log in to each PI app server (to a command prompt)

Enter "telnet [hostname] [port]". That's if PI is running on windows. Some operating systems may format it like "telnet [hostname]:[port]"

Example:

C:> telnet www.ebay.com 80

If the screen goes blank, or tells you that it has connected, then the port is open. If the screen just sits there trying to connect (and eventually, after a long while, timing out), then talk to your network administrator about opening the ports.

A note of common frustration on opening ports. If you are using virtual IP addresses on your PI server (which most companies do these days), then the PI hostname is not the one that needs to be opened in the firewall. Most operating systems the request to the firewall using a static IP on the server. The best way to figure out what IP you need to use is to have your network admin watch the firewall logs as you force PI to call the Web service. He can find the correct IP and port number from those logs.

--Dan King

IBM Global Business Services