[JBoss JIRA] (JBTM-1843) test.war failed to deploy in AdvertiseUnadvertiseTest
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1843?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1843:
-------------------------------------
This should be fixed now. I'll keep an eye out for a passing build.
> test.war failed to deploy in AdvertiseUnadvertiseTest
> -----------------------------------------------------
>
> Key: JBTM-1843
> URL: https://issues.jboss.org/browse/JBTM-1843
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/187/TESTS=BLACKTI...
> {code}
> Running AdvertiseUnadvertiseTest
> [0m14:14:41,397 INFO [org.jboss.as.repository] (management-handler-thread - 5) JBAS014900: Content added at location /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el5/blacktie/jboss-as/standalone/data/content/c1/07acf40dac17fe603f6631c2ad2d746c824553/content
> [0m[0m14:14:41,400 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war")
> [0m[31m14:14:41,756 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."test.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "test.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Alpha3-SNAPSHOT.jar:8.0.0.Alpha3-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1942) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1875) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not lookup org.jboss.as.server.deployment.SimpleAttachmentKey<org.jboss.jandex.Index>
> at org.jboss.as.txn.deployment.TransactionCDIProcessor.deploy(TransactionCDIProcessor.java:63)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha3-SNAPSHOT.jar:8.0.0.Alpha3-SNAPSHOT]
> ... 5 more
> [0m[31m14:14:41,759 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 5) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "test.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"test.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"test.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not lookup org.jboss.as.server.deployment.SimpleAttachmentKey<org.jboss.jandex.Index>"}}
> [0m[31m14:14:41,763 ERROR [org.jboss.as.server] (management-handler-thread - 5) JBAS015870: Deploy of deployment "test.war" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"test.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"test.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not lookup org.jboss.as.server.deployment.SimpleAttachmentKey<org.jboss.jandex.Index>"}}
> [0m[0m14:14:41,784 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 20ms
> [0m[0m14:14:41,785 INFO [org.jboss.as.controller] (management-handler-thread - 5) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.deployment.unit."restat-web-5.0.0.M4-SNAPSHOT.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."restat-web-5.0.0.M4-SNAPSHOT.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "restat-web-5.0.0.M4-SNAPSHOT.war"
> service jboss.deployment.unit."test.war".DEPENDENCIES
> [0mTests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.646 sec <<< FAILURE!
> Results :
> Tests in error:
> AdvertiseUnadvertiseTest: Cannot deploy: test.war
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBTM-1843) test.war failed to deploy in AdvertiseUnadvertiseTest
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1843?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on JBTM-1843:
---------------------------------------
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/188/TESTS=BLACKTI...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/188/TESTS=BLACKTI...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/188/TESTS=BLACKTI...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/188/TESTS=BLACKTI...
> test.war failed to deploy in AdvertiseUnadvertiseTest
> -----------------------------------------------------
>
> Key: JBTM-1843
> URL: https://issues.jboss.org/browse/JBTM-1843
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/187/TESTS=BLACKTI...
> {code}
> Running AdvertiseUnadvertiseTest
> [0m14:14:41,397 INFO [org.jboss.as.repository] (management-handler-thread - 5) JBAS014900: Content added at location /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el5/blacktie/jboss-as/standalone/data/content/c1/07acf40dac17fe603f6631c2ad2d746c824553/content
> [0m[0m14:14:41,400 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war")
> [0m[31m14:14:41,756 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."test.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "test.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Alpha3-SNAPSHOT.jar:8.0.0.Alpha3-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1942) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1875) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not lookup org.jboss.as.server.deployment.SimpleAttachmentKey<org.jboss.jandex.Index>
> at org.jboss.as.txn.deployment.TransactionCDIProcessor.deploy(TransactionCDIProcessor.java:63)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha3-SNAPSHOT.jar:8.0.0.Alpha3-SNAPSHOT]
> ... 5 more
> [0m[31m14:14:41,759 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 5) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "test.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"test.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"test.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not lookup org.jboss.as.server.deployment.SimpleAttachmentKey<org.jboss.jandex.Index>"}}
> [0m[31m14:14:41,763 ERROR [org.jboss.as.server] (management-handler-thread - 5) JBAS015870: Deploy of deployment "test.war" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"test.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"test.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not lookup org.jboss.as.server.deployment.SimpleAttachmentKey<org.jboss.jandex.Index>"}}
> [0m[0m14:14:41,784 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 20ms
> [0m[0m14:14:41,785 INFO [org.jboss.as.controller] (management-handler-thread - 5) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.deployment.unit."restat-web-5.0.0.M4-SNAPSHOT.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."restat-web-5.0.0.M4-SNAPSHOT.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "restat-web-5.0.0.M4-SNAPSHOT.war"
> service jboss.deployment.unit."test.war".DEPENDENCIES
> [0mTests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.646 sec <<< FAILURE!
> Results :
> Tests in error:
> AdvertiseUnadvertiseTest: Cannot deploy: test.war
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBTM-1843) test.war failed to deploy in AdvertiseUnadvertiseTest
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-1843:
-------------------------------------
Summary: test.war failed to deploy in AdvertiseUnadvertiseTest
Key: JBTM-1843
URL: https://issues.jboss.org/browse/JBTM-1843
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: BlackTie
Reporter: Gytis Trikleris
Assignee: Amos Feng
Fix For: 5.0.0.M4
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/187/TESTS=BLACKTI...
{code}
Running AdvertiseUnadvertiseTest
[0m14:14:41,397 INFO [org.jboss.as.repository] (management-handler-thread - 5) JBAS014900: Content added at location /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el5/blacktie/jboss-as/standalone/data/content/c1/07acf40dac17fe603f6631c2ad2d746c824553/content
[0m[0m14:14:41,400 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war")
[0m[31m14:14:41,756 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."test.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "test.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Alpha3-SNAPSHOT.jar:8.0.0.Alpha3-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1942) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1875) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not lookup org.jboss.as.server.deployment.SimpleAttachmentKey<org.jboss.jandex.Index>
at org.jboss.as.txn.deployment.TransactionCDIProcessor.deploy(TransactionCDIProcessor.java:63)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha3-SNAPSHOT.jar:8.0.0.Alpha3-SNAPSHOT]
... 5 more
[0m[31m14:14:41,759 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 5) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "test.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"test.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"test.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not lookup org.jboss.as.server.deployment.SimpleAttachmentKey<org.jboss.jandex.Index>"}}
[0m[31m14:14:41,763 ERROR [org.jboss.as.server] (management-handler-thread - 5) JBAS015870: Deploy of deployment "test.war" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"test.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment \"test.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not lookup org.jboss.as.server.deployment.SimpleAttachmentKey<org.jboss.jandex.Index>"}}
[0m[0m14:14:41,784 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 20ms
[0m[0m14:14:41,785 INFO [org.jboss.as.controller] (management-handler-thread - 5) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."restat-web-5.0.0.M4-SNAPSHOT.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."restat-web-5.0.0.M4-SNAPSHOT.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "restat-web-5.0.0.M4-SNAPSHOT.war"
service jboss.deployment.unit."test.war".DEPENDENCIES
[0mTests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.646 sec <<< FAILURE!
Results :
Tests in error:
AdvertiseUnadvertiseTest: Cannot deploy: test.war
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBTM-1830) WSBAParticipantCompletionTestCase failure: 'participant_completion_coordinator_rules.btm' either doesn't exist or isn't a file
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1830?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on JBTM-1830:
---------------------------------------
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/186/TESTS=XTS,jdk...
> WSBAParticipantCompletionTestCase failure: 'participant_completion_coordinator_rules.btm' either doesn't exist or isn't a file
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1830
> URL: https://issues.jboss.org/browse/JBTM-1830
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Application Server Integration, Testing, XTS
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/173/TESTS=XTS,jdk...
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase
> -------------------------------------------------------------------------------
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.704 sec <<< FAILURE!
> org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase Time elapsed: 2.325 sec <<< ERROR!
> java.lang.RuntimeException: Failed to submit Byteman script
> at org.jboss.as.test.xts.simple.BMScript.submit(BMScript.java:43)
> at org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase.submitBytemanScript(WSBAParticipantCompletionTestCase.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> Caused by: java.lang.RuntimeException: 'participant_completion_coordinator_rules.btm' either doesn't exist or isn't a file
> at org.jboss.as.test.xts.simple.BMScript.getScriptFiles(BMScript.java:69)
> at org.jboss.as.test.xts.simple.BMScript.submit(BMScript.java:40)
> ... 54 more
> org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase Time elapsed: 2.326 sec <<< ERROR!
> java.lang.RuntimeException: Failed to remove Byteman script
> at org.jboss.as.test.xts.simple.BMScript.remove(BMScript.java:53)
> at org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase.removeBytemanScript(WSBAParticipantCompletionTestCase.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87)
> at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> Caused by: java.lang.RuntimeException: 'participant_completion_coordinator_rules.btm' either doesn't exist or isn't a file
> at org.jboss.as.test.xts.simple.BMScript.getScriptFiles(BMScript.java:69)
> at org.jboss.as.test.xts.simple.BMScript.remove(BMScript.java:50)
> ... 54 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBTM-1790) If xaNodeName is not set then a nullpointerexception is raised rather than an informative exception
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1790?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1790:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> If xaNodeName is not set then a nullpointerexception is raised rather than an informative exception
> ---------------------------------------------------------------------------------------------------
>
> Key: JBTM-1790
> URL: https://issues.jboss.org/browse/JBTM-1790
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA, JTS
> Affects Versions: 5.0.0.M3
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M4
>
> Original Estimate: 30 minutes
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> TxControl needs a static initialization block reintroducing/similar such that if CoordinatorEnvironmentBean::getNodeIdentifier() returns null it should log a fatal error and fail to initialize.
> Currently for JTS an obscure stack trace is printed:
> [INFO] --- exec-maven-plugin:1.2.1:java (default-cli) @ iiop-jts-client ---
> Jun 21, 2013 6:08:11 PM com.arjuna.orbportability.internal.utils.InitLoader createInstance
> INFO: ARJUNA021027: Loading PreInitLoader class - com.arjuna.ats.internal.jts.context.ContextPropagationManager
> Jun 21, 2013 6:08:11 PM org.jacorb.config.JacORBConfiguration init
> WARNING: jacorb.home unset! Will use '.'
> Jun 21, 2013 6:08:11 PM org.jacorb.config.JacORBConfiguration init
> WARNING: File ./jacorb.properties for configuration jacorb not found
> Jun 21, 2013 6:08:11 PM org.jacorb.config.JacORBConfiguration init
> INFO: configuration jacorb loaded from classpath
> Jun 21, 2013 6:08:11 PM com.arjuna.orbportability.internal.utils.InitLoader createInstance
> INFO: ARJUNA021027: Loading PostInitLoader class - com.arjuna.ats.internal.jts.recovery.RecoveryInit
> Jun 21, 2013 6:08:11 PM com.arjuna.orbportability.internal.utils.InitLoader createInstance
> INFO: ARJUNA021027: Loading PostInitLoader class - com.arjuna.ats.jts.utils.ORBSetup
> Jun 21, 2013 6:08:11 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService
> INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 43728
> Jun 21, 2013 6:08:11 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init>
> INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 43728
> Jun 21, 2013 6:08:11 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start
> INFO: ARJUNA012170: TransactionStatusManager started on port 43728 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
> java.rmi.RemoteException: CORBA UNKNOWN 30001 No; nested exception is:
> org.omg.CORBA.UNKNOWN: java.lang.NullPointerException vmcid: 0x7000 minor code: 1329 completed: No
> at com.sun.corba.se.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:315)
> at javax.rmi.CORBA.Util.mapSystemException(Util.java:83)
> at com.sun.corba.se.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:164)
> at com.sun.corba.se.spi.orbutil.proxy.CompositeInvocationHandlerImpl.invoke(CompositeInvocationHandlerImpl.java:79)
> at com.sun.proxy.$Proxy7.hello(Unknown Source)
> at org.jboss.qa.IIOPTesting.main(IIOPTesting.java:27)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.omg.CORBA.UNKNOWN: java.lang.NullPointerException vmcid: 0x7000 minor code: 1329 completed: No
> at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.get_txcontext(ArjunaTransactionImple.java:1300)
> at com.arjuna.ArjunaOTS.ArjunaTransactionPOATie.get_txcontext(ArjunaTransactionPOATie.java:129)
> at com.arjuna.ArjunaOTS._ArjunaTransactionStub.get_txcontext(_ArjunaTransactionStub.java:788)
> at com.arjuna.ats.jts.orbspecific.jacorb.interceptors.interposition.InterpositionClientRequestInterceptorImpl.send_request(InterpositionClientRequestInterceptorImpl.java:196)
> at org.jacorb.orb.portableInterceptor.ClientInterceptorIterator.invoke(ClientInterceptorIterator.java:95)
> at org.jacorb.orb.portableInterceptor.AbstractInterceptorIterator.iterate(AbstractInterceptorIterator.java:67)
> at org.jacorb.orb.portableInterceptor.ClientInterceptorIterator.iterate(ClientInterceptorIterator.java:68)
> at org.jacorb.orb.ClientInterceptorHandler.invokeInterceptors(ClientInterceptorHandler.java:265)
> at org.jacorb.orb.ClientInterceptorHandler.handle_send_request(ClientInterceptorHandler.java:99)
> at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:996)
> at org.jacorb.orb.Delegate.invoke(Delegate.java:957)
> at com.sun.corba.se.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:151)
> ... 9 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBTM-1799) Move javadoc configuration to "release" profile, and remove extra install plugin config
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1799?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1799:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Thanks for the contribution
> Move javadoc configuration to "release" profile, and remove extra install plugin config
> ---------------------------------------------------------------------------------------
>
> Key: JBTM-1799
> URL: https://issues.jboss.org/browse/JBTM-1799
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Gier
> Assignee: Paul Gier
> Fix For: 5.0.0.M4
>
>
> Several modules generate javadocs using the maven-javadoc-plugin. This is not needed for every build, just for releases, so it could be moved to a "release" profile.
> The narayana-full module depends on the generated javadoc, so this module will also need to be moved to the release profile.
> -Also, there is currently extra configuration of the install plugin in several modules which doesn't appear to have any function.-
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBTM-1806) Remove XTS servicetests code from emma statistics
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1806?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson resolved JBTM-1806.
---------------------------------
Assignee: Tom Jenkinson (was: Paul Robinson)
Resolution: Done
Resolved in (also includes not run interop classes) https://github.com/jbosstm/narayana/commit/7f2fd0fffb743dc82c4e11dca8e19b...
> Remove XTS servicetests code from emma statistics
> -------------------------------------------------
>
> Key: JBTM-1806
> URL: https://issues.jboss.org/browse/JBTM-1806
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M4
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> As the code for the package: org.jboss.jbossts.xts.servicetests.* exists in "src/main", i.e. ./XTS/localjunit/xtstest/src/org/jboss/jbossts/xts/servicetests it is being instrumented and its numbers are therefore affecting coverage.
> Interestingly the numbers are actually showing zero percent rather than 100% for these packages, so the first thing to investigate is why does this code exist and are we actually using it to test. After that we should exclude this package in the root /pom.xml in the emma instrument goal similar to the orb generated source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months