Details
-
Task
-
Resolution: Obsolete
-
Minor
-
JBossAS-4.0.1 SP1, JBossAS-4.0.2 Final
-
None
Description
Some customers find useful to access JMXInvokerServlet via a JNDI lookup
---------------------------------------------------------------------------
NOTE: for security reason, I would recommend keeping this mbean commented out
---------------------------------------------------------------------------
/deploy/jmx-invoker-service.xml
<!-- Expose the jmx invoker service interface via HTTP <mbean code="org.jboss.invocation.http.server.HttpProxyFactory"
name="jboss.jmx:type=adaptor,name=Invoker,protocol=http,service=proxyFactory">
<attribute name="InvokerURL">http://localhost:8080/invoker/JMXInvokerServlet</attribute>
<!-- The target MBean is the InvokerAdaptorService configured below -->
<depends optional-attribute-name="InvokerName">jboss.jmx:type=adaptor,name=Invoker</depends>
<attribute name="ExportedInterface">org.jboss.jmx.adaptor.rmi.RMIAdaptorExt</attribute>
<attribute name="JndiName">jmx/invoker/HttpAdaptor</attribute>
<attribute name="ClientInterceptors">
<interceptors>
<interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
<interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
<interceptor>org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor</interceptor>
<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
</interceptors>
</attribute>
</mbean>
-->