WebeService Retry Problem - RED CROSS After 1 Retry - Socket Timeout Error - 408

WebeService Retry Problem - RED CROSS After 1 Retry - Socket Timeout Error - 408 Error
All,
We have a WebService which sometimes gets a socket timeout error as follows:-
"The maximum time waiting for an operation to complete was reached (socket timeout)."

When we checked the Appian docs, it says that in case of timeout from a WebService, Appian retries automatically every 32 seconds for upto conf.retry.MAX_TIME_TO_LIVE=64800 .
forum.appian.com/.../Configuring_Automatic_Error-Handling.

This I believe is a 408 Request Timeout Error--> Request timeout (408): The Web server (running the Web Service) thinks that there has been too long an interval of time between the establishment of an IP connection (socket) between the client and the server and the receipt of any data on that socket, so the server has dropped the connection. The request from the client must be repeated - in a timely manner.

But in our case, the ret...

OriginalPostID-70465

OriginalPostID-70465

  Discussion posts and replies are publicly visible

Parents
  • ...ry does not seem to happen. Appian just stops after 32 seconds or 1 retry, puts a RED CROSS on the ACTIVITY and stops the process instance over there.

    Keep in mind, that we have indeed set the property to -->conf.retry.MAX_TIME_TO_LIVE=64800

    Therefore, it should retry every 32 seconds according to the docs for roughly 12 times or 18 hrs before it fails and puts a RED CROSS.

    But this is not happening?

    Any reason why?
Reply
  • ...ry does not seem to happen. Appian just stops after 32 seconds or 1 retry, puts a RED CROSS on the ACTIVITY and stops the process instance over there.

    Keep in mind, that we have indeed set the property to -->conf.retry.MAX_TIME_TO_LIVE=64800

    Therefore, it should retry every 32 seconds according to the docs for roughly 12 times or 18 hrs before it fails and puts a RED CROSS.

    But this is not happening?

    Any reason why?
Children
No Data