SOAP Receiver

[Former Member]

Have an issue with new dev SOAP Receiver:

Connection times out with the below error

SOAP: call failed: java.net.SocketException: Connection timed out:could be due to invalid address

Connection is open and we can telnet the external server and also we can access the webservices,

Thanks for your assistance

[markangelo_dihiansan · Accepted solution]

Hello,

Can you check with your basis team regarding PI firewall? It is also possible that you are able to access/telnet the webservice locally, but in the point of view of PI you cannot.

Hope this helps,

Mark

[Former Member · Accepted solution]

We could infact telnet to their server from PI server...

[markangelo_dihiansan · Accepted solution]

Hello,

In that case, have you checked your proxy settings? Is the message you are sending very large?

Regards,

Mark

[Former Member · Accepted solution]

Hi Thanks for reply...we donot have forrward or reverse proxy for the setup in our landscape ..and the payload is just 10 lines ..so that should not cause any problem

[naveen_chichili · Accepted solution]

This could be the firewall problem....

[Former Member]

Thanks guys for these updates, we have raised an request with our N/w team to check the trafficfrom XI server to their N/w lets see what does it say ..will keep you guys posted

[anupam_ghosh2]

Hi ,

We get this exception in java as public class ConnectException extends SocketException

This just signals that an error occurred while attempting to connect a socket to a remote address and port. The connection is refused remotely (e.g., no process is listening on the remote address/port). Or a firewall perhaps, blocking your request ..

Maybe its a 504 Gateway Timeout

Connection timeouts occur when following steps happen:

1. The IP address for the requested server is successfully found

2. Connection establishment packets are dispatched to the IP address

3. The destination address deliberately ignores or does not receive them

Similar to connection timeout is Connection Refused, but in this case the destination system is actually sending packets back saying "go away, there is no service running on the port you are trying to connect to"

Your packets are just being lost.. either the system or some intermediate system is firewalled.. if you can't connect using telnet, a browser or some other app, its a network problem.

Secondly there is a limit to number of conncetions the server can accept, Say for example after 250 it would not accept further conncetions. In java we can normally set the conncetion timeout period while we create the socket as per code shhown below

Socket s = new Socket(); s.connect(new InetSocketAddress(my_hostName, my_port), 60000);

This code waits for 60 seconds to get connceted. A timeout of zero is interpreted as an infinite timeout. The connection will then block until established or an error occurs. But PI has a default timeout period set, so if your timeout value is more than the default period, this code won't have any effect. You can increase the default timeout period for PI and check if this is working. You can use the following link or take help of your BASIS team to alter the TIMEOUT period

http://documentation.softwareag.com/webmethods/xi_adapters/xie411/admin/configSapXi.htm

regards

Anupam