[jbossts-issues] [JBoss JIRA] (JBTM-959) Some XTS services fail to deploy to AS7 when deploying from Arquillian based test

Paul Robinson (Commented) (JIRA) jira-events at lists.jboss.org
Thu Nov 24 08:55:41 EST 2011


    [ https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645403#comment-12645403 ] 

Paul Robinson commented on JBTM-959:
------------------------------------

Ivo,

Did the AS7 test guys get back to you about this?
                
> Some XTS services fail to deploy to AS7 when deploying from Arquillian based test
> ---------------------------------------------------------------------------------
>
>                 Key: JBTM-959
>                 URL: https://issues.jboss.org/browse/JBTM-959
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: XTS
>    Affects Versions: 4.15.3
>            Reporter: Ivo Studensky
>            Assignee: Paul Robinson
>             Fix For: 4.15.4
>
>         Attachments: jbtm-959-target.tar.gz, log.txt
>
>
> Some of the XTS services fail to deploy to AS7 when deploying by an Arquillian test within the AS7 testsuite. The org.jboss.as.webservices.publish.EndpointPublisherImpl.publish() method fails in org.apache.naming.resources.FileDirContext.setDocBase() method which gets an invalid path to the AS7 tmp directory in which the context path occurs twice, see the stacktrace below and take notice of 'target/xts/standalone/tmp' substring in it. 
> This issue does not occur when the AS7 is manually started from the command line, but it only occurs when started by Arquillian from the new AS7 testsuite. However, it does not seem to hit all the XTS functionality as the wsas and wscf tests pass. Only ws-c, ws-t and ws-tx tests are hit by it.
> The stacktrace snippet from target/xts/standalone/logs/server.log:
> {noformat}
> 14:48:30,579 INFO  [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-2) WSDL published to: file:/home/studensky/job/git/jboss-as/testsuite/integration/target/xts/standalone/data/wsdl/ws-t11-client.deployment/TerminationParticipantService.wsdl
> 14:48:30,585 INFO  [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-7) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService
> 14:48:30,597 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Error starting static Resources: java.lang.IllegalArgumentException: Document base /home/studensky/job/git/jboss-as/testsuite/integration/target/xts/standalone/tmp/target/xts/standalone/tmp/ws-t11-client does not exist or is not a readable directory
> 	at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:148) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT]
> 	at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:3554) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT]
> 	at org.apache.catalina.core.StandardContext.start(StandardContext.java:3723) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT]
> 	at org.jboss.as.webservices.publish.EndpointPublisherImpl.startWebApp(EndpointPublisherImpl.java:133) [jboss-as-webservices-server-integration-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
> 	at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:103) [jboss-as-webservices-server-integration-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
> 	at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:81) [jboss-as-webservices-server-integration-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
> 	at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:76) [jboss-as-webservices-server-integration-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
> 	at org.jboss.as.webservices.service.EndpointPublishService.start(EndpointPublishService.java:87) [jboss-as-webservices-server-integration-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
> 	at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
> 14:48:30,599 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Error in resourceStart()
> 14:48:30,603 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Context [/ws-t11-client] startup failed due to previous errors
> 14:48:30,603 INFO  [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/ws-t11-client] has not been started
> {noformat}
> The list of services affected by this issue:
> /ws-t11-client
> /ws-t11-participant
> /ws-t11-coordinator
> /ws-c11

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossts-issues mailing list