Error when test an INterface with SOAP Sender CC

[Former Member]

Hello everybody,

I'm testing a Scenario that goes as follows Web Service Consumer-> PI 7.0 -> RFC, now I've already tried to test it with Altova XML Spy, and with the WebServcies Navigator Tool of UDDI, now I'm getting the next error in both cases:

HTTP/1.1 500 Internal Server Error

Connection: close

Server: SAP J2EE Engine/7.00

Content-Type: text/xml; charset=utf-8

Date: Tue, 16 Dec 2008 22:10:42 GMT

<?xml version='1.0'?>

<!-- see the documentation -->

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>

<SOAP:Body>

<SOAP:Fault>

<faultcode>SOAP:Server</faultcode>

<faultstring>Server Error</faultstring>

<detail>

<s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>

<context>XIAdapter</context>

<code>RecoverableException</code>

<text><![CDATA[

com.sap.aii.af.ra.ms.api.DeliveryException: java.net.ConnectException: Connection refused: connect

at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:157)

at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:850)

at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

]]></text>

</s:SystemError>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

now in the RW in the communication channel I', getting history as follows:

error ocurred

request received

but no more about it, and I can't see the message in SXMB_MONI, can anyone tell me something about what could be wrong, thanks in advance.

Regards.

[Former Member]

THANKS A LOT THE PROBLEM WAS AN HTTP PORT WRONGLY CONFIGURED IN SOME RFC'S, THANKS.

[SudhirT]

Check if the XI RFC destination is working fine. ALso check the sap note no.804124, 807000 .

Thanks!

[VijayKonam]

I think it is because of the logon details. Did you give authentication details in your test?

VJ