You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been using DTC Queue for virtually every one of our projects that requires a queue manager. Everything works great except for this one worker that we have setup. It builds a PDF using mPDF and is suppose to email out. The problem is this occurs A LOT and it never fires off the worker. So we don't believe there is any issue with the worker code itself (because it is just like our other workers and they work just fine).
So we have setup the worker to fire off with a max-count of 1 thinking that it might be a threading issues caused by two workers running at the same time. The issue is the above error captured in the archive table means it never even got to our worker code to fire off.
So what is causing this? We are on Symfony 5? Like I said all of our other workers are firing off with no problems except for this specific one. We even attempted renaming it - but still similar issues.
Any thoughts on what the cause is?
The text was updated successfully, but these errors were encountered:
We have been using DTC Queue for virtually every one of our projects that requires a queue manager. Everything works great except for this one worker that we have setup. It builds a PDF using mPDF and is suppose to email out. The problem is this occurs A LOT and it never fires off the worker. So we don't believe there is any issue with the worker code itself (because it is just like our other workers and they work just fine).
So we have setup the worker to fire off with a max-count of 1 thinking that it might be a threading issues caused by two workers running at the same time. The issue is the above error captured in the archive table means it never even got to our worker code to fire off.
So what is causing this? We are on Symfony 5? Like I said all of our other workers are firing off with no problems except for this specific one. We even attempted renaming it - but still similar issues.
Any thoughts on what the cause is?
The text was updated successfully, but these errors were encountered: