[nanocontainer-scm] [jira] Resolved: (NANO-129) Prevent re-registering mbeans

"Joerg Schaible (JIRA)" <jira-yCVjj/[email protected]> Tue, 15 Mar 2005 09:51:31 -0500 (EST)
Newsgroups gmane.comp.java.nanocontainer.cvs
Message-ID <[email protected]>
     [ http://jira.codehaus.org/browse/NANO-129?page=3Dhistory ]
    =20
Joerg Schaible resolved NANO-129:
---------------------------------

    Resolution: Won't Fix
     Assign To: Joerg Schaible

Hi Greg, as already explained on the list I will not apply this (although I=
 really appreciate your work and our discussion). Main reason is, that your=
 patch will hide an unwanted double registration, since an existing MBean w=
ill silently dropped. I expect this to be much harder to track down as perf=
orming proper unregister operations.

> Prevent re-registering mbeans
> -----------------------------
>
>          Key: NANO-129
>          URL: http://jira.codehaus.org/browse/NANO-129
>      Project: NanoContainer
>         Type: Improvement
>   Components: jmx
>     Versions: 1.0-beta-5
>     Reporter: Gr=E9gory Joseph
>     Assignee: Joerg Schaible
>  Attachments: jmx-prevent-double-registration.patch
>
>
> Currently, the JMXVisitor will register mbeans no matter if they are alre=
ady registered in the MBeanServer or not.
> Here's a patch that first unregisters the ObjectName if it's already regi=
stered, and then registers it. (This, as opposed to ignoring the registrati=
on only if not yet registered, probably avoids stale instances of the mbean=
 to lie in the vm)

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira