Error with Soap Receiver Adaptor

[Former Member]

Hi Experts,

We have imported files from XI 3.0 to PI 7.1 .

In RFC <---> SOAP scenario , we are getting the below error in PI 7.1 but its working fine with the same url on XI 3.0

SXMB_MONI -

---

> com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect

Runtime Workbench -

---

>

Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect

How can i solve this error.

Regards,

Syed

[Former Member]

We solved this error by changing the url from Service to Servlet.

What is the difference between using Service and Servlet in URL?

Regards,

Syed

[Former Member]

Hi Umar,

We are facing same issue and message we can see in PI Java Stack Comm Channel Monitoring.

Can you confirm with some details as how you resolved this issue.

Alim

[Former Member]

Hi Zahid,

The SOAP action is not defined. I have directly imported the scenario from XI 3.0 . Its not defined in XI 3.0 also.

Regards,

Syed

Edited by: Umar Syed on Feb 16, 2009 1:38 PM

[Former Member]

try defining SOAP action. moreover clear CPA cache aswell and try again.

Good Luck

[Former Member]

Its a local network and its only one xml message.

Regards,

Syed

[Former Member]

are u describing soap action ?

[Former Member]

Hi Zahid,

The URL is correct as its working in XI 3.0

the message in monitoring is

Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect

Regards,

Syed

[Former Member]

hmm... connection timeout can be due to many reasons:

incorrect proxy settings is one, are u accessing your web service on internet or is it in local network.

are u describing SOAP action in communication channel.

Another problem we once faced was hierarchy of the both messages ( our message being mapped to WSDL message) and it gave "Time out" error as well than. Do u have straight (one level xml) message or more than one.

In our case, we had to define request and response messages of our message interface exactly of same hierarchy, as that of WSDL which allowed proper posting of SOAP request.

good luck

do keep us posted of any developement..

[Former Member]

Services are up and running,

In XI 3.0 no proxy server details have been configured but its working with XI 3.0

Regards,

Syed

[Former Member]

can u provide log from communication channel monitoring, secondly, check the URL, and SOAP action, is it correctly defined ?

[Former Member]

Hey,

You have to mention the Proxy server details in SOAP adapter ( If You are Under proxy server).

Check the SOAP Connectivity using a WSDL Client.

BR,

Sainath

[Former Member]

Firewall is disabled on both the systems .( PI 7.1 and SOAP) Provider.

Server is up and running as we can run the same scenario with XI 3.0

Regards,

Syed

[markangelo_dihiansan]

Hi,

When the connection refused or timeout error happens, this is usually caused by:

1. Too many messages that are being processed by the receiving server

2. The receiver system is down

You can try resending the messages.

Hope this helps,

[Former Member]

Hi,

Please check if target system is down, in such cases you get the message.

Also check if you are transferring all the parameters in communication channel from xi 3.0 to 7.1 such as proxy server etc.

Regards

Ravijeet

[Former Member]

Hi,

Keep the Firewall port oen for the new system.and try.

Thanks and Regards,

Raju.P