[FIX] GroupRegistrationHandler's scheduler should be final
And be initialized in the constructor.
Given the RabbitMQEventBus beans are limited and the group use case is soon or late being used, we do not need lazy initialization for the scheduler IMO.
Otherwise, James could restart the `GroupRegistrationHandler` while it is not started yet (e.g. a RabbitMQ node is down before any group listener is registered) which leads to `java.lang.NullPointerException: scheduler` and fail the `RabbitEventBusConsumerHealthCheck`.
1 file changed
