might be worth trying with latest 5.3.1 snapshot - with networks,
there was a problem where subscriptions weren't being cleaned up
properly
On 22 Feb 2010, at 17:56, Eric-AWL wrote:
No. I don't understand.
I'm not sure of the current configuration, but it's strange
2 groups of developers. One network of broker where each component
has a
transport and a network connector with the same multicast group
On components developed by the first group of developers :
2341 ObjectNames (I think it's OK when I count my consumers, queues,
topics,
advisory queues ...)
146 MBeanServerNotifications
On components developed by the second group of developers :
72049 Object Names.
127956 MBeanServerNotification
I think the most of ObjectNames are the subscription MBeans.
Eric-AWL
--
View this message in context:
http://old.nabble.com/Too-much-%22subscription-MBeans%22-%3D%3E-OOM.-tp27685385p27691468.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Rob Davies
http://twitter.com/rajdavies
I work here: http://fusesource.com
My Blog: http://rajdavies.blogspot.com/
I'm writing this: http://www.manning.com/snyder/
