Reputation: 431
I have a Laravel-based web application with a database job queue connection that has been functioning properly for the past month. However, recently, a problem has arisen where a specific set of jobs are not being recorded in the jobs table.
Upon further investigation, it was found that when jobs are dispatched to the "teleops_default" queue, the CPU gets stuck on that line and is unable to proceed. However, when a different queue name is used, the job is successfully dispatched and written to the jobs table as expected.
Broken code ( teleops_default queue name )
dispatch(new \App\Jobs\Test('data', 'data'))->onQueue('teleops_default');
Working Code ( Different queue name )
dispatch(new \App\Jobs\Test('data', 'data'))->onQueue('teleops_test');
Upvotes: -4
Views: 38