Recently we started to test the Direct Container Factory in one of our microservices, the main motivation to change container factory is we want to reduce the thread number that process messages from queues.
Usually, when this microservice boots using the Simple Container Factory, we see a thread group called "pool-1-thread-#" which is the pool used by Rabbit consumers. Now that we have changed to Direct Container Factory, we see two thread groups called "pool-1-thread-#" and "null-consumerMonitor-#".
We have been playing with application and listeners configuration but we haven't been able to remove this "problem". This is our configuration, could it have a problem?
This is one of our listeners:
Also we are using the RabbitListenerConfigurer to configure a AfterReceivePostProcessor to factory, but we think it shouldn't provoque this behavior.
Could this be a bug? We weren't expecting that two thread groups were created and the "null" in the name either.