SOAP adapter Connectivity issue

[Former Member]

Sender: Database

Receiver: SAP ECC

Middleware: PI

Flow of the interface: Upstream system (US)->PI-> ECC

Type of communication: SOAP adapter (Upstream system (US) -> PI)

Problem: Connectivity gap occurred between Upstream system to PI.

1)    Our US system was unable to send the messages to PI and around 93 messages failed on US side and the below error occurred.

   Exception: Error Invoking Web Service Dispatch javax.xml.ws.WebServiceException: java.net.SocketException: Write failed: Broken pipe javax.xml.ws.WebServiceException: java.net.SocketException: Write failed: Broken pipe at”

2)    Our US team claimed that one of the PI cluster node is not responding so the messages failed at their side.

3)    After some time the messages were automatically processing from US system to PI normally and reprocessed all the failed messages .

4)     From PI perspective we have analyzed the issue and found that the every application server is working fine after they came up with issue, all the  communication channels are in green status, no error messages in PI and all the queues are clear.

Can any one of you suggest us where the problem might be.

Thanks,

Srinivas.

[baskar_gopalakrishnan2 · Accepted solution]

Glad that problem is resolved.  There could be firewall connectivity issue between US system and PI server cluster node. Your network team might have resolved by enabling port between these two. Or Cluster node is not configured to redirect the webservice call at the right port. These might be one of the reasons.

[former_member184720]

Hi Srinivas - .Personally i don't like an issue to be fixed automatically

As the issue is resolved now whatever we do it'll be just our assumptions but of course it'll help us to debug the issue whenever you get such issues in future.

As mentioned by Baskar it might be a network issue.

Based on the error message...Broken pipe means that the connection has failed. sometimes sending a huge sized files can cause this issue too..

Broken pipe message comes for a stream that could not deliver data to a socket.

If this max number of attempts cross then application assumes that socket is closed by other party and throws this exception.

If you get such issues in future - Ask your network to check for connection made from UI system(TCP IP tool)...

check your server availability..web dispatcher..server nodes..CPU utilization.. memory..xyz..

you can even try sending the same message from a soap UI..

Regards,

Hareesh