Anyone used redis as queueing and broadcasting driver at same time?

Are you getting any errors? Have you monitored the Redis connection in terminal to see what is being processed by the Redis server using 'redis-cli monitor' in command line.

How many Redis server instances do you have running, you can't just add another redis connection to your database config in Laravel and expect it to listen to a separate port on 6380 unless you have created another Redis instance and configured it to listen to a separate connection.

Yes I've tried with multiple redis instances eg: port 6379 & 6380 but no luck.

I ran 'redis-cli monitor' command and somehow laravel does not use multiple connection as I configured in database.php

Fixed it by instantiating new redis client with different connection. Eg:

$redis = Redis::connection('pubsub');

But it will be better if we could select the connection while broadcasting the event.

I don't think that is possible looking at similar answers:

http://stackoverflow.com/questions/18438974/how-to-change-the-connection-info-for-laravel-4-when-using-the-redis-driver

http://fideloper.com/laravel-multiple-database-connections

Actually I did the Redis things manually rather than depending on the event broadcasting. Like:

// Redis Publish
$redis = Redis::connection('pubsub');
$data = [
    'event' => 'App\\Events\\UserRegisteredEvent',
    'data' => [
        'name' => $user->name,
    ],
];
$redis->publish('user-register-channel', json_encode($data));

For now I need thing is done :)

I will find a better solution.

Please let me know if you get something.

Thanks

Hey @Sohelamin, I am having a similar issue. I'm using redis as my broadcast driver, and watching for published events through socket.io. Everything is working fine in a local vm, however, when run on an EC2 production server, the publish event does not get fired when using ShouldBroadcast.

If I use the manual redis instantiation and publish snippet you did above, redis catches the publish event as it should, on both my local vm and production environments.

Any clues as to why Laravel cannot properly publish on an EC2 server setup almost identically to my local vm?

Thanks!

worked for me with artisan queue:listen

The better solution is to set default driver which is not redis in services/queue.phpthen set another connection you wish to use using->onConnection('redis');