[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Leaks.. leaks.. leaks...

[clebert.suconic@jboss.com]

I have found a few leaks already on the code. Nothing that stops production...but affects the testsuite because of stop/start the servers.  (stress tests are affect by those)

I have added -XX:+PrintClassHistogram to the testsuite. If you call kill -3 you would see QueueImpl, MessageReference growing a lot, mainly on all the MultiThreadFailoverTests.

One of the leaks I saw was Remoting has a reference to Management that has references to Queues. The management reference is never cleared. (maybe?)

Another I saw was during a run on XALargeMessageMultiThreadFaviloverTest. Somewhere on management has a reference to the resourceManager. Operations are never released of that resourcemanager (maybe more than 1 resourceManager instance here). queues and messages are building up and the test could get OME depending on the memory settings.


I would need more time to investigate those.. but maybe Tim and Jeff would have a better clue since this is your guys areas.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236871#4236871

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236871