[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: FailoverTests consuming a lot of memory...
clebert.suconic@jboss.com
do-not-reply at jboss.com
Thu Dec 18 15:29:52 EST 2008
It's actually quite funny...
MultiThreadFailvoerTest was taking about 7 minutes to run before disabling JMX on the test, and 3 minutes after the change.
(I ran all these without my changes for largeMessage & clustering)
I have seen this MessageReferences following this path:
MessagingReferenceImpl <- ConcurrentHashMaps <- QueueImpl <- MessageCounter <- ManagementImpl <- Somewhere_I_couldn't find (Probably JMX on the JVM)
(This is a summarized graph of course.... the real profiler shows many more objects in between)
I was only seeing MessageReferenceImpl growing on those tests, like the old JMXManagement Object was not being released. Maybe it would worth taking a look if management is not leaving objects after a server is stopped.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197452#4197452
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197452
More information about the jboss-dev-forums
mailing list