Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have defined a camel jetty-activemq route as below:
from(“jetty:http://0.0.0.0:8087/url1”).to(“activemq:queue:queue1)
Does camel create an activemq connection and then use that connection for all messages received by jetty or create an activemq connection per message.
I am planning to use a pooled connection for activemq, since my message inflow is pretty high per second, i need to understand camel behaviour to define the max connection pool size.
The ActiveMQ component, as well as the JMS component, is based on JMSTemplate from Spring Framework, when sending messages.
As you fear, it creates and closes a connection+session+producer per message, which is not optimal performence wise.
As recommended in the activemq component documentation, you should set it up with pooling. Then you will reuse the connection/session/producer.
You could actually live with just one connection in the pool for that pool if you intend to use it for this route only.
ActiveMQ has made a summary of tips and tricks with JMSTemplate. It’s worth reading.
Update: Regarding the number of Connections related to concurrency:
Simplified, a Connection is a network connection (“socket”) with the broker, that is shared among many threads. Each of your threads would still have it’s own (pooled) session that uses the shared connection and operate concurrently. Multiple connection could still be an enhancement, if you have multiple ActiveMQ brokers and want to loadbalance between them (given ActiveMQ is the bottleneck and not your application).
It might also be that, in practice, performance might go up to some small extent by using a limited set of connections instead of one, but that you probably have to test out for your particular environment.