我正在使用Apache Camel JMS组件来处理大量的JMS消息。处理一条消息不需要很多计算，但是处理量很高。性能和可靠性是此应用速度的主要要求，必须支持XA事务。
由于顺序并不重要，因此我可以增加并发使用者的数量，以便可以尽快使用这些消息。
但是，通过查看日志条目，我可以发现JMS端点似乎每秒都会发送一条新消息。
26-07-2018 06:38:00.000 Camel (camel-1) thread #21 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #21 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #15 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #14 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #21 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #21 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #15 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #15 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #21 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #21 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #15 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #15 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #14 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #14 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #14 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #14 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #14 - JmsConsumer
26-07-2018 06:38:00.000 Camel (camel-1) thread #11 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #11 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #11 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #11 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #11 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #11 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #20 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #10 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #10 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #18 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #20 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #20 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #20 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #20 - JmsConsumer
26-07-2018 06:38:01.001 Camel (camel-1) thread #20 - JmsConsumer
26-07-2018 06:38:02.002 Camel (camel-1) thread #17 - JmsConsumer
26-07-2018 06:38:02.002 Camel (camel-1) thread #17 - JmsConsumer
26-07-2018 06:38:02.002 Camel (camel-1) thread #18 - JmsConsumer
26-07-2018 06:38:02.002 Camel (camel-1) thread #18 - JmsConsumer
26-07-2018 06:38:02.002 Camel (camel-1) thread #18 - JmsConsumer
26-07-2018 06:38:02.002 Camel (camel-1) thread #18 - JmsConsumer
26-07-2018 06:38:02.002 Camel (camel-1) thread #18 - JmsConsumer
26-07-2018 06:38:02.002 Camel (camel-1) thread #16 - JmsConsumer
26-07-2018 06:38:02.002 Camel (camel-1) thread #16 - JmsConsumer
26-07-2018 06:38:02.002 Camel (camel-1) thread #16 - JmsConsumer
26-07-2018 06:38:02.002 Camel (camel-1) thread #16 - JmsConsumer
但是，当您必须一秒钟处理数百万条消息时，绝对是很长的时间。只是想知道是否有任何方法可以配置该轮询间隔，或者我应该考虑更改设计以使用轮询使用者。
欢迎提出任何有关如何使此处理更快的想法。
预先感谢您的输入。