You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Normally when a worker encounters an error that can't be handled (e.g. an error is fired again from inside of the catch clause) the processing loop as well as worker thread will terminate.
Good example of this type of error is - in distributed setup - if the underlying MQ connection is terminated then basically all the workers stop and all workflow processing grinds to a halt. Currently such situation has to be monitored/discovered/handled by admins.
Proposed solution:
Add a property :restart-workers-on-error to systems so as it can be configurable to initiate a restart in case of such fatal error.
The text was updated successfully, but these errors were encountered:
Normally when a worker encounters an error that can't be handled (e.g. an error is fired again from inside of the catch clause) the processing loop as well as worker thread will terminate.
Good example of this type of error is - in distributed setup - if the underlying MQ connection is terminated then basically all the workers stop and all workflow processing grinds to a halt. Currently such situation has to be monitored/discovered/handled by admins.
Proposed solution:
Add a property
:restart-workers-on-error
to systems so as it can be configurable to initiate a restart in case of such fatal error.The text was updated successfully, but these errors were encountered: