Yes in 3.2
It hasn't been backported correctly to 3.0
so it doesn't work.

Use the following steps:
server/default/deploy/jmx-invoker-adaptor-service.xml/META-INF/jboss-service.xml
add the following mbean config



<!-- Where to bind the proxy -->
jmx/invoker/HttpAdaptor

<!-- The interface to expose at the proxy -->
javax.management.MBeanServer

<!-- The JMX Object Name of the invoker that performs the transport -->
<depends optional-attribute-name="InvokerName">jboss:service=invoker,type=http


This binds an http adaptor at jmx/invoker/HttpAdaptor

Use the following jndi.properties
java.naming.factory.initial=org.jboss.naming.HttpNamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=http://localhost:8080/invoker/JNDIFactory

And the following code

InitialContext ctx = new InitialContext();
MBeanServer server = (MBeanServer) ctx.lookup("jmx/invoker/HttpAdaptor");

Warning, there is no security for this
adaptor. If you want security, you can
bind the ejb adaptor to http

I'm off to fix 3.0
Regards,
Adrian

You can go through the http adaptor by creating the appropriate HTTP requests. A more sophisticated solution in the form of a SOAP connector will be included in 4.0.

For an example, see the Shutdown.java implementation in JBoss 3.0.7