cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP Sender Error: Connection Refeused

Former Member
0 Kudos

Hello,

My scenario;

1st: ABAP Proxy to PI to SOAP Sender(Third Party)

2nd: Idoc to PI to SOAP Sender(Third Party)

We have tested the endpoint URL using SOAP UI and its working without error.

But when try to do a test from RWB using Integration Engine, message is delivered successfully, no error in sxi_monitor but in communication channel, we get and error SOAP: call failed: java.net.ConnectException: Connection refused

Our Webserver communicates through 8080 port and which has been opened for communication.

also we are able to ping the webserver through PI.

Any input will be helpful

Regards,

Abhishek

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

> But when try to do a test from RWB using Integration Engine, message is delivered successfully, no error in sxi_monitor but in communication channel, we get and error SOAP: call failed: java.net.ConnectException: Connection refused

This is connectivity issue, have you checked the below threads

http://forums.sdn.sap.com/thread.jspa?threadID=444378

http://forums.sdn.sap.com/thread.jspa?threadID=1364587

Regards,

Venkata Ramesh

Answers (5)

Answers (5)

Former Member
0 Kudos

The RFC destination maintained for Idoc to SOAP sent from R/3, the client was wrong in RFC.

Former Member
0 Kudos

Hi,

Please go through this thread

[http://forums.sdn.sap.com/thread.jspa?threadID=1988766]

Regards,

Venkata S Pagolu

iaki_vila
Active Contributor
0 Kudos

Hi Abhishek,

Does your backend use special security like wsse?, is it a simple SOAP protocol?

Regards.

Former Member
0 Kudos

Hello,

This is a simple SOAP protocol.

Regards,

Abhishek

former_member184681
Active Contributor
0 Kudos

Hi Abhishek,

Make sure that you typed the correct Target URL and SOAP Action in the receiver Communication Channel parameters. This is the most common reason for communication problems, when you are able to successfully ping the target location. Most importantly, make sure that the URL does not contain the "?WSDL" ending and that SOAP Action is in accordance with the .wsdl file contents.

Hope this helps,

Greg

Former Member
0 Kudos

Hello,

Thank you for your replies,

The URL address mentioned in correct, when i use the same URL, in the testing tool like SOAP UI, i do get a response back from the web service, but when i do the same from PI, it gives me connection error.

I have also maintained authentication for user, ie the user id and password.

Regards,

Abhishek

Former Member
0 Kudos

My scenario;

1st: ABAP Proxy to PI to SOAP Sender(Third Party)

2nd: Idoc to PI to SOAP Sender(Third Party)

i think ur scenarios is soap sender to Server proxy is it correct

if coreect then once you check the wsdl file whatever u was generated in sender agreement:

if ur scenario is Proxy to Soap :

once you check target url and actions in Receiver comm.channel.

please Elaborate ur issue and scenario and once you check the below blog

http://forums.sdn.sap.com/thread.jspa?threadID=2132278

Former Member
0 Kudos

Hello,

The WSDL has been provided by the Third Party, and when they test using the same wsdl, in SOAP UI, they are able to successfully test.

But when we try it from PI, we get an error connection refused.

Regards,

Abhishek