SOAP Receiver adapter on 7.4 AEX exeeds synchronous timeout

[Former Member]

I have a problem with NW 7.4 AEX (single stack) with synchronous SOAP calls ( SOAP- AEX- SOAP)

I'am not able to get a response from SOAP Receiver channel, I always get a MessagingExpiredException.

My scenario:
1a. webservice client calls AEX with SOAP-sender-channel
2. AEX calls other webserver - this works  ( JBOSS in my case. I see it in the jboss log)
3. AEX throws a MessagingExpiredException, message log shows "Synchronous timeout exceeded"

My other tests:
4. set the parameter syncTimeout in SOAP_CHannel for Module CallSapAdapter does not change anything
5. Asynchronus communication works with changing the SOAP-sender-channel to "Exactly one"
6. webservice client calls JBOSS direct : works

In the forum discussion is mentioned the "XPI Inspector" (SAP Note 1514898) instead of trying to set the SOAP adapter log level to DEBUG.

Any ideas ?

Kerstin

Hier are the message logs:

messagelogs.txt.zip

[Harish]

Hi Kerstin,

You can increase the timeout. please refer the below discussion

In the SOAP Receiver adapter:

Under the module tab:

Go to the module configuration and add the below key values:

Module Key                  Parameter name              Parameter Value

your key name          XMBWS.Timeout                 give your value in milliseconds.

regards,

Harish

[Former Member]

Hi Harish

I tried with syncTimeout 30000 - does not help

[Harish]

Hi Kerstin,

Synctimeout should work in your case. Please refer the below doc , it might help

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03...

regards,

Harish

[Former Member]

Hi Kerstin,

How did you resolve this issue?

We are facing same issue, help is greatly appreciated.

Thanks

[former_member184720]

Hi Kerstin - Did you test your webservice with Soap UI? Are you getting the response from the webservice?

[Former Member]

Hi Haresh,

yes - I tested with SoapUI: JBoss without AEX works fine, SoapUI - AEX - JBoss doesn't work

regards

Kerstin

[former_member184720]

Hi Kerstin - How long does it take to get the response when you tested it from SOAP UI?

Also did you test it with same request message from SOAP UI & AEX?

[Former Member]

with AEX: this depends on "syncTimeout" in CallSapAdapter

without AEX: milliseconds

[Former Member]

Hello,

I think the problem is with ur request. So, I would suggest you to use XPI Inspector and compare the request which you are sending from PI and SOAP UI.

Thanks

Amit Srivastava

[former_member184720]

Hi Kerstin - Can you also confirm if you are sending the same request message from SOAP UI & AEX?

[Former Member]

Hi Armit

do you know from where I can download the XPI inspector ?

Do I really have to make an OSS call ?

regards

Kerstin

[Former Member]

yes - the same request message

[former_member184720]

Hi Kerstin - Refer to the note # 1514898 - XPI Inspector for troubleshooting XI

[Former Member]

Hello,

No, u don't need to make any OSS call.

In the note which u have mentioned above u will find one sda file just deploy the same on ur PI server

I remember there is a blog on the same

Thanks

Amit Srivastava

[Former Member]

Michal's PI tips: XPI inspector - help OSS and yourself

[Former Member]

Hi Amit,

SAP has made the version 71 of SAP-Note 1514898 without any ear-file.

I looked for the last version with attached ear-file.

This is version 69 - now I can try the XPI inspector

thanks

Kerstin

[former_member184720]

Hi Kerstin - You might want to have a look at the below blog which talks about additional features available in analyzing the issues -

http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/03/03/michals-pi-tips-xpi-inspector--ne...

[Former Member]

Hi Guys,

I was able to get xpi_inspector and deploy the ear-file to my AEX-Server. I tried also a synchronous JDBC Receiver adapter - that means a SELECT statement to a database.

My result:

• synchronous SOAP receiver adapter and JDBC receiver adapters work, if there is no inbound mapping used
• with inbound mapping comes always the timeout
• a big syncTimeout  does not help

regards

Kerstin