lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emanuele Lombardi (JIRA)" <>
Subject [jira] [Updated] (SOLR-3616) Solr TestJmxIntegration#testJmxOnCoreReload bug related to TestHarness
Date Wed, 11 Jul 2012 10:23:34 GMT


Emanuele Lombardi updated SOLR-3616:

    Attachment: TestHarnessPatch.txt
> Solr TestJmxIntegration#testJmxOnCoreReload bug related to TestHarness
> ----------------------------------------------------------------------
>                 Key: SOLR-3616
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: multicore
>            Reporter: Emanuele Lombardi
>              Labels: CoreReload, JMX
>             Fix For: 3.4, 3.5, 3.6
>         Attachments: TestHarnessPatch.txt
> Using zabbix to monitor my Solr instance I noticed that after core reloading the Mbeans
have disappeared. There is a test -> testJmxIntegration#testJmxOnCoreReload used to check
Mbeans presence after core reload. The test is wrong because TestHarness sets core name to
null on creating the core for the first time (CoreContainer#initialize) so his Mbeans have
jmxRootName="solr" (JmxMonitoredMap#line61). Once the core is created it sets coreName = ""
causing new Mbeans to have jmxRootName="solr/"
> So after first core closing only MBeans having name "solr" are removed and   only MBeans
with name "solr/" persists on JMXServer. This test is fake.
> Step to reproduce test fail
> 1) Apply TestHarness patch
> 2) Run the tests

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message