Yes, that code part is uncommented in my config and I prefer this secured
version of course, but I think it was uncommented by defalut. (I used the
installer version of 4.0.5 with 'ejb3-clustered' settings)
Anyway, thanks for the help!
View the original post :
Thank you! This one works correctly! In the meantime I tried out the folloowing
for the singleton-jmx-adaptor-service.xml:
| mbean code=org.jboss.invocation.jrmp.server.JRMPProxyFactory
name=jboss.jmx:type=adaptor,name=SingletonInvoker,protocol=jrmp,service=proxyFactory
| depends
Yes, that declaration does not include your mbean in a security domain. Have a
look at your deploy/jmx-invoker-service.xml file,
jboss.jmx:type=adaptor,name=Invoker mbean, section about the invoke operation.
You must have this uncommented:
descriptors
|interceptors
| interceptor
Looks like the jboss.jmx:type=adaptor,name=Invoker service is secured, using
the same security domain as the JMX console. So, you need to associate a
principal and credential that the jmx-console domain will accept with the
caller thread before invoking on the adaptor.
This can be done as
