Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338106 - MBeans registered via o.e.j.s.context.ManagedAttributes are not unregistered
Summary: MBeans registered via o.e.j.s.context.ManagedAttributes are not unregistered
Status: RESOLVED FIXED
Alias: None
Product: Jetty
Classification: RT
Component: server (show other bugs)
Version: 7.3.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 7.3.x   Edit
Assignee: Greg Wilkins CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-24 10:50 EST by Simone Bordet CLA
Modified: 2011-09-06 01:14 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simone Bordet CLA 2011-02-24 10:50:35 EST 
MBeans that gets registered using the context param "org.eclipse.jetty.server.context.ManagedAttributes" in web.xml are never unregistered on context stop, causing memory leaks in case of redeployments of the context.
Comment 1 Simone Bordet CLA 2011-02-24 11:57:19 EST 
Note that this is only happening on redeploy.
If the server is stopped, then MBeanContainer is stopped and it will unregister everything, but if a context is redeployed, then some of its mbeans will not be unregistered.
Comment 2 Simone Bordet CLA 2011-03-29 05:07:15 EDT 
Greg, I believe this is fixed, but since you worked on the final fix, can you confirm ?
Comment 3 Greg Wilkins CLA 2011-09-06 01:14:00 EDT 
fixed by using Weak hash maps.