Time out for Client Proxy

[Former Member]

Hi All,

I have a scenario, where ECC sends a request to a BPM synchronously. The BPM can sends a response back immediately, if it is a success, else sends the response back to ECC after 2 minutes, if there is a communication failure.

But for the second case, ECC is throwing HTTP 500 error within 1 minute.

We tried to set up the parameter icm/keep_alive_timeout to 180 in ECC side, but it is going into error in exact 60 seconds.

Could you please suggest a solution?

Regards,

SS

[Shabarish_Nair]

can you confirm if the return code of the BPM in SXI_CACHE is 0?

[Former Member]

yes , It is 0. For the success, I am finding the desired result. I checked the work flow monitor. The exception is triggered for communication failure, and the deadline branch is executed. As the connection is terminated by that time, the message is not being able to sent back to ECC.

Do I need to tune the same parameter for PI? Because I am getting HTTP error, it gives me a feeling that time out at ICM level.

Regards,

SS

Edited by: Subhendu Sahu on May 9, 2011 3:09 PM

[Shabarish_Nair]

try to increase the HTTP_TIMEOUT parameter in SXMB_ADM of ECC and PI.

Also try to delete all ERROR work items from SWWL

[Former Member]

There is no error under SWWL. I tried to set the value for HTTP_TIMEOUT to 180 second, but it is still not working.

But appreciate your help and guidance.

Regards,

SS

[naveen_chichili]

try increasing the parameters to icm/conn_timeout = 900000. icm/HTTP/max_request_size_KB = 1507152 .

[Former Member]

I set the same parameter icm/keep_alive_timeout in PI to 180 and it worked. HTTP 500 means the client did not get a response from the server because of some reason. For our case, ECC is the client and PI is the server. PI closed the HTTP connection after 60 seconds, which was the default value for icm/keep_alive_timeout . Thus ECC could not get the response it was waiting for(As the BPM 's deadline is set to be 2 minutes, thus PI could not send back the response in 60 seconds), resulting in HTTP 500 error.

Edited by: Subhendu Sahu on May 10, 2011 7:35 PM

[Former Member]

Usually error 500 referred to Internal server error... probably message structure is wrong..