[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2939) Handler chain file not found

[Richard Opalka (JIRA)]

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

Richard Opalka updated JBWS-2939:
---------------------------------

    Fix Version/s:     (was: jbossws-cxf-3.4.0)
                       (was: jbossws-native-3.4.0)


> Handler chain file not found
> ----------------------------
>
>                 Key: JBWS-2939
>                 URL: https://jira.jboss.org/browse/JBWS-2939
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions:  jbossws-native-3.2.2
>         Environment: Fedora 12
> JDK 6
> JBossAS 5.1.0.GA
> JBossWS-native-3.2.2.GA.
>            Reporter: Gary Brown
>            Assignee: Richard Opalka
>         Attachments: Component-SMSCTBC-1.0.0.war
>
>
> A RiftSaw user submitted an example to demonstrate an issue, but when I tried to install it I got the following exception:
> 12:47:08,079 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/home/gbrown/testing/riftsaw/test/jboss-5.1.0.GA/server/default/deploy/Component-SMSCTBC-1.0.0.war/ state=PreReal mode=Manual requiredState=Real
> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/home/gbrown/testing/riftsaw/test/jboss-5.1.0.GA/server/default/deploy/Component-SMSCTBC-1.0.0.war/
> 	at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
> 	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177)
> 	at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
> 	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
> 	at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
> 	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
> 	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
> 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
> 	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
> 	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
> 	at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
> 	at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
> 	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> 	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
> 	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> 	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> 	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:619)
> Caused by: org.jboss.ws.WSException: Cannot process handler chain: http://localhost:8080/Component-SMSCTBC-1.0.0/myhandler.xml
> 	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.getHandlerChainsMetaData(JAXWSMetaDataBuilder.java:290)
> 	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.processHandlerChain(JAXWSMetaDataBuilder.java:189)
> 	at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:194)
> 	at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50)
> 	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:62)
> 	at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:64)
> 	at org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer.internalDeploy(WSDeploymentAspectDeployer.java:107)
> 	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
> 	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
> 	... 24 more
> Caused by: java.io.FileNotFoundException: http://localhost:8080/Component-SMSCTBC-1.0.0/myhandler.xml
> 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1311)
> 	at java.net.URL.openStream(URL.java:1010)
> 	at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.getHandlerChainsMetaData(JAXWSMetaDataBuilder.java:268)
> 	... 32 more
> 12:47:08,098 WARN  [HDScanner] Failed to process changes
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> Related to the handle chain:
> @HandlerChain(file="http://localhost:8080/Component-SMSCTBC-1.0.0/myhandler.xml")
> The referenced file is present.
> The user did not experience the problem, however they were using the jbossws version 3.1.2.GA bundled with JBossAS 5.1.0.GA. So I tried reproducing the problem in vanilla JBossAS 5.1.0.GA (with no riftsaw installed) - and it did not complain when I deployed the attached war.
> However when I updated to jbossws-3.2.2.GA, it generated the exception.

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