[jbossws-issues] [JBoss JIRA] Updated: (JBWS-1912) DispatcherDelegate - Bypass RMIAdaptor when used locally

[Thomas Diesler (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBWS-1912?page=all ]

Thomas Diesler updated JBWS-1912:
---------------------------------

    Fix Version/s: jbossws-native-2.0.4

> DispatcherDelegate - Bypass RMIAdaptor when used locally
> --------------------------------------------------------
>
>                 Key: JBWS-1912
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1912
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: ws-eventing
>    Affects Versions: jbossws-2.0.1.SP2
>            Reporter: Magesh Kumar B
>             Fix For: jbossws-native-2.0.4
>
>
> When we dispatch an event from within the same JVM (through an ejb, jms component), an RMIAdaptor lookup is performed and then the SubscriptionManagerMBean is called to dispatch and this leads to the following error message if the jmx-console is secured:
> Exception in IncidentNotificationBean.wseNotify() : java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
> 	at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169)
> 	at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118)
> 	at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:209)
> 	at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:195)
> 	at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
> 	at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
> 	at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
> 	at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
> 	at $Proxy42.invoke(Unknown Source)
> 	at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201)
> 	at $Proxy542.dispatch(Unknown Source)
> 	at org.jboss.ws.extensions.eventing.mgmt.DispatcherDelegate.dispatch(DispatcherDelegate.java:42)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira