7,289 is definitely a leak. I was just pointing out the config had 500,
in case you had something like 489 instances ;-)
Definitely troubleshoot the client side first, much easier to debug.
You might try a single message test to see if you are getting a leak
with every message, or if its jus
I'll try bumping the max connections down, but I'm not sure I understand how
it would cause the leak. This route has been running on my dev box since
last Thursday and as of this morning I have 7,289 instances of the
ActiveMQConnection and TransportConnectionState.
I guess I could remove the XA co
I'm wondering if its a XA problem, or look into adjusting your pool
config. It currently allows a max of 500 connections. For consuming,
4-5 max connections per CPU core is usually a good ratio.
On 2/14/12 10:12 AM, john wrote:
I think I'm only using spring for transactions. Here's the confi
I think I'm only using spring for transactions. Here's the configuration I
have:
--
View this
Are you using the Spring Caching Connection factory? If so, please
disable that. There are a number of reported bugs. Try the non-caching
version, or use the ActiveMQConnectionFactory directly.
On 2/14/12 9:13 AM, john wrote:
I'm running the fuse 4.4.1-fuse-01-13 ESB release which includes
