Github user alopresto commented on the issue:
I ran this with an ActiveMQ instance in Docker and a [simple
published JMS messages to a queue and then consumed them. It ran very well at
first, and I saw 10 threads on the ConsumeJMS once I configured it that way.
But after starting and stopping a few times, the ActiveMQ admin panel showed 30
consumers (3 times start/stopping 10 consumers) and no messages were being
consumed anymore. I have attached the bootstrap log which should have the
thread dump contents.