Async r3->xi->soap problem.. no soap msg sent from SOAP receiver adapter

[Former Member]

Hi guys!

I have an issue with SOAP scenario. I have ABAP Proxy->XI->SOAP async scenario. When I send msgfrom r3, it arrives into XI, but no SOAP message is sent to the target url. In the SXMB monitor, the flag is delivered The status of adapter is not valid. error: target url is invalid. messages crash at timeout. But when I test it from other tools, the target web service worx fine. One more info: we use stand-alone adpater engine. I tried it also on the integrated one, but it didn't work.

Sync scenarios work fine: SOAP->XI->R3->XI->SOAP.

Any ideas, what could be wrong? Are there some special requirements, for message interfaces (do they need 2 b sync??) or something else?

Thanx, Olian.

[MichalKrawczyk · Accepted solution]

Hi,

what do you see in:

http://xihost:port/MessagingSystem/monitor

link (audit log) do you see any more details about the error?

>>>>for message interfaces (do they need 2 b sync??)

of course not - they need to be async if you use async communication

Regards,

michal

[Former Member · Accepted solution]

Hi Michal!

First, I even didn't know about this monitoring tool it's gr8.

Well, I found error: MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction:

Any idea?

I'm going to study something about it, but if you know, let me pls info!

Thanx a lot!

Olian

[Former Member · Accepted solution]

Aaaaa, I thought, it's ok. Now I get other issue:

SOAP: call failed: java.net.SocketException: Connection timed out:could be due to invalid address

But I'm sure, that adress is correct..

Any ideas?

Olain

Message was edited by:

Olian Saludew

[MichalKrawczyk · Accepted solution]

hi,

are you sure XI has access to your web service?

(firewall etc) ?

Regards,

michal

[Former Member · Accepted solution]

Michal, if I use sync scenario: SOAP->ABAP PROXY->SOAP, everything worx fine. I get response. And it uses the same AE, so the net should be ok...

Strange...

O.

[Former Member · Accepted solution]

uffffff...

I'm a little in shame to say it

guys, always check the targets!

O.

[MichalKrawczyk · Accepted solution]

Regards,

michal

[Former Member · Accepted solution]

Hi Olian,

We are also getting the same error 'SOAP: call failed: java.net.SocketException: Connection timed out:could be due to invalid address'

From XI the file is not going to third party system.

Could you please provide the solution.

Your early response is highly appreciated.

Many thanks in advance.

Jitender