cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP: call failed: java.io.EOFException

Former Member
0 Kudos

Hi all,

I have build a proxy to soap scenario that generates errors during runtime. The scenario

consists of an ABAP program consuming a webservice through PI. The communication

channel shows the following errorlog:


- Message processing started
- request entering
- SOAP: call failed: java.io.EOFException: Connection closed by remote host.
- Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.
MessagingException: java.io.EOFException: Connection closed by remote host.

Does anyone know the cause of this error?

Thanks in advance.

Regards,

Ivo

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member181962
Active Contributor
0 Kudos

The webservice might have been down at that particular moment.

YOu can try manually to test the webservice by typing the url and see if you get any screen where you can enter your request.

Regards,

Ravi Kanth Talagana

Former Member
0 Kudos

Hi Ravi,

thanks for your reply. I just tested the webservice by entering the url in a browser. This works fine.

Regards,

Ivo

Former Member
0 Kudos

Hi,

does the inbound message type corresponds to WS signature?

Regards,

Dmitriy

Former Member
0 Kudos

Hi Dmitriy,

How can I check if the message type corresponds to the webservice signature?

I created the message type by importing the WSDL for this webservice.

Regards,

Ivo

former_member181962
Active Contributor
0 Kudos

Hi Ivo,

Is there any firewall in between your XI system and the webservice?

Can you check with your network folks?

It might be preventing the request from reaching the webservice.

Regards,

Ravi Kanth Talagana

Former Member
0 Kudos

I noticed in the monitor that it shows the inbound message first and then the outbound message.

Does XI show the messages in a random order or is this caused by an error in the interface?

Former Member
0 Kudos

Hi Ravi,

although I was able to reach the URL through a webbrowser, this problem was indeed caused by unavailability of the webservice. I just tried the connection without making any changes in PI and everything is working fine now.

Case closed.

Regards,

Ivo