[JBoss JIRA] Created: (ISPN-1314) Support properties instance other than System.getProperties() when resolving configuration placeholders
by Yuri de Wit (JIRA)
Support properties instance other than System.getProperties() when resolving configuration placeholders
--------------------------------------------------------------------------------------------------------
Key: ISPN-1314
URL: https://issues.jboss.org/browse/ISPN-1314
Project: Infinispan
Issue Type: Enhancement
Components: Configuration
Affects Versions: 5.0.0.CR7
Reporter: Yuri de Wit
Assignee: Manik Surtani
The current implementation always uses System.getProperties() when resolving configuration placeholders (See InfinispanConfiguration line 331) and this is a bit limiting when trying to configure Infinispan in a webapplication. In this specific case, I need to construct a Properties object with a combination of System.getProperties() and the servlet context parameters. In other cases maybe the web app don't have access permissions to System.getProperties().
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (ISPN-1304) QueryInterceptor incorrectly handles replace command
by Michal Linhard (JIRA)
QueryInterceptor incorrectly handles replace command
----------------------------------------------------
Key: ISPN-1304
URL: https://issues.jboss.org/browse/ISPN-1304
Project: Infinispan
Issue Type: Bug
Components: Querying
Affects Versions: 5.0.0.CR8
Reporter: Michal Linhard
Assignee: Manik Surtani
org.infinispan.query.backend.QueryInterceptor.visitReplaceCommand() wrongly interprets field ReplaceCommand.oldValue as always present oldValue, but this field serves only for execution of conditional replace.
this leads to failure during replace when using searchable cache.
ReplaceCommand.oldValue is probably not well suited name for the field
test case project attached.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Resolved: (ISPN-1181) NPE when starting JMX registration after configuration validation failed
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/ISPN-1181?page=com.atlassian.jira.plugin.... ]
Pete Muir resolved ISPN-1181.
-----------------------------
Resolution: Done
> 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
>
> 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
12 years, 8 months
[JBoss JIRA] Updated: (ISPN-1181) NPE when starting JMX registration after configuration validation failed
by Vlastimil Eliáš (JIRA)
[ https://issues.jboss.org/browse/ISPN-1181?page=com.atlassian.jira.plugin.... ]
Vlastimil Eliáš updated ISPN-1181:
----------------------------------
Remaining Estimate: (was: 0 minutes)
Git Pull Request: https://github.com/infinispan/infinispan/pull/388 (was: https://github.com/infinispan/infinispan/pull/388)
> 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
>
> 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
12 years, 8 months
[JBoss JIRA] Commented: (ISPN-1181) NPE when starting JMX registration after configuration validation failed
by Pete Muir (JIRA)
[ 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
12 years, 8 months
[JBoss JIRA] Work logged: (ISPN-1181) NPE when starting JMX registration after configuration validation failed
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/ISPN-1181?page=com.atlassian.jira.plugin.... ]
Pete Muir logged work on ISPN-1181:
-----------------------------------
Author: Pete Muir
Created on: 05/Aug/11 5:55 AM
Start Date: 05/Aug/11 5:54 AM
Worklog Time Spent: 1 minute
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes
Time Spent: 1 minute
Worklog Id: (was: 12425096)
> 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
12 years, 8 months
[JBoss JIRA] Updated: (ISPN-1181) NPE when starting JMX registration after configuration validation failed
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/ISPN-1181?page=com.atlassian.jira.plugin.... ]
Pete Muir updated ISPN-1181:
----------------------------
Issue Type: Bug (was: Feature Request)
Git Pull Request: https://github.com/infinispan/infinispan/pull/388
> 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
>
>
> 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
12 years, 8 months
[JBoss JIRA] Updated: (ISPN-1181) NPE when starting JMX registration after configuration validation failed
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/ISPN-1181?page=com.atlassian.jira.plugin.... ]
Pete Muir updated ISPN-1181:
----------------------------
Issue Type: Feature Request (was: Bug)
> NPE when starting JMX registration after configuration validation failed
> ------------------------------------------------------------------------
>
> Key: ISPN-1181
> URL: https://issues.jboss.org/browse/ISPN-1181
> Project: Infinispan
> Issue Type: Feature Request
> 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
>
>
> 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
12 years, 8 months
[JBoss JIRA] Updated: (ISPN-1181) NPE when starting JMX registration after configuration validation failed
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/ISPN-1181?page=com.atlassian.jira.plugin.... ]
Pete Muir updated ISPN-1181:
----------------------------
Fix Version/s: 5.0.0.FINAL
(was: 5.0.0.CR6)
> 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
>
>
> 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
12 years, 8 months
[JBoss JIRA] Commented: (ISPN-1181) NPE when starting JMX registration after configuration validation failed
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-1181?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on ISPN-1181:
---------------------------------------
Hi Pete, this seems open but marked for version 5.0.0.CR6.. was it solved?
> 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.CR6
>
>
> 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
12 years, 8 months