On Dec 2, 2010, at 1150AM, Rupert Smith wrote: > Hi, > > I have successfully registered a JMX RMI Connector with in a registry in an > app process, looked it up by service type, and queried it for available > MBeans in a management process. I have many app instances starting/stopping, > and a single management instance that needs to know when the applications > come up or down, and to obtain access to their MBeans when they do. > > To get started, I have run an example lookup on the management process. Now > instead of a pull interface (client driven poll), I want, if possible a > registry driven push interface, registry will tell the management process as > service become available/unavailable.
My guess is that from the stacktrace thats what seems to be attempted. Since reggie does not have the com.rapidaddition.fix.management.jini.MBeanJiniListener in it's classpath, it needs to load it from somewhere. Reggie is looking to load that class based on the codebase for your service. Are you setting the codebase to your service when you start it? Can we see the command line when you start your service? I assume the com.rapidaddition.fix.management.jini.MBeanJiniListener class is in genzero-api-1.2-beta2-SNAPSHOT.jar right?
