[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-1025?pa...
]
Jakub Białek commented on HSEARCH-1025:
---------------------------------------
In this case problem can be resolved by adding to ImmutableSearchFactory.close() method
invocation of
JMXRegistrar.unRegisterMBean(StatisticsInfoMBean.STATISTICS_MBEAN_OBJECT_NAME);
I'll try to prepare patch.
This issue is associated with HSEARCH-1026, so if I create patch for HSEARCH-1026 it will
be incompatible with patch for this issue (both patches may touch the same part of the
code). How should I do it? Create one patch for both issues? Create patch for one issue
wait until it'll be accepted and added to 'trunk' then create patch for second
issue?
StatisticsInfoMBean is never unregistered
-----------------------------------------
Key: HSEARCH-1025
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-1025
Project: Hibernate Search
Issue Type: Bug
Affects Versions: 3.4.1.Final
Environment: Hibernate 3.6.9.Final
Reporter: Jakub Białek
When application with property hibernate.search.jmx_enabled set to true is undeployed the
StatisticsInfoMBean isn't removed from JMX.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira