Synchronous messages through Soap Adapter

[Former Member]

Hi XI Guru's

In my scenario I am sending a synchronous soap message over soap adapter. Message flow is like

3rd Party Application --> XI --> SAP R/3.

My message do get processed in SAP R/3 and I do get response in SXMB_MONI as well as in Message Monitoring in RWB.

The return message for message f1bdf1d0-cec5-11de-a9c0-0050569626f6(OUTBOUND) was successfully passed to the waiting "call" thread.

2009-11-11 05:27:26 Information The message status was set to DLVD.

2009-11-11 05:27:26 Information SOAP: response message entering the adapter (call)

2009-11-11 05:27:26 Information SOAP: response message leaving the adapter

But still the response from XI does not reaches 3rd party application.

On digging the logs I found following message. Can this be an issue in XI which is blocking the reponse message from reaching the 3rd Party Application.( I tried posting the message through XML spy and I do get the response in XML spy.)

(Note : My XI Installation has central adapter engine)

#1.5 #0050569626F6004200000D0B00000B5000F66675B4B8DEA5#1257401122698#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/com.sap.aii.adapter.soap.app#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#LOVEIN#25369##sapnw03_NPI_6935550#Guest#2fd59d51c9d111debb440050569626f6#HTTP Worker [4]##0#0#Warning##Plain###Cannot send an HTTP error response [500 "Application error occurred during the request procession." (details: "The WebApplicationException log ID is [0050569626F6004200000D0800000B5000F66675B4B8DEA5].")]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: *The stream is closed.*

+ at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.ensureOpen(ServletOutputStreamImpl.java:354)+

Any help in this regard is appreciated .

Thanks

Lovein

[p_boeijen]

Hello,

I found the sap note 1028961; and i managed to create the u201Ccom.sap.aii.af.axisproviderlib.sdau201D

But somehow it doesn't register in the JSPM.

I can't deploy it in PI 7.11

Maby someone has the solution for this problem?

Regards,

Patrick

[Former Member]

Dear Experts,

I also getting error in depolying that file using JSPM in PI 7.11.

Thnaks,

ajai

[p_boeijen]

Hello,

Did anyone find a solution for this yet?

I'm running into the same problems edited the web.xml. I commented out the security settings. To dissable the logincheck for the soap adapter.

But somehow it doesn't register, even with a stop start of the complete Java Stack.

On a PI 7.0 environment this solution works but on PI 7.1 it doesn't.

Thanks in advance,

Regards,

Patrick

Edited by: P. Boeijen on May 20, 2010 11:14 AM

[stefan_grube]

> On a PI 7.0 environment this solution works but on PI 7.1 it doesn't.

No, PI 7.1 does not support this workaround.

You can use Axis adapter where you can configure anonymous logon.

[former_member200962]

In addition with checking the timeout...also check if the sender application is designed properly to receive the response....error code 500 means that there is some problem with the source system (one if the possibilities)

Regards,

Abhishek.

[Former Member]

Thanks for your reply Stephan / Abhishek.

To add some more info on the issue. This issue is when I am using PI 7.1 version.

I do not face the issue if I use XI 3.0 and end to end flow works fine and response message reaches 3rd party application.

Only difference I have in 2 versions is that in XI 3.0 we have been able to disable the soap adapter authentication (by changing web.xml file) where as in PI 7.1 we have not been able to disable that authentication and userid/ password info has to be provided while sending the soap message from 3rd Party application.

(Security if not disabled gives 401 message as described on following blog [|] )

On the other note do you guys know a way to disable this authentication on PI 7.1 version.

Thanks ,

Lovein

[stefan_grube]

Check the timeout settings of the sending system.

Maybe there is a timeout before the response is sent.

Check also execution time of RFC.