John Nabil comments

Results 5 comments of


                                            John Nabil

Laravel Octane with Rabbitmq - broken pipe or closed connection error and CHANNEL_ERROR - expected 'channel.open'(60, 40)

- Laravel version 9 - Octane version 1 - Rabbitmq version 3.11.8 - Package version 13.1 @khepin I had the same issue till now but I managed a solution for...

Laravel Octane with Rabbitmq - broken pipe or closed connection error and CHANNEL_ERROR - expected 'channel.open'(60, 40)

@khepin yes it mainly happens on the publish side but I think it won't happen on the consumers. The consumers has it's own connection when you run `queue:work` or `rabbitmq:consume`...

Laravel Octane with Rabbitmq - broken pipe or closed connection error and CHANNEL_ERROR - expected 'channel.open'(60, 40)

That's great I hope this can be merged soon this is a really way better than creating connections and I will see if I can help to improve this merge...

Laravel Octane with Rabbitmq - broken pipe or closed connection error and CHANNEL_ERROR - expected 'channel.open'(60, 40)

@adm-bome I think theoretically this is possible but we should look into after the timeout cause when it times out or the connection was closed by any cause it can...

Laravel Octane with Rabbitmq - broken pipe or closed connection error and CHANNEL_ERROR - expected 'channel.open'(60, 40)

@adm-bome we should add rabbitmq connection in `octane.php` config file to the warm array to resolve it only one time when the app starts for the first time. ```php 'warm'...