Thnks for the information I was working on caching but the Camel that is shipped with ActiveMQ does not appear to provide the same functionality and/or use the same settings that a full Camel installation provides; there is also the possibility I am setting something incorrectly as well.
Are there are suggestions on how caching should be set-up/configure for Spring/Camel within an ActiveMQ instance? As for concurrentConsumers I am using this option, I set a minimum and maximum number. I have noticed that there appears to be a threshold hit on the maximum number of consumers; any number above 50 does not make a difference. Jason Jackson Senior Manager Main Office: 703-639-0709 Direct: 202-888-3973 Cellular: 863-370-5324 Fax: 571-431-7618 http://www.itechag.com/ -----Original Message----- From: Anton Roskvist <ant...@apache.org> Sent: Thursday, March 28, 2024 11:03 AM To: users@activemq.apache.org Subject: Re: ActiveMQ Classic to IBM MQ Bridge Throughput [You don't often get email from ant...@apache.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Jason, There are quite a few variables to consider for this, but from the top of my head I'd suggest you look into increasing the "cache-level" and "concurrentConsumers" properties of camel-jms and possibly provide pooling or caching of your connections using something like Springs "CachingConnectionFactory" or PooledJMS (https://github.com/messaginghub/pooled-jms";). Strong YMMV disclaimer depending on your specific setup and requirements though, make sure to test these things properly.
