JMX annotations and parsing question

[deruelle_jean]

Hi guys,

I'm trying to expose some properties of the Sip Stack used by Mobicents on top of JBoss AS 5.1.0.GA. Unfortunately the Stack is not a bean and not injected or anything, so I just added the following annotation to my implementation class

@JMX(name="org.mobicents.jain.sip:type=sip-stack,name=mobicents-jain-sip",exposedInterface=SipStackImplMBean.class, registerDirectly=true)

public class SipStackImpl extends ClusteredSipStackImpl implements SipStackImplMBean {

...

}

The jar which contains this is located in server/<profile>/deploy/jboss-web.sar

Upon startup I couldn't see my MBean registered in the jmx-console

Should it be recognized automatically and registered with the AS MBean Server or shall I need to tweak something else ?

Thanks in advance

BR

Jean Deruelle

[alesj]

There is no auto-magic discovery.

You will need to somehow tweak this to end-up in MC/MBeanServer.

If you post more info I can give you more exact suggestion.

[deruelle_jean]

Thanks for the answer.

so the sip stack is started as a Tomcat connector.

In server.xml of jboss web, you basically have this under the Service tag

<!-- Define a SIP Connector -->

<Connector port="5080" ipAddress = "${jboss.bind.address}" protocol="org.mobicents.servlet.sip.startup.SipProtocolHandler" signalingTransport="udp" sipStackPropertiesFile="conf/mss-sip-stack.properties"/>

Thus when the connectors are started by org.jboss.web.tomcat.service.deployers.TomcatService, the SIP Connector is started.

During the SIP Connector Startup, we use a stack which we need to pass some properties programmatically so this stack is created programmatically See http://code.google.com/p/mobicents/source/browse/trunk/servers/sip-servlets/sip-servlets-impl/src/main/java/org/mobicents/servlet/sip/startup/SipProtocolHandler.java#362 for SIP stack creation.

I was wondering if it was possible to get the MBeanServer through something similar to JBoss AS 4, MBeanProxyExt class ?

Thanks in advance

BR

Jean

[alesj]

I was wondering if it was possible to get the MBeanServer through something similar to JBoss AS 4, MBeanProxyExt class ?

You mean MBeanServerLocator?

There are two things wrong with that static hack:

* JMX might not exist in next version of AS (it will be optional)

* MC equivalent can be scoped, hence you might end up with the wrong instance of Kernel

I hacked together a simple MC-int-servlet lib (which I think I already pointed you once), which deals with this two issues.

The entry point is somewhere in Tomcat/JBossWeb code, where I attach current Kernel instance and DeploymentUnit to ServletContext's attributes.

Dunno if that helps you, but my suggestion would be you do something similar.

In the worst case use ThreadLocalUtil in MC-int-common to help you pass around the right instance.

* http://anonsvn.jboss.org/repos/jbossas/projects/mc-int/trunk/

The current version is 2.2.0.Alpha2, also distributed in our mvn repo.

[deruelle_jean]

I actually need something supported out of the box on EAP 5, so if ThreadLocalUtil is available in EAP 5 I could use that easily otherwise it will have to wait that we intergate with AS6, I guess otherwise I would use MBeanServerLocator. Also in my case, I need the ServiceController not the Kernel right ?

Is the entry point you mention located in deployWebModule method of http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_5_1_0_GA/server/src/main/org/jboss/web/deployers/AbstractWarDeployer.java ?

Thanks

Jean

[alesj]

I actually need something supported out of the box on EAP 5, so if ThreadLocalUtil is available in EAP 5 I could use that easily otherwise it will have to wait that we intergate with AS6, I guess otherwise I would use MBeanServerLocator. Also in my case, I need the ServiceController not the Kernel right ?

Either one.

Is the entry point you mention located in deployWebModule method of http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_5_1_0_GA/server/src/main/org/jboss/web/deployers/AbstractWarDeployer.java ?

This piece creates the mbean which then creates ServletContext, where the Kernel and DeploymentUnit are stashed.