[jboss-dev-forums] [Deployers on JBoss (Deployers/JBoss)] - Re: JBAS-4593 -- Leaking classloader via JMX Notifications

[scott.stark@jboss.org]

There are no expected listeners, its just part of the jmx management
interface to emit notifications when class loaders are added/removed
from a repo. I do see that there is a
org.jboss.aop.deployment.LoaderRepositoryUrlUtil class referencing the
CLASSLOADER_ADDED/CLASSLOADER_REMOVED event types to track some internal
sequence number, but that is the only explicit usage in the 4.2 codebase
I can find. In the past there were thoughts about using these notifications to handle implicit deployment dependencies based on usage of a class from the repository, but this was never fleshed out.

I don't see a problem with wrapping the class loader in a WeakReference
to avoid the jmx layer being a strong referent. NotificationListeners
would have to be aware that the Notification user data has changed to a
WeakReference. This could be added as an optional behavior based on a
system property. Notification emission could also be disabled altogether as well based on this property.


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

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