373
Views
5
Comments
Process does not trigger, gives Request timeout error
Question

Hi all,

I am facing an issue in Outsystems 9.1.x on Java platform where intermittently a process does not trigger from one of my actions.

The same  process is triggered from different screens within the application and I get the request time out only in some invocations.

I see the following errors in the Service Center logs.


Request timed out

outsystems.hubedition.util.OSRequestTimeoutException: Request timed out

   at java.lang.Thread.getStackTrace(Thread.java:1552)

   at outsystems.hubedition.util.OSRequestTimeoutException.<init>(Unknown Source)

   at outsystems.hubedition.http.iiIiiiiiIIiIi.checkPoint(Unknown Source)

   at outsystems.hubedition.http.HttpContext.checkPointForAbortion(Unknown Source)

   at osespacename.actions.ActApplication_Create_Search.executeApplication_Create_Search(Unknown Source)


There are no slow sql's seen in the General logs and no "Active instances with Errors" and "Suspended" instances of this process Search.

Could someone suggest what could be the cause of this Request timeouts and from an environment perspective what can be verified to ensure that process is triggered successfully.


Thanks,

Ayan

2019-11-12 17-31-26
Justin James
 
MVP

Ayan -

Strange. Any DB locks open for too long?

J.Ja

2018-05-16 11-16-36
João Heleno
 
MVP

@Ayan

How are your processes launched? On an entity create or explicitly with Launch action?  

UserImage.jpg
Ayan Sen

João Heleno wrote:

@Ayan

How are your processes launched? On an entity create or explicitly with Launch action?  

The process is launched with a Launch action


2020-06-08 02-42-28
Wasabi

HI Sen,

Timeout could be caused by many things:

1. Network busy / no connection 

2. Firewall

3. Caching in internal Database

etc..

If all being well, the process should be launched smoothly.

If you call it from application, try to loop, say it 5 times or if you call it in a process - so it is a child/sub process - it will be retried automatically when you put the launch_process in an activity... and the interval of trying is bigger and bigger..

regards,

UserImage.jpg
Ayan Sen

I think the issue was due to using Entity Action - GetActionForUpdate which was causing lock on the  table in a separate action (not from the process). We changed that to fetch the data using an aggregrate and update.

After the above change we have not seen any further timeouts today.

Thanks all for your help.



Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.