I agree that a single connection per consumer is a good starting point. Be
mindful of overall connection counts on the server though, and be sure to
use the NIO connector if those counts will be high on the broker (in the
thousands rather than hundreds). Make sure to count connections from all
cl
I don’t recommend using pools for consumers, until you have a specific scenario
that a single connection per consumer doesn’t fit your needs. Pre-tuning
usually results in de-tuning when it comes to messaging.
Start with a single connection and single consumer and measure performance
there. Mo
My recommendation is to start simple and add complexity as-needed.
What does a pooled connection add to the solution? If nothing, remove it.
In general, pooled connections are useful for two key concerns:
- Processing flows which do not keep connections for long periods (e.g. open
connection /
FYI: This is how my configuration looks like:
${mybroker.url}
and my listener is using it as:
