[
https://issues.apache.org/jira/browse/SOLR-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455804#comment-13455804
]
wing-tung Leung commented on SOLR-1841:
---------------------------------------
There is also another possible implementation fix: when we could provide a
custom MBean naming strategy, we can avoid that the name is altered by the
MBean server. This at least works for Websphere AS 6.1, if you provide some
extra information like cell, domain and node name attributes.
But it would require some extra configuration attribute for the "jmx" tag, to
provide your own implementation.
Any change that such patch would be accepted for the 3.6.x branch?
E.g. <jmx namingStrategy="com.mycompany.util.jmx.WebSphereNamingStrategy" />
> Unregistering of Searcher MBean doesn't work in Websphere
> ---------------------------------------------------------
>
> Key: SOLR-1841
> URL: https://issues.apache.org/jira/browse/SOLR-1841
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
