Closed rulrok closed 9 years ago
First of all, thanks for a very thorough description. I think that the problem is that you are trying to push the job to images_queue
queue using the default connection(GAE). In order to use a different connection('images_queue') I would suggest to try the following code:
Queue::connection('images_queue')->pushOn('images_queue', $command);
Please notice that both the connection and the queue are sharing the same name(according to the configuration file). I would suggest changing the connection name to something like images_connection
. Please let me know if this helps.
That was it!
This is what was making me confused too. The gae
connection has the same name as the driver. So I though that by saying which queue you wanted, you were actually saying which connection to use. Moreover, I was already in a scavenger hunt into Laravel documentation and they've never told about that Queue::connection
method. Now I have changed the names as you suggested.
Gosh. This is so frustrating! :disappointed:
Thank you a lot. You saved me here.
Hello,
I'm trying to setup a Laravel 5.0 project on GAE that uses the push queue for all the normal actions which you could do, and one beanstalkd queue that is running in a VM compute engine.
I need to use this beanstalkd queue for only one very specific task that MUST be run on the VM.
So, inside my
Command
class I have this method to push it to my desired queue.In my controller, I just dispatch the process like that
The problem is that the exception that I'm getting suggests that this process was tried to be queued into GAE queue instead of beanstalkd. Below, the stack trace (most recent at the top). The lines 05~07 make me believe that Gae queue is getting in the way somehow.
My .env file looks like this (for debugging)
My queue config file looks like this
I'm getting out of hope at this point. Could someone give me a hand here?