In Laravel 6’s queue processor, the processing that does not take effect after the code changes
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.
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
Figure 2
Modules\\ThemeStoreDB\\Jobs\\ThemeInstallationJob has been attempted too many times or run too long. The job may have previously timed out.
