SOAP Error- Connection refused by remote host

[former_member235717]

Hi All,

I have a ECC to third party web service interface where I'm using Proxy on the sender side and web service on the receiver side.

I have configured all the necessary data in SOAP comm channel. Data is flowing through ECC and PI but on the receiver side the following error "Connection closed by remote host." has occurred.

I have posted the same issue sometime back in SDN and found out that the networking team has to add the firewall rule.

But my new issue is, since after all the setting done on networking side, I still see the same issue.

In receiver comm channel, I'm configuring the proxy to send the call outside the server. When I try to execute the payload in SOAP UI outside the company network I'm able to see the response back.

Please help!!

Thank you!!

[former_member235717]

Hi All,

Thank you all for your response. However we couldn't able to find out the reason for failure. SOAP UI works but in PI we are still receiving "Connection refused" error.

The only difference I see in PI perspective is the change in the format of tags in payload.

PI is sending the payload as:(RWB)

<?xml version="1.0" encoding="UTF-8" ?>

- <ns1:empdata xmlns:ns1="http://XXX.com/XXX/">

<ns1:name>XXX</ns1:name>

<ns1:values>XXX</ns1:values>

<ns1:values2><![CDATA[XML code]]></ns1:value2>

</ns1:empdata>

   In SOAP UI  (The format looks like)

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rar="http://XXX.com/XXX/">

   <soapenv:Header/>

   <soapenv:Body>

      <rar:empdata>

         <!--Optional:-->

         <rar:name>XXX</rar:name>

         <!--Optional:-->

         <rar:node1>XXX</rar:node1>

         <!--Optional:-->

         <rar:node2><![CDATA[XML code]]></rar:node2>

      </rar:empdata>

   </soapenv:Body>

</soapenv:Envelope>

Here in SOAP I'm simple pasting the values in name, node1 and node2. So it works .

Does this change in format of payload tags is effecting the interface?

Please help.

Thanks!!

[Former Member]

I think that if you can execute the service from SOAP UI outside the company network maybe there is a problem with the network configuration inside the company.

Infrastructure team should be capable of give you a solution. Ask them if the legacy service endpoint is visible from PI server.

regards

[Former Member]

Hi Swetha,

Most of the times this error will come due to firewall issue in network, you said its fine.

Try to check certificates, if any expired (begin and end date), if certificates validity is proper try to reimport and see. Still problem exist set higher trace level and check the error. Once you finish tracing revert back the changes as it will consume more memory.

Thanks & Regards,

A.Neelima.

[former_member235717]

Thanks I will check accordingly.

Also, I know it doesn't make any sense but just to confirm, the webservice is sending a response back but we have designed the interface as ASY and not handling the response. Is the issue because of this design?

[iaki_vila]

Hi Swetha,

Even in async scenarios if there is a http error the endpoint will response this http error, it isn't any issue in your scenario.

Regards.

[Former Member]

It won't, Here error is data is not going to target only, first will resolve it once it reached target with out any problem, response message will come in to the picture , Best way is you can ask target people that not to send any response as you are not handling, so there is no point in them to send response.

Thanks & Regards,

A.Neelima.

[former_member235717]

Ok thank you Neelima and Inaki.

We did re imported the certificates and has set the trace to high level. Still it shows the same issue. Actually in my case certificates is not manadatory as per the target system details. But we are trying in all possible ways to check.

I did check the webservice in SOAP UI outside the company network without any certificates in the UI tool and it gave the response back.

 

[Former Member]

can you share the trace.

One more try, try to trouble shoot by using TCP gate way.

Thanks & Regards,

A.Neelima.

[former_member235717]

Here is the trace:

>

#2.0^H#2014 03 17 13:23:57:514#0-400#Error#com.sap.aii.af.sdk.xi.srt.CallerServiceImpl2#
#BC-XI-CON-AFW#com.sap.aii.af.lib#4201520A5D02B0D200000001003C008A#411060350000001376#sap.com/com.sap.aii.adapter.soap.app#com.sap.aii.af.sdk.xi.srt.CallerServiceImpl2##0#SAP J2EE Engine
JTA Transaction : [18ffffff80487e05e176]#50C5A6D07D2C11E3CFF44201520A5D02#50c5a6d07d2c11e3cff44201520a5d02#50c5a6d07d2c11e3cff44201520a5d02#0#XI SOAP[cc_rcv_ra_test//]_7108482#Plain##
Error in call over HTTP: HTTP 0 null
[EXCEPTION]
java.io.EOFException: Connection closed by remote host.

I tried using TCP gateway but nothing I can see. I have provided the Host and port  as the proxy host , port which I used in Receiver comm channel config

[Former Member]

Helpful links:

http://scn.sap.com/thread/1668695

https://scn.sap.com/thread/1372529

Thanks & Regards,

A.Neelima.

[former_member184720]

Hi Swetha -

As you have confirmed that you could receive the response when you test outside the n/w, for me it's clear that it's a network issue.

May be you can request your n/w team to re-validate if the ports are open and no firewall restrictions in place.

You can also make use of TCP Gateway

[former_member235717]

Harish,

I did check with them. It seems it looks good on their end.

Basis gave us the same error log which I'm seeing in PI RWB.

Sometimes we get the following message too

"Invalid SSL message, peer seems to be talking plain!" . But when I run the report in ECC without any changes the error again changes to "Connection refused by remote host!!"

[Harish]

Hi Swetha,

are you using SSL in scenario? Please check authentication configuration for receiver soap adapter.

regards,

Harish

[former_member235717]

I checked with and without authentication. Sam error in both the scenarios