You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "viola.lu (JIRA)" <ji...@apache.org> on 2010/06/04 05:21:53 UTC

[jira] Commented: (GERONIMO-4738) ejb ws report authorization failures as 500 internal server error

    [ https://issues.apache.org/jira/browse/GERONIMO-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875448#action_12875448 ] 

viola.lu commented on GERONIMO-4738:
------------------------------------

Deploy modified jaxws-ejb-sec jar successfully, but there are errors from background console:
2010-06-04 12:13:19,000 ERROR [EjbModuleBuilder] JAXWSEJBModuleBuilderExtension.initContext() failed: Duplicate contextID registered! org.apache.geronimo.testsuite/jaxws-ejb-sec/2.2.1-SNAPSHOT/jar?EJBModule=org.apache.geronimo.testsuite/jaxws-ejb-sec/2.2.1-SNAPSHOT/jar,J2EEApplication=null,j2eeType=StatelessSessionBean,name=BeanBasic
org.apache.geronimo.common.DeploymentException: Duplicate contextID registered! org.apache.geronimo.testsuite/jaxws-ejb-sec/2.2.1-SNAPSHOT/jar?EJBModule=org.apache.geronimo.testsuite/jaxws-ejb-sec/2.2.1-SNAPSHOT/jar,J2EEApplication=null,j2eeType=StatelessSessionBean,name=BeanBasic
	at org.apache.geronimo.j2ee.deployment.EARContext.addSecurityContext(EARContext.java:128)
	at org.apache.geronimo.jaxws.builder.JAXWSEJBModuleBuilderExtension.initContext(JAXWSEJBModuleBuilderExtension.java:167)
	at org.apache.geronimo.openejb.deployment.EjbModuleBuilder.initContext(EjbModuleBuilder.java:541)
	at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:592)
	at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:257)
	at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:136)
	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:592)
	at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
	at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
	at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:851)
	at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
	at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
	at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
	at java.lang.Thread.run(Thread.java:595)

> ejb ws report authorization failures as 500 internal server error
> -----------------------------------------------------------------
>
>                 Key: GERONIMO-4738
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4738
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 2.2
>            Reporter: David Jencks
>            Assignee: Delos Dai
>             Fix For: 2.2.1
>
>
> If you secure an ejb web service with ejb security constraints cxf reports authorization failures as 500 internal server error and doesn't log much useful.  Axis2 logs the auth failure and IIRC reports 401 or 403.
> I think this can be reproduced by removing the ejb-jar.xml security constraints from   testsuite/webservices-testsuite/jaxws-tests/jaxws-ejb-sec/src/main/resources/META-INF/ejb-jar.xml

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.