lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrik Nordebo (JIRA)" <>
Subject [jira] Commented: (SOLR-1841) Unregistering of Searcher MBean doesn't work in Websphere
Date Tue, 11 May 2010 09:21:41 GMT


Patrik Nordebo commented on SOLR-1841:

I assumed in the patch that the derived object name returned for an original object name is
always the same.  If that isn't the case, then the map will have to be synchronized to be
safe, unless we can be sure that no two threads will ever register/unregister the same name
at the same time. I believe the latter was the case when I wrote the patch, but I could be
misremembering.  In Websphere we also always get the same name (as long as we're running in
the same VM), so there at least the implementation should be safe.

> Unregistering of Searcher MBean doesn't work in Websphere
> ---------------------------------------------------------
>                 Key: SOLR-1841
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>         Environment: Websphere Application Server 6.1
>            Reporter: Patrik Nordebo
>            Priority: Minor
>         Attachments: patch, SOLR-1841.patch
> On a Websphere cluster, all MBeans registered in the default MBean server get renamed
on registration (it adds properties based on which node and cell in the Websphere cluster
the process was running).  This means that when Solr tries to unregister an MBean (e.g. an
old searcher), the old MBean is never removed.  In the case of a rebind the binding of the
new MBean fails because it tries to register a name that is already taken.
> To get around this the name the mbean gets assigned must be stored somewhere where it
can be looked up when we need to remove the binding.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message