cancel
Showing results for 
Search instead for 
Did you mean: 

Exception in request: java.net.SocketException: Connection reset

Former Member
0 Kudos

Hi,

We are trying to send a message from SOAP UI to XI. However, we are getting an error "Exception in request: java.net.SocketException: Connection reset"!

This error is only occuring when trying to send messages to XI via port 50000. We tried sending messages via other port, and it worked. However, we tested whether we could send the message to XI using the URL with port 50000 in XI RWB, and the result came successful!

The client, however, wants us to use port 50000 only.

Weirdly, as far as we could investigate, both XI port 50000 and SOAP UI port 50000 are working fine !! We were able to send messages from SOAP UI to other XI environments using port 50000.

Here is the log in SOAP UI:

Fri Feb 15 12:06:33 GMT 2008:INFO:ofcomtols028:50000 requires authentication with the realm 'XISOAPApps'

Fri Feb 15 12:06:33 GMT 2008:ERROR:Exception in request: java.net.SocketException: Connection reset

Fri Feb 15 12:06:33 GMT 2008:ERROR:An error occured Connection reset, see error log for details

Fri Feb 15 12:06:33 GMT 2008:INFO:Error getting response for MI_CustomerBinding.MI_Customer:Request 1; java.net.SocketException: Connection reset

Please advice on this matter.

Regards,

Bhaswar

Edited by: Bhaswar Dasgupta on Feb 15, 2008 6:32 PM

Edited by: Bhaswar Dasgupta on Feb 15, 2008 6:39 PM

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

witch url are you trying to use?

keep in mind you need to use http://server:port/XISOAPAdapter/MessageServlet?channel=:service:channel.

regards.

roberti

Former Member
justin_santhanam
Active Contributor
0 Kudos

Das,

Did u gave the username and pwd in the SOAPUI?

raj.

Former Member
0 Kudos

Yes - we used the same id-pass when sending through port 8000 and port 50000. We even tested it in XI RWB ...its not an authorization issue.

Former Member
0 Kudos

Hi,

it can be an authorization problem. When you test in rwb, it does not go through icm, the message goes directly to the integration engine, and the role you need to authenticate on icm does not matter. Check if the user you are using has SAP_XI_APPL_SERV_USER role.

another things can be happening are related to security questions, like firewall, adapter timeout, etc... check these things.

Just a hint: I would suggest you to give points for people who are trying to help you, so more people will try to help you (it works when I post questions here in the forum

regards.

roberti