[JBoss JIRA] (JBTM-1844) CrashRecovery05_2_Test028 failed
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1844?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1844:
----------------------------------
Description:
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/192/TESTS=QA_JTS_...
{code}
starting command: /usr/local/jdk1.7.0_17/bin/java -classpath dist/narayana-full-5.0.0.M4-SNAPSHOT/etc/:dist/narayana-full-5.0.0.M4-SNAPSHOT/lib/*:dist/narayana-full-5.0.0.M4-SNAPSHOT/lib/ext/*:dist/narayana-full-5.0.0.M4-SNAPSHOT/jacorb/lib/*:dist/narayana-full-5.0.0.M4-SNAPSHOT/jacorb/etc/:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=2 -DCoordinatorEnvironmentBean.defaultTimeout=240 -DCoordinatorEnvironmentBean.dynamic1PC=false -Demma.coverage.out.file=./testoutput/crashrecovery05_2/CrashRecovery05_2_Test028/client1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/workspace/narayana/TESTS/QA_JTS_JACORB/jdk/jdk7.latest/label/linux/qa/testoutput/crashrecovery05_2/CrashRecovery05_2_Test028/client -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.CrashRecovery05Clients2.Client03a value_3 value_4
2013-07-13 09:09:35,696 err: log4j:WARN No appenders could be found for logger (org.jboss.logging).
2013-07-13 09:09:35,696 err: log4j:WARN Please initialize the log4j system properly.
2013-07-13 09:09:35,778 err: SLF4J: Class path contains multiple SLF4J bindings.
2013-07-13 09:09:35,778 err: SLF4J: Found binding in [jar:file:/home/hudson/workspace/narayana/TESTS/QA_JTS_JACORB/jdk/jdk7.latest/label/linux/qa/dist/narayana-full-5.0.0.M4-SNAPSHOT/lib/ext/slf4j-simple.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2013-07-13 09:09:35,779 err: SLF4J: Found binding in [jar:file:/home/hudson/workspace/narayana/TESTS/QA_JTS_JACORB/jdk/jdk7.latest/label/linux/qa/dist/narayana-full-5.0.0.M4-SNAPSHOT/jacorb/lib/slf4j-jdk14-1.5.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2013-07-13 09:09:35,779 err: SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2013-07-13 09:09:35,787 err: 5 [main] INFO jacorb.config - base configuration loaded from classpath orb.properties
2013-07-13 09:09:35,788 err: 5 [main] WARN jacorb.config - File e:/JacORB_CONFIG_FEATURE/etc/jacorb.properties for configuration jacorb not found
2013-07-13 09:09:35,794 err: 12 [main] INFO jacorb.config - configuration jacorb loaded from classpath
2013-07-13 09:09:35,827 err: 45 [main] INFO jacorb.orb.print_version -
2013-07-13 09:09:35,827 err: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2013-07-13 09:09:35,827 err: JacORB V 2.3.1 (JBoss patch01), www.jacorb.org
2013-07-13 09:09:35,827 err: (C) The JacORB project 29-Jul-2009
2013-07-13 09:09:35,827 err: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2013-07-13 09:09:35,969 err: 187 [main] INFO jacorb.orb - Property "jacorb.hashtable_class" is set to: java.util.Hashtable
2013-07-13 09:09:35,986 err: 204 [main] INFO jacorb.orb.interceptors - InterceptorManager started with 1 Server Interceptors, 1 Client Interceptors and 1 IOR Interceptors
2013-07-13 09:09:36,156 err: 374 [main] INFO jacorb.config - base configuration loaded from classpath orb.properties
2013-07-13 09:09:36,156 err: 374 [main] WARN jacorb.config - File e:/JacORB_CONFIG_FEATURE/etc/jacorb.properties for configuration jacorb not found
2013-07-13 09:09:36,157 err: 375 [main] INFO jacorb.config - configuration jacorb loaded from classpath
2013-07-13 09:09:36,158 err: 376 [main] INFO jacorb.orb.singleton - created ORBSingleton
2013-07-13 09:09:36,270 err: 488 [main] INFO jacorb.orb.giop - ClientConnectionManager: created new ClientGIOPConnection to 172.17.131.36:36476 (3ec35868)
2013-07-13 09:09:36,299 err: 517 [main] INFO jacorb.orb.iiop - Connected to 172.17.131.36:36476 from local port 43572
2013-07-13 09:09:36,378 err: 596 [main] INFO jacorb.orb.giop - ClientConnectionManager: created new ClientGIOPConnection to 172.17.131.36:40980 (62565cf8)
2013-07-13 09:09:36,384 err: 602 [main] INFO jacorb.orb.iiop - Connected to 172.17.131.36:40980 from local port 55512
2013-07-13 09:09:38,189 out: Gonna fail1
2013-07-13 09:09:38,190 out: Gonna fail2
2013-07-13 09:09:38,190 out: Gonna fail3
2013-07-13 09:09:38,190 out: Gonna fail4
2013-07-13 09:09:38,190 out: Using timeout delay factor of 2
2013-07-13 09:09:58,219 out: Gonna fail5: ResourceTraceNone
2013-07-13 09:09:58,219 out: Gonna fail6
2013-07-13 09:09:58,219 out: Failed
2013-07-13 09:09:58,220 err: 22438 [POADestructor] INFO jacorb.poa - POA RootPOA destroyed
2013-07-13 09:09:58,220 err: 22438 [main] INFO jacorb.orb - prepare ORB for shutdown...
2013-07-13 09:09:58,220 err: 22438 [main] INFO jacorb.orb - ORB going down...
2013-07-13 09:09:58,227 err: 22439 [main] INFO jacorb.orb.iiop - Client-side TCP transport to 172.17.131.36:36476 closed.
2013-07-13 09:09:58,227 err: 22439 [main] INFO jacorb.orb.iiop - Client-side TCP transport to 172.17.131.36:40980 closed.
2013-07-13 09:09:58,227 err: 22439 [main] INFO jacorb.orb - ORB shutdown complete
2013-07-13 09:09:58,227 err: 22445 [ClientMessageReceptor0] INFO jacorb.util.tpool - ConsumerTie exited
2013-07-13 09:09:58,227 err: 22445 [ClientMessageReceptor1] INFO jacorb.util.tpool - ConsumerTie exited
2013-07-13 09:09:58,227 err: 22445 [ServerSocketListener] INFO jacorb.orb.iiop - Listener exited
{code}
was:http://172.17.131.2/view/Narayana+BlackTie/job/narayana/192/TESTS=QA_JTS_JACORB,jdk=jdk7.latest,label=linux/consoleText
> CrashRecovery05_2_Test028 failed
> --------------------------------
>
> Key: JBTM-1844
> URL: https://issues.jboss.org/browse/JBTM-1844
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTS, Testing
> Reporter: Gytis Trikleris
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.M4
>
> Attachments: CrashRecovery05_2_Test028.zip, TEST-org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2.txt
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/192/TESTS=QA_JTS_...
> {code}
> starting command: /usr/local/jdk1.7.0_17/bin/java -classpath dist/narayana-full-5.0.0.M4-SNAPSHOT/etc/:dist/narayana-full-5.0.0.M4-SNAPSHOT/lib/*:dist/narayana-full-5.0.0.M4-SNAPSHOT/lib/ext/*:dist/narayana-full-5.0.0.M4-SNAPSHOT/jacorb/lib/*:dist/narayana-full-5.0.0.M4-SNAPSHOT/jacorb/etc/:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=2 -DCoordinatorEnvironmentBean.defaultTimeout=240 -DCoordinatorEnvironmentBean.dynamic1PC=false -Demma.coverage.out.file=./testoutput/crashrecovery05_2/CrashRecovery05_2_Test028/client1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/workspace/narayana/TESTS/QA_JTS_JACORB/jdk/jdk7.latest/label/linux/qa/testoutput/crashrecovery05_2/CrashRecovery05_2_Test028/client -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.CrashRecovery05Clients2.Client03a value_3 value_4
> 2013-07-13 09:09:35,696 err: log4j:WARN No appenders could be found for logger (org.jboss.logging).
> 2013-07-13 09:09:35,696 err: log4j:WARN Please initialize the log4j system properly.
> 2013-07-13 09:09:35,778 err: SLF4J: Class path contains multiple SLF4J bindings.
> 2013-07-13 09:09:35,778 err: SLF4J: Found binding in [jar:file:/home/hudson/workspace/narayana/TESTS/QA_JTS_JACORB/jdk/jdk7.latest/label/linux/qa/dist/narayana-full-5.0.0.M4-SNAPSHOT/lib/ext/slf4j-simple.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> 2013-07-13 09:09:35,779 err: SLF4J: Found binding in [jar:file:/home/hudson/workspace/narayana/TESTS/QA_JTS_JACORB/jdk/jdk7.latest/label/linux/qa/dist/narayana-full-5.0.0.M4-SNAPSHOT/jacorb/lib/slf4j-jdk14-1.5.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> 2013-07-13 09:09:35,779 err: SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> 2013-07-13 09:09:35,787 err: 5 [main] INFO jacorb.config - base configuration loaded from classpath orb.properties
> 2013-07-13 09:09:35,788 err: 5 [main] WARN jacorb.config - File e:/JacORB_CONFIG_FEATURE/etc/jacorb.properties for configuration jacorb not found
> 2013-07-13 09:09:35,794 err: 12 [main] INFO jacorb.config - configuration jacorb loaded from classpath
> 2013-07-13 09:09:35,827 err: 45 [main] INFO jacorb.orb.print_version -
> 2013-07-13 09:09:35,827 err: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 2013-07-13 09:09:35,827 err: JacORB V 2.3.1 (JBoss patch01), www.jacorb.org
> 2013-07-13 09:09:35,827 err: (C) The JacORB project 29-Jul-2009
> 2013-07-13 09:09:35,827 err: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 2013-07-13 09:09:35,969 err: 187 [main] INFO jacorb.orb - Property "jacorb.hashtable_class" is set to: java.util.Hashtable
> 2013-07-13 09:09:35,986 err: 204 [main] INFO jacorb.orb.interceptors - InterceptorManager started with 1 Server Interceptors, 1 Client Interceptors and 1 IOR Interceptors
> 2013-07-13 09:09:36,156 err: 374 [main] INFO jacorb.config - base configuration loaded from classpath orb.properties
> 2013-07-13 09:09:36,156 err: 374 [main] WARN jacorb.config - File e:/JacORB_CONFIG_FEATURE/etc/jacorb.properties for configuration jacorb not found
> 2013-07-13 09:09:36,157 err: 375 [main] INFO jacorb.config - configuration jacorb loaded from classpath
> 2013-07-13 09:09:36,158 err: 376 [main] INFO jacorb.orb.singleton - created ORBSingleton
> 2013-07-13 09:09:36,270 err: 488 [main] INFO jacorb.orb.giop - ClientConnectionManager: created new ClientGIOPConnection to 172.17.131.36:36476 (3ec35868)
> 2013-07-13 09:09:36,299 err: 517 [main] INFO jacorb.orb.iiop - Connected to 172.17.131.36:36476 from local port 43572
> 2013-07-13 09:09:36,378 err: 596 [main] INFO jacorb.orb.giop - ClientConnectionManager: created new ClientGIOPConnection to 172.17.131.36:40980 (62565cf8)
> 2013-07-13 09:09:36,384 err: 602 [main] INFO jacorb.orb.iiop - Connected to 172.17.131.36:40980 from local port 55512
> 2013-07-13 09:09:38,189 out: Gonna fail1
> 2013-07-13 09:09:38,190 out: Gonna fail2
> 2013-07-13 09:09:38,190 out: Gonna fail3
> 2013-07-13 09:09:38,190 out: Gonna fail4
> 2013-07-13 09:09:38,190 out: Using timeout delay factor of 2
> 2013-07-13 09:09:58,219 out: Gonna fail5: ResourceTraceNone
> 2013-07-13 09:09:58,219 out: Gonna fail6
> 2013-07-13 09:09:58,219 out: Failed
> 2013-07-13 09:09:58,220 err: 22438 [POADestructor] INFO jacorb.poa - POA RootPOA destroyed
> 2013-07-13 09:09:58,220 err: 22438 [main] INFO jacorb.orb - prepare ORB for shutdown...
> 2013-07-13 09:09:58,220 err: 22438 [main] INFO jacorb.orb - ORB going down...
> 2013-07-13 09:09:58,227 err: 22439 [main] INFO jacorb.orb.iiop - Client-side TCP transport to 172.17.131.36:36476 closed.
> 2013-07-13 09:09:58,227 err: 22439 [main] INFO jacorb.orb.iiop - Client-side TCP transport to 172.17.131.36:40980 closed.
> 2013-07-13 09:09:58,227 err: 22439 [main] INFO jacorb.orb - ORB shutdown complete
> 2013-07-13 09:09:58,227 err: 22445 [ClientMessageReceptor0] INFO jacorb.util.tpool - ConsumerTie exited
> 2013-07-13 09:09:58,227 err: 22445 [ClientMessageReceptor1] INFO jacorb.util.tpool - ConsumerTie exited
> 2013-07-13 09:09:58,227 err: 22445 [ServerSocketListener] INFO jacorb.orb.iiop - Listener exited
> {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) TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1843?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris edited comment on JBTM-1843 at 7/15/13 11:00 AM:
-----------------------------------------------------------------
Deleted
was (Author: gytis):
Should I just delete other failures caused because of this which are not documented?
> TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment
> -------------------------------------------------------------------------
>
> 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: Application Server Integration
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> 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) TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1843?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris edited comment on JBTM-1843 at 7/15/13 11:01 AM:
-----------------------------------------------------------------
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/188,
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/189
was (Author: gytis):
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/188
> TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment
> -------------------------------------------------------------------------
>
> 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: Application Server Integration
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> 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) TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1843?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris edited comment on JBTM-1843 at 7/15/13 10:56 AM:
-----------------------------------------------------------------
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/188
was (Author: gytis):
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...
> TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment
> -------------------------------------------------------------------------
>
> 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: Application Server Integration
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> 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) TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1843?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1843:
----------------------------------
Component/s: Application Server Integration
(was: BlackTie)
> TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment
> -------------------------------------------------------------------------
>
> 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: Application Server Integration
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> 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) TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1843?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1843:
----------------------------------
Summary: TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment (was: test.war failed to deploy in AdvertiseUnadvertiseTest)
> TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment
> -------------------------------------------------------------------------
>
> 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: Paul Robinson
> 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) TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1843?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on JBTM-1843:
---------------------------------------
Should I just delete other failures caused because of this which are not documented?
> TransactionCDIProcessor fails to lookup org.jboss.jandex.Index attachment
> -------------------------------------------------------------------------
>
> 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: Paul Robinson
> 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 Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1843?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1843:
--------------------------------
Assignee: Paul Robinson (was: Amos Feng)
> 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: Paul Robinson
> 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