5 a.m.
[
https://issues.jboss.org/browse/ISPN-1181?page=com.atlassian.jira.plugin....
]
Pete Muir commented on ISPN-1181:
---------------------------------
I can't close the issue (JIRA problem?) but I can confirm the test passes for me in
5.0.x branch
NPE when starting JMX registration after configuration validation
failed
------------------------------------------------------------------------
Key: ISPN-1181
URL: https://issues.jboss.org/browse/ISPN-1181
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 5.0.0.CR5
Reporter: Sanne Grinovero
Assignee: Pete Muir
Priority: Critical
Fix For: 5.0.0.FINAL
Time Spent: 1 minute
Remaining Estimate: 0 minutes
This is reproducible running the lucene-directory-demo, I'm sending a pull request
for the demo to fix the test (which was not running):
https://github.com/infinispan/infinispan/pull/388
After that pull is included, you'll see the test failing and highlighting a critical
issue:
{code}2011-06-14 10:48:25,990 WARN [TimeoutConfigurationValidatingVisitor] (main)
ISPN00148: Invalid <transport>: distributedSyncTimout value of 240000. It can not be
higher than <stateRetrieval>:timeout which is 10000
FAILED CONFIGURATION: @BeforeTest init
java.lang.NullPointerException
at
org.infinispan.config.GlobalConfiguration$GlobalJmxStatisticsType.getMBeanServerLookupInstance(GlobalConfiguration.java:1645)
at
org.infinispan.config.GlobalConfiguration.getMBeanServerLookupInstance(GlobalConfiguration.java:245)
at org.infinispan.jmx.JmxUtil.lookupMBeanServer(JmxUtil.java:55)
at
org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:50)
at
org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:62)
at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:572)
at
org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:269)
at
org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:238)
at
org.infinispan.lucenedemo.CacheConfigurationTest.init(CacheConfigurationTest.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:76)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
at org.testng.TestRunner.beforeRun(TestRunner.java:624)
at org.testng.TestRunner.run(TestRunner.java:592)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:329)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:324)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:286)
at org.testng.SuiteRunner.run(SuiteRunner.java:235)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1049)
at org.testng.TestNG.runSuitesLocally(TestNG.java:974)
at org.testng.TestNG.run(TestNG.java:905)
at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111)
at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:203)
at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:174){code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira