Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitoring is not detect if task crash with fatal exception #73

Open
xorik opened this issue Jul 20, 2017 · 1 comment
Open

Monitoring is not detect if task crash with fatal exception #73

xorik opened this issue Jul 20, 2017 · 1 comment

Comments

@xorik
Copy link

xorik commented Jul 20, 2017

Hi. Thanks for your bundle, it is really useful.

But I found an issue:

If some task is crushed with fatal exception (e.g. out of memory or some function returns incrorrect type in php 7+), in this case last result will not changed and task will stay locked.

E.g. if during scheduler:execute some task is crashed:

[Symfony\Component\Debug\Exception\FatalThrowableError]
  Type error: Return value of SomeService::getUser() must be an instance of
   SomeUser, null returned

In this case the next scheduler:monitor will not show any problem.

@xorik
Copy link
Author

xorik commented Jul 20, 2017

As a workaround I suggest to run cron tasks in separate process, is it hard to implement?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant