没有不值得去解决的问题,也没有不值得去学习的技术!

In Laravel 6’s queue processor, the processing that does not take effect after the code changes

你可以平滑地重启所有队列处理器通过使用 queue:restart 方法:php artisan queue:restart。

1. Since in Windows 10, the setting of the maximum number of seconds (timeout time) that the task can perform does not take effect. Therefore, it is decided to test this feature in the online Linux server.

2. Add: sleep(1200); to the handle() method of the job; because $timeout = 600; , it is expected that it will fail due to the execution timeout.

3. However, after adding it in the Linux server, it does not take effect.

4. The queue processor is a resident process and holds the started application state in memory. So they don’t notice changes to your code after startup. So, during your redeployment process, remember to restart your queue processor.

5. You can smoothly restart all queue processors by using the queue:restart method: php artisan queue:restart. as shown in Figure 1

/var/www/object # php artisan queue:restart
Broadcasting queue restart signal.

你可以平滑地重启所有队列处理器通过使用 queue:restart 方法:php artisan queue:restart。
Figure 1

6. Execute the queue task again. After the time exceeds 10 minutes, it will automatically fail, which is in line with expectations. as shown in Figure 2

再次执行队列任务,当时间超过 10 分钟后,自动失败,符合预期
Figure 2
Modules\\ThemeStoreDB\\Jobs\\ThemeInstallationJob has been attempted too many times or run too long. The job may have previously timed out.

关于作者 · 持续学习与技术实践

我是一名拥有 15 年以上开发经验的技术从业者,自 2013 年起持续运营个人技术博客,记录工作与个人项目中遇到的真实问题,以及解决问题过程中的探索、实践和思考。

除了技术写作,我也在持续开发和维护自己的独立项目,探索新技术和新工具在实际场景中的应用。我始终相信,没有不值得去解决的问题,也没有不值得去学习的技术。

如果这篇文章对你有所帮助,欢迎浏览博客中的其他文章,也欢迎交流技术经验与想法。

关于我  ·  GitHub  ·  邮件联系