Interaction between Message Groups (JMSXGroupID) and Message Selectors freezes JMS Consumers. MAVEN_OPTS='-Xmx256m -Dcom.sun.management.jmxremote' To run: mvn clean test test case will start an embedded broker that will store data within target dir, so mvn clean will delete brokers files to allow for clean runs. You see failure when Camel Throughput logger output stops indicating that JMS Consumers have stoped. Enqueue Count however is still growing within embedded broker. if within src/main/resources/routers.xml you set MessageCreator's numPartitions propery to 1 (only 1 message selector) or numMessageGroups to 0 (no JMSXGroupID header) then the JMS Consumer(s) will continue forever MAVEN_OPTS='-Xmx256m -Dcom.sun.management.jmxremote' To run: mvn clean test test case will start an embedded broker that will store data within target dir, so mvn clean will delete brokers files to allow for clean runs. You see failure when Camel Throughput logger output stops indicating that JMS Consumers have stoped. Enqueue Count however is still growing within embedded broker. if within src/main/resources/routers.xml you set MessageCreator's numPartitions propery to 1 (only 1 message selector) or numMessageGroups to 0 (no JMSXGroupID header) then the JMS Consumer(s) will continue forever