We are still having memory usage issues, but I no longer think it has anything to do with the camel activemq component bean.
The 2 queues in question are using Atomikos and org.apache.activemq.ActiveMQXAConnectionFactory. The other dozen queues are consistently at zero cursor memory usage. The two transactional queues eat cursor memory and never return it. E White wrote: > > We are also having some issues with memory consumption increasing and > never decreasing that seem to be linked to using the camel activemq > component bean. > Is there any way of changing the default port camel uses to connect to > activemq without using this bean? > > -- View this message in context: http://old.nabble.com/Multiple-isolated-brokers-tp27720815p27723755.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
