Open edwardotis opened 7 years ago
That "issue" has been around forever now. The reason is that the redis connections are already closed before the workers are actually stopped. i will check whether we can hook into the shutdown process earlier to stop workers but this will keep happening if there is a long running job running, while the app is being stopped. There is simply no way of gracefully killing that thread while it is still working on something.
Thanks, @peh. FYI, my queue was empty so the workers were not actively performing tasks.
yeah that happens from time to time when timing is bad. but it's also nothing bad at all and can happen to other connections that are not handled in the "main thread"
gotcha, ok, so sounds like a low priority issue.
this has been fixed by #28
Using v1.2.1, when I restart my app deployed to Tomcat, the logs spew the following redis errors for each workerimpl
And other error for each worker:
Using: grails jesque v1.2.1 grails 3.1.16 tomcat 8.0.41 Linux