Hi Matt, the jmx whiteboard is independent of blueprint. The idea behind jmx whiteboard is to make it easy to get an osgi service to also be an mbean. In order to tell the whitebaord that you want your service to be registered as an mbean you need: - a service property named jmx.objectname whose value is the desired objectname or - the service should implement MBeanRegistration
Furthermore the service should either be a standard or dynamic mbean. So you should make your AMQSendMsgService a standard MBean (e.g. by naming the interface AMQSendMsgServiceMBean) and make sure it's registered as a service with an appropriate jmx.objectname service property. The karaf "management" feature should install all the necessary bundles. There's also a jmx blueprint bundle that exposes blueprint contexts as jmx mbeans. This won't help you expose your own service as an mbean, however. hope this helps david jencks You also need the aries On Jan 2, 2012, at 9:08 PM, Matt Madhavan wrote: > Hi Felix, > Happy New Year and thanks for the reply. If you could let me know the set of > bundles I need to deploy would be great. > > All the bundles like Derby, Camel etc, I can see them instrumented and can > see them in JConsole. I know JMX and that's the easy part, but all the > promises of todayland? > > How about user bundles, like the one I deployed, can't be rocket sience!(sic > I almost became one) but simple steps and docs? > > Man I'm getting stumped on one of the basic concept of BluePrint-extender > bundles. JMX is an old tech, let's not make a simple tech complex in > BluePrint. We r software guys who r supposed to provide solutions, its not > abt tech, its about the problem we need to solve > > Any help will be appreciated, and will come back to the open source many > times from me. Rt now, need to figure out simple steps to solve s/w problems. > > On Jan 1, 2012 12:01 PM, "Felix Meschberger" <[email protected]> wrote: > Hi > IIRC the JMX whiteboard is a separate bundle > Regards > Felix > > Matt Madhavan <[email protected]> wrote: > > Hello, > I'm trying to instrument one of my Blueprint bean as follows: > > package com.hcsc.ccsp.dupcheck.jms.tester; > > public interface SendMsgServiceMBean { > public void sendMsg(); > } > > public class AMQSendMsgService implements SendMsgServiceMBean{ > ..... > } > > <bean id="amqSendMsgServiceBean" > > class="com.hcsc.ccsp.dupcheck.jms.tester.internal.AMQSendMsgService" > init-method="init" destroy-method="destroy"> > <property name = "connectionFactory" ref="connectionFactory"/> > </bean> > <service id = "amqSendMsgService" > ref="amqSendMsgServiceBean" > interface="com.hcsc.ccsp.dupcheck.jms.tester.SendMsgServiceMBean"> > <service-properties> > <entry key="jmx.objectname" value="domain:name=sendMessage" /> > </service-properties> > </service> > > I have deployed this in Karaf (Felix). I see that Karaf has Aries JMX and JMX > Blueprint bundes. > > In JConsole I not see my instrumented bean. > > Any ideas please? Am I missing some bundles? > > Thanks in advance! > > Matt
