[jboss-jira] [JBoss JIRA] Updated: (JBAS-5301) JaasSecurityManagerService.startService - java.lang.IllegalArgumentException: handler exists

[Anil Saldhana (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anil Saldhana updated JBAS-5301:
--------------------------------

    Fix Version/s: JBossAS-5.0.0.GA


> JaasSecurityManagerService.startService - java.lang.IllegalArgumentException: handler exists
> --------------------------------------------------------------------------------------------
>
>                 Key: JBAS-5301
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5301
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions:  JBossAS-5.0.0.Beta3
>         Environment: EmbeddedJboss Beta3, Windows XP sp2, IBM Websphere 6.1.11, IBM JDK 1.5.0 J9 2.3
>            Reporter: Dror Bereznitsky
>            Assignee: Anil Saldhana
>             Fix For: JBossAS-5.0.0.GA
>
>
> When hot deploying EmbeddedJboss on IBM Websphere the JaasSecurityManagerService tries to register the "org.jboss.security.auth.spi.CallbackHandler" in jacc policy context.
>    PolicyContext.registerHandler(CallbackHandlerPolicyContextHandler.CALLBACK_HANDLER_KEY,
>             chandler, false);
> Since the policy context is static it already contains this handler from previous deployment resulting in registration failure:
> java.lang.IllegalArgumentException: handler exists
> 	at javax.security.jacc.PolicyContext.registerHandler(PolicyContext.java:218)
> 	at org.jboss.security.plugins.JaasSecurityManagerService.startService(JaasSecurityManagerService.java:448)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:299)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:615)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> 	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:668)
> 	at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:167)
> 	at $Proxy64.start(Unknown Source)
> This issue will probably happen on each platform that implements the context handler map as a static member.

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