Hi Kirk, Yes, Cache is created on that JVM by that time and all necessary Regions are created without problem. Here the problem seem to be due to MBeanJMXAdapter.localGemFireMBean staying empty… because as I noted in my previous mail in this thread to Jinmei, even if I remove the startManager call and try to start locator with “jmx-manager-start=true”, any call like managementService.getDistributedSystemMXBean() returns null due to this map being empty even after cache and regions creation…
Thanks, Vahram. From: Kirk Lund [mailto:[email protected]] Sent: Wednesday, February 22, 2017 10:12 PM To: [email protected] Subject: Re: NullPointerException during SystemManagementService.startManager I'm not aware of any changes in this area between GF 8.2 and Geode 1.1. How are you invoking ManagementService.startManager()? Does the JVM in which you're invoking this already have a Cache or is the Cache still being created when you invoke startManager? On Wed, Feb 22, 2017 at 9:51 AM, Vahram Aharonyan <[email protected]<mailto:[email protected]>> wrote: Hi Anthony, Currently I’m using Geode 1.1.0 released last week, but actually saw this problem previously with geode-1.0.0-incubating.M3 as well. BTW, I have not hit this issue with gemfire 8.2.0.6 used before that. Thanks, Vahram. From: Anthony Baker [mailto:[email protected]<mailto:[email protected]>] Sent: Wednesday, February 22, 2017 8:41 AM To: [email protected]<mailto:[email protected]> Subject: Re: NullPointerException during SystemManagementService.startManager What version of Geode are you using? On Feb 22, 2017, at 12:09 AM, Vahram Aharonyan <[email protected]<mailto:[email protected]>> wrote: Hi All, We are getting java.lang.NullPointerException while trying to start JMX Manager Node by invoking ManagementService.startManager: org.apache.geode.management.ManagementException: java.lang.NullPointerException at org.apache.geode.management.internal.FederatingManager.startManager(FederatingManager.java:139) at org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:467) Caused by: java.lang.NullPointerException at org.apache.geode.management.internal.MemberMessenger.broadcastManagerInfo(MemberMessenger.java:64) at org.apache.geode.management.internal.FederatingManager.startManager(FederatingManager.java:132) ... 45 more This seems to be due to MBeanJMXAdapter. localGemFireMBean being empty by that point. Please note that before startManager call from Java code gemfire locator was successfully started, cache was created, necessary Regions were created using this configuration: .set("jmx-manager", "true") .set("jmx-manager-start", "false") Could you please let us know whether we miss something in configuration or anything else need to be performed before starting JMX manager Node dynamically? Thanks, Vahram.
