Skip to Content
0

Failed to get the input stream from socket: java.net.SocketException: Connection reset

Apr 28, 2017 at 02:56 PM

2.5k

avatar image

Hi,

Getting below exception in soap receiver where

1) target url i can able to open in browser and

2) url able to access through server also

3) getting response when i call the url in soap UI, So assuming client service is running &up.

4)IP whitelisted and port opened for the service and can able to do telnet to the destination

5) If i ping soap receiver channel it is showing unable to connect to the target url

6) Also checked SSL and TLS version which was same in both ends i.e TLSv1.2

Earlier same was working which is not working now.

Please suggest

SOAP: Call failed: java.io.IOException: Failed to get the input stream from socket: java.net.SocketException: Connection reset SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Failed to get the input stream from socket: java.net.SocketException: Connection reset MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Failed to get the input stream from socket: java.net.SocketException: Connection reset Exception caught by adapter framework: java.io.IOException: Failed to get the input stream from socket: java.net.SocketException: Connection reset Transmitting the message to endpoint using connection SOAP_http:// sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Failed to get the input stream from socket: java.net.SocketException: Connection reset

Regards

Pavan Kumar D

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Andrzej Filusz Apr 28, 2017 at 03:15 PM
0

Hi Pavan,

Could you use an XPI inspector to get more details about what goes wrong during a handshaking process please?

Maybe a certificate on the target side has been changed for a new one? If yes then get it from the target side and import it into the TrustedCA. And don't forget to restart your communication channel after that.

Regards,

Andrzej

Share
10 |10000 characters needed characters left characters exceeded
Pavan Dogiparthy Apr 29, 2017 at 11:34 AM
0

Hi,

Thanks for your reply below are the traces i can see from xpi and earlier it was different when it got worked now they made changes getting exceptions while testing with their new certificate and cross verified the certificates with client also configured the same in nwa.

Begin IAIK Debug: ssl_debug(14): Starting handshake (iSaSiLk 5.104)...

ssl_debug(14): Sending v3 client_hello message to server URL, requesting version 3.3...

ssl_debug(14): Sending extensions: renegotiation_info (65281), signature_algorithms (13)

ssl_debug(14): IOException while handshaking: Connection reset

ssl_debug(14): Sending alert: Alert Fatal: handshake failure

ssl_debug(14): Exception sending message: java.net.SocketException: errno: 32 (Broken pipe),

error: Write failed (local port source port to address sourceIP (domain name), remote host unknown) ssl_debug(14): Shutting down SSL layer... ssl_debug(14): Closing transport...

Regards

Pavan

Share
10 |10000 characters needed characters left characters exceeded
Andrzej Filusz Apr 30, 2017 at 11:00 PM
0

Hi Pavan,

Ok, you received a "Broken pipe" exception cos you tried to write to a closed connection. But it's still unclear to me why your connection is closed. What are you XPI Inspector settings?

Regards,

Andrzej

Share
10 |10000 characters needed characters left characters exceeded
Pavan Dogiparthy May 09, 2017 at 06:05 AM
0

It is certificate issue at server side they have provided new certificate then it got resolved

Regards

pavan

Share
10 |10000 characters needed characters left characters exceeded