[JBoss JIRA] (JBTM-959) Some XTS services fail to deploy to AS7 when deploying from Arquillian based test
5:03 p.m.
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
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/BusinessAgreementWithCoordinator...
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
5:21 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Andrew Dinn commented on JBTM-959:
----------------------------------
The reason the wsas and wscf tests are not affected is that they don't rely on the
JaxWS endpoints.
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
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/BusinessAgreementWithCoordinator...
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
9:58 a.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-959:
-------------------------------
Attachment: jbtm-959-target.tar.gz
Ivo,
Can you check your reproduction steps as I can't reproduce this error from them. I
have attached the generated target dir (jbtm-959-target.tar.gz), so that you can see the
failure I get.
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
Attachments: jbtm-959-target.tar.gz
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/BusinessAgreementWithCoordinator...
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
10:20 a.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on JBTM-959:
------------------------------------
Sure, already checking them..
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
Attachments: jbtm-959-target.tar.gz
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/BusinessAgreementWithCoordinator...
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
10:44 a.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on JBTM-959:
------------------------------------
Hmm, that's strange. It looks like the maven runs the tests on 'smoke' profile
for you instead of 'xts' profile, but there is <noSmoke>true</noSmoke>
property and activation of smoke profile by !noSmoke in the testsuite/integration/pom.xml.
I hit the same issue for the first run too, but for the second and further runs it works
as expected. I'll play with it a bit more.
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
Attachments: jbtm-959-target.tar.gz
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/BusinessAgreementWithCoordinator...
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
11 a.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on JBTM-959:
------------------------------------
Thanks Ivo,
Let me know when it's ready for me to re-produce.
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
Attachments: jbtm-959-target.tar.gz
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/BusinessAgreementWithCoordinator...
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
11:15 a.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on JBTM-959:
------------------------------------
There is something rotten in the maven or in the as7 testsuite. As I said I hit the same
issue once, but since that I haven't been able to reproduce it again even from the
scratch, i.e. with completely new git clone, build, test.
Paul, could you try to run the step 6 with adding '-P
!smoke.integration.tests.profile' or even better with adding '-X | tee log' at
the end of command line; and send me the log, please?
Thanks.
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
Attachments: jbtm-959-target.tar.gz
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/BusinessAgreementWithCoordinator...
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
11:43 a.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on JBTM-959:
------------------------------------
Ivo,
I re-ran and didn't get my issue anymore. So it looks like i can re-produce the
problem now. Thanks fir the assistance, I look into what's causing it.
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
Attachments: jbtm-959-target.tar.gz
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/BusinessAgreementWithCoordinator...
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
12:50 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on JBTM-959:
------------------------------------
Ivo,
I have a workaround which seems to make the tests pass. Set a fully qualified jbossHome in
xt-arquillian.xml:
{code}
<?xml version="1.0" encoding="UTF-8"?>
<arquillian xmlns="http://jboss.org/schema/arquillian"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://jboss.org/schema/arquillian
http://jboss.org/schema/arquillian/arquillian_1_0.xsd">
<container qualifier="jboss" default="true">
<configuration>
<property
name="jbossHome">/home/paul/dev/jboss-as.ivo/testsuite/integration/target/xts</property>
<property
name="javaVmArguments">${server.jvm.args}</property>
<property
name="serverConfig">${server.config:standalone-xts.xml}</property>
<property
name="allowConnectingToRunningServer">true</property>
</configuration>
</container>
</arquillian>
{code}
I accept that this is not a long term solution, but it now means that I should be able to
reproduce this in a simple example.
The next problem I have is that maven seems to still want to run the smoke tests, which I
take from your previous messages is bad:
{code}
.io has been deprecated
[INFO]
[INFO] --- maven-surefire-plugin:2.10:test (tests-xts.surefire) @
jboss-as-testsuite-integration ---
[INFO] Surefire report directory:
/home/paul/dev/jboss-as.ivo/testsuite/integration/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.as.test.xts.XTSUnitTestCase
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 277.924 sec
Results :
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] --- maven-surefire-plugin:2.10:test (smoke-default.surefire) @
jboss-as-testsuite-integration ---
[INFO] Surefire report directory:
/home/paul/dev/jboss-as.ivo/testsuite/integration/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.as.test.xts.XTSUnitTestCase
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.8 sec <<<
FAILURE!
Results :
Tests in error:
org.jboss.as.test.xts.XTSUnitTestCase: Could not deploy to container
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5:25.745s
[INFO] Finished at: Fri Nov 11 11:37:29 GMT 2011
[INFO] Final Memory: 65M/659M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test
(smoke-default.surefire) on project jboss-as-testsuite-integration: There are test
failures.
[ERROR]
[ERROR] Please refer to
/home/paul/dev/jboss-as.ivo/testsuite/integration/target/surefire-reports for the
individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the
following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
{code}
I'll attach the full log shortly. Just waiting for it to re-run with -X.
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
Attachments: jbtm-959-target.tar.gz
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/BusinessAgreementWithCoordinator...
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
1:32 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on JBTM-959:
------------------------------------
Thanks, Paul.
It is much appreciated. I will consult this with AS7 testsuite guys.
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
Attachments: jbtm-959-target.tar.gz
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/BusinessAgreementWithCoordinator...
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
2:46 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-959:
-------------------------------
Attachment: log.txt
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
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/BusinessAgreementWithCoordinator...
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
2:46 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on JBTM-959:
------------------------------------
See log.txt for the problem mentioned in my previous message
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
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/BusinessAgreementWithCoordinator...
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
2:48 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on JBTM-959:
------------------------------------
Thanks, Paul!
I've already changed the xts profile to pass the absolute path of jboss.home to
Arquillian. The change has been pushed to my github.
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
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/BusinessAgreementWithCoordinator...
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
2:50 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky edited comment on JBTM-959 at 11/11/11 8:49 AM:
--------------------------------------------------------------
Thanks, Paul!
I've already changed the xts profile to pass the absolute path of jboss.home to
Arquillian. The change has been pushed to my github account.
was (Author: istudens):
Thanks, Paul!
I've already changed the xts profile to pass the absolute path of jboss.home to
Arquillian. The change has been pushed to my github.
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
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/BusinessAgreementWithCoordinator...
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
4:08 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on JBTM-959:
------------------------------------
Ivo,
Do you know what type of jboss-as-arquillian-container is being used from the root
pom.xml?
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
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/BusinessAgreementWithCoordinator...
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
4:38 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on JBTM-959:
------------------------------------
Ivo,
this is proving a bit harder to reproduce, in a simple scenario, than I'd anticipated.
Are you happy for me to halt progress on this until you hear from the AS7 test guys? I
don't want to spend too long in this and then find out its something obvious they
already know about.
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
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/BusinessAgreementWithCoordinator...
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
4:46 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on JBTM-959:
------------------------------------
Sure, Paul. Let's wait for the AS7 test guys.
wrt container, it should be as7-managed. But it was provided by the AS7 itself, at least
in the past.
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
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/BusinessAgreementWithCoordinator...
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
2:55 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-959:
-------------------------------
Fix Version/s: 4.15.4
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/BusinessAgreementWithCoordinator...
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
2:55 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
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/BusinessAgreementWithCoordinator...
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
4:39 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on JBTM-959:
------------------------------------
It seems that this issue can be closed. I was told by AS7 testsuite guys that the relative
path to jboss home in arq's conf was an issue of the AS7 testsuite and that the full
path is needed there. The new AS7 testsuite structure should fix this in all arq conf
files.
Regarding the smoke test execution, it is needed to put '-DnoSmoke=true' on the
commnand line, although it is specified in the pom.xml (mvn profiles are selected before
the resolution of variables from pom file). Again, the new AS7 testsuite structure should
fix 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/BusinessAgreementWithCoordinator...
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
4:39 p.m.
[
https://issues.jboss.org/browse/JBTM-959?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky resolved JBTM-959.
--------------------------------
Resolution: Done
Closing this issues as the full path to jboss home fix the failure. Thanks, Paul.
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/BusinessAgreementWithCoordinator...
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
4536
days inactive
4550
days old
jbossts-issues@lists.jboss.org
20 comments
7 participants
participants (7)
-
Andrew Dinn (Commented) (JIRA) -
Ivo Studensky (Commented) (JIRA)
-
Ivo Studensky (Created) (JIRA)
-
Ivo Studensky (Issue Comment Edited) (JIRA)
-
Ivo Studensky (Resolved) (JIRA)
-
Paul Robinson (Commented) (JIRA)
-
Paul Robinson (Updated) (JIRA)