Re: [Dev] [API-M 1.10.0] NPE in Key Manager Startup

2016-05-04 Thread Imesh Gunaratne
Vishanth figured out the root cause of this problem, a great finding Vishanth!! As we understood the above error has been raised because of the health check triggered as soon after starting the server. To be more specific the transports have been opened before initializing internal components. We

Re: [Dev] [API-M 1.10.0] NPE in Key Manager Startup

2016-05-04 Thread Vishanth Balasubramaniam
Hi, I am getting the same error when I try to deploy GREG store publisher setup, from the store node. Seems like the error is thrown from some UI component. Regards, Vishanth On Tue, May 3, 2016 at 6:13 PM, Imesh Gunaratne wrote: > Hi Devs, > > I'm seeing the below NPE in Key Manager startup i

[Dev] [API-M 1.10.0] NPE in Key Manager Startup

2016-05-03 Thread Imesh Gunaratne
Hi Devs, I'm seeing the below NPE in Key Manager startup in a API-M fully distributed setup, any thoughts on this? [2016-05-03 12:16:52,950] INFO - RegistryEventingServiceComponent Successfully Initialized Eventing on Registry [2016-05-03 12:16:53,070] INFO - JMXServerManager JMX Service URL :