cancel
Showing results for 
Search instead for 
Did you mean: 

Synch send from BPM

Former Member
0 Kudos

Hi all,

I have a synchronous send step to a webservice from my BPM.

I am getting the error com.sap.aii.af.ra.ms.api.DeliveryException: No response available. after 3 mins the call is made.

My webservice would take some time to response hence i would like to increase the timeout threshold. Any idea how how can i achieve this?

I have set the variable XMBWS.Timeout in Soap Adapter Module to be 10 mins however i am still getting that error in moni.

Appreciate any help.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi all,

I have solved the problem

In Visual Admin, Under the service SAP XI Adapter: XI

The time can be increase using this property.

xiadapter.inbound.timeout.default

Appreciate all helps.

Former Member
0 Kudos

Hi all,

What i meant was after i have set XMBWS.Timeout in Soap Receiver Adapter Module to be 10 mins, I am still getting the error in SXMB_MONI after 3 minutes the message was sent from PI to the SOAP Receiver.

So are there any more settings to increase the timeout?

There is absolutely no problem with the web service. It is just taking a much longer time to response.

Appreciate any response.

Former Member
0 Kudos

HI

Increase the HTTP_TIMEOUT in SXMB_ADM to 10 minutes as well and try

Thanks

Gaurav

Former Member
0 Kudos

I have set HTTP_TIMEOUT to be 600 in SXMB_ADM, however i am still getting the error after 3 mins in SXMB_MONI.

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: No response available.</SAP:AdditionalText>

Any more advices?

Thank you

Former Member
0 Kudos

Hey,

I guess the http_timeout is in millisec so if you want it more then 3 mins you need to set it above 180000.

regards,

Milan

Former Member
0 Kudos

Milan: HTTP_TIMEOUT is in seconds, 3 mins is 180.

Former Member
0 Kudos

Hi

After increasing the time out this should be solved. IF not then the problem is target system downtime or network and that you cannot control. At max you can schedule automated restart of failed messages

1. IS_ENTRY - change the number of retries TUNING IS_RETRY_LIMIT

2. A mass restart by scheduling RSXMB_RESTART_MESSAGES

Thanks

Gaurav

SudhirT
Active Contributor
0 Kudos

Hi,

I dont think increasing timeout will solve ur problem.

Whenever u see this error,plz check if the target/receiver system is up

and there r no issues with network connectivity.

Thanks!