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:aba...@pivotal.io] Sent: Wednesday, February 22, 2017 8:41 AM To: user@geode.apache.org Subject: Re: NullPointerException during SystemManagementService.startManager What version of Geode are you using? On Feb 22, 2017, at 12:09 AM, Vahram Aharonyan <vaharon...@vmware.com<mailto:vaharon...@vmware.com>> 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.
