there are two ways to fix this bug:
1) merge RabbitMQ 3.x packages into 4.1 repository and corresponding updated init script 2) revert this patch, that uses rabbitmq 3.x
I think, preferrable is #1, but we need to make sure that corresponding astute patch will also be merged into stable/4.1 branch
there are two ways to fix this bug:
1) merge RabbitMQ 3.x packages into 4.1 repository and corresponding updated init script
2) revert this patch, that uses rabbitmq 3.x
I think, preferrable is #1, but we need to make sure that corresponding astute patch will also be merged into stable/4.1 branch