Skip to Content
0

SSL peer shut down incorrectly in SCPI

May 08 at 07:02 AM

64

avatar image

I'm trying to connect to a SOAP webservice via SCPI located on. The service recently changed its endpoint. So I imported the complete SSL key chain for the new service, similar to the old endpoint. Finally, I configured the following settings in the SOAP channel:


When trying to send data to this channel, I get an error:

org.apache.cxf.interceptor.Fault: Could not send Message., cause: java.io.EOFException: SSL peer shut down incorrectly.

When trying to send the same content via SoapUI a valid response is received from the service. The configured endpoint only supports TLS 1.2.

Is there a way to retrieve more information from SCPI besides this error message?

channel.png (98.4 kB)
error.png (78.3 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Aditya Sharma May 17 at 06:19 AM
0

Hi Iddo,

You can check the Target application's logs to get further information on this error, also, from CPI view, you can use the Tail log functionality in Eclipse on the IFLMAP node to get further details on this error with full JAVA stack.

You can as well enable the trace / debug of the iFlow from WebUI and re-run for a list of steps and the error received (though it rarely helps).

Thanks,

Aditya

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Thanks, but this doesn't give much more information besides "Remote host closed connection during handshake".tail-log.txt

tail-log.txt (6.7 kB)
0