Hello,

I have a problem with the processes, they sleep after a few minutes, and I don't know why this problem occurred.
I try to restore the server, iisrest and deploy, but I was unsuccessful.

May someone help me?


thank you.

Monitoring/Environment Health/Scheduler

Is it producing any stack or verbose log?

Hi Agno.

Processes go to sleep whenever there's nothing for them to do.

For example, if your processes are composed of only human activities, the process itself will execute very briefly (just to advance from one human activity to the next), and then go back to sleep again until the next human activity is closed. All of the transactions required for the human activity will be done in screens (or even outside of the system - for example, phoning a customer or physically signing a paper report).

Even if your process has automatic activities, it will wake up, execute the automatic activity, then go back to sleep again. So unless you have long transactions happening in your process (which you SHOULDN'T - leave long transactions to timers), it's very likely that all your processes will be sleeping at any given time. Those lazy bastards!

# I have a case as well for Java Stack in production environment, is there having to do with this sleeping activity?

# there is log like activity does not exist

# there is no lock process/sub process

# there is no impact analysis?

# and mostly record goes thru bpt smoothly

# but a few (we experienced about 3 records in different days) that is stuck on IF widget activity (at the node start) and has status waiting

# Miracelly, it runs again at mid night and succeed.

# Can anybody explain this case?

Thank you very much, 

regards,

Your case could be caused by multiple issues. It will probably be due to some concurrency issue - BPT uses its own database transactions, and in that case it could run into deadlocks with other transactions on your system.

When you talk about an IF widget, I suppose you meant a Decision activity? It has the same icon as the If node, but it behaves very differently. Decision activities execute code, and if that code throws an error it will be left in an error state. I'm not sure why you have a "Waiting" status though - I believe the "Waiting" is only used for Wait, Human and Automatic activities. But in any case you should contact OutSystems support, they will help you troubleshoot this problem.

Thank you Sir,

# If it is deadlock how come it recovered itself after several hours? 

# Why it is only a few records (3 out of 40000) in different days?

# Correct, i mean Decision activity.

# yes, it is waiting when in the service center - that decision activity is not finished

regards


leonardo.fernandes wrote:

Hi Agno.

Processes go to sleep whenever there's nothing for them to do.

For example, if your processes are composed of only human activities, the process itself will execute very briefly (just to advance from one human activity to the next), and then go back to sleep again until the next human activity is closed. All of the transactions required for the human activity will be done in screens (or even outside of the system - for example, phoning a customer or physically signing a paper report).

Even if your process has automatic activities, it will wake up, execute the automatic activity, then go back to sleep again. So unless you have long transactions happening in your process (which you SHOULDN'T - leave long transactions to timers), it's very likely that all your processes will be sleeping at any given time. Those lazy bastards!


Hello Leonardo,
Thank you a lot for explanation,
In my case i have only automatic process, however, how many seconds is the limit for execute a process ?

 (10,20, 50.. seconds - 2 minutes). Maybe i have long process in execution.
Thank you more one time.

this wrote:

# If it is deadlock how come it recovered itself after several hours? 

# Why it is only a few records (3 out of 40000) in different days?

Deadlocks are not permanent. They can be resolved, usually by kiling one of the processes. And I can't really answer your second question without knowing more details about the case.

But please contact support to have that sorted out.

Solution

Agno, the timeout for automatic activities is 5 minutes: https://success.outsystems.com/Support/Enterprise_Customers/Maintenance_and_Operations/BPT_-_Automatic_Activities_Timeout

If I wasn't clear enough... sleeping activity processors are completely normal, even if you have active processes, because a process is only brought into execution at particular times.

Solution