July 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1825) Error starting XTS Services

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1825?page=com.atlassian.jira.plugin.... ] Work on JBTM-1825 stopped by Amos Feng. > Error starting XTS Services > --------------------------- > > Key: JBTM-1825 > URL: https://issues.jboss.org/browse/JBTM-1825 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Server Integration, XTS > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M4 > > > On Wildfly master as of today, booting with standalone-xts.xml produces these errors: > {code} > 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-8) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-11) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-5) JBAS015539: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-1) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=BusinessAgreementWithCoordinatorCompletionCoordinatorService > 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-8) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=CoordinatorService > 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-11) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=CompletionCoordinatorService > 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-4) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=TerminationCoordinatorRPCService > 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-3) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=TerminationCoordinatorService > 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-2) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=BusinessAgreementWithParticipantCompletionCoordinatorService > 14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-5) JBWS022103: Cannot start endpoint in state STARTED: jboss.ws:context=ws-t11-coordinator,endpoint=CompletionCoordinatorRPCService > {code} > The XTS integration tests in the WildFly codebase under 'testsuite/integration/xts' pass on my box, but are failing in CI (sometimes). I don't know how any of the XTS tests could be passing if those services really haven't started up. > Note that the wsdl is available at http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService?wsdl, despite TerminationCoordinatorService claiming not to have started. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1796) BlackTie quickstart build hangs

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1796?page=com.atlassian.jira.plugin.... ] Amos Feng resolved JBTM-1796. ----------------------------- Resolution: Done > BlackTie quickstart build hangs > ------------------------------- > > Key: JBTM-1796 > URL: https://issues.jboss.org/browse/JBTM-1796 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Demonstrator > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M4 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-quickstarts-windo... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1568) Install the StompConnect component of BlackTie as an WildFly subsystem module

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1568?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1568: --------------------------------- FYI, the hornetq can support stomp protocol with the following configuration {noformat} <acceptor name="stomp-acceptor"> <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class> <param key="protocol" value="stomp" /> <param key="port" value="61613" /> </acceptor> {noformat} I've just test but it does not work with our tests. The error looks like it can not find the queue. > Install the StompConnect component of BlackTie as an WildFly subsystem module > ----------------------------------------------------------------------------- > > Key: JBTM-1568 > URL: https://issues.jboss.org/browse/JBTM-1568 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.0.Final > > Original Estimate: 2 weeks > Time Spent: 1 week, 1 day > Remaining Estimate: 4 days > > Apparently there is a way to deploy a war as a module coming soon, wait till this is available possibly. Though, in the meantime, you could merge the stompconnect ear and blacktie-admin-servers ear into a single ear. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1568) Install the StompConnect component of BlackTie as an WildFly subsystem module

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1568?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1568: --------------------------------- It looks good to me and StompConnectService is OK in the blacktie subsystem https://github.com/zhfeng/jboss-as/blob/a071a0b7d8bd03ce374b43b4245d74f7e... > Install the StompConnect component of BlackTie as an WildFly subsystem module > ----------------------------------------------------------------------------- > > Key: JBTM-1568 > URL: https://issues.jboss.org/browse/JBTM-1568 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.0.Final > > Original Estimate: 2 weeks > Time Spent: 1 week, 1 day > Remaining Estimate: 4 days > > Apparently there is a way to deploy a war as a module coming soon, wait till this is available possibly. Though, in the meantime, you could merge the stompconnect ear and blacktie-admin-servers ear into a single ear. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-846) Allow multiple transaction managers with different configurations to operate in a single JVM

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/JBTM-846?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on JBTM-846: ---------------------------------- I don't think we've encountered any use cases for multiple instances of JTS or JTA in WildFly, if that helps. At least I've never heard of such a request. > Allow multiple transaction managers with different configurations to operate in a single JVM > -------------------------------------------------------------------------------------------- > > Key: JBTM-846 > URL: https://issues.jboss.org/browse/JBTM-846 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTA, JTS, Recovery, Transaction Core, XTS > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > This will require removal of much of the static configuration state such as StateManager references to ObjectStore -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1839) blacktie pom.xml has hardcoded WildFly versions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1839?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1839: -------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/375 (was: https://github.com/jbosstm/narayana/pull/371) > blacktie pom.xml has hardcoded WildFly versions > ----------------------------------------------- > > Key: JBTM-1839 > URL: https://issues.jboss.org/browse/JBTM-1839 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M4 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-846) Allow multiple transaction managers with different configurations to operate in a single JVM

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-846?page=com.atlassian.jira.plugin.s... ] Mark Little commented on JBTM-846: ---------------------------------- Yes, I agree and identifying that state is much more than just looking at the static initialisers that we have. I probably know most of the codebase better than anybody but even then I'd be stretched to come up with a complete list off the top of my head. It will take time to scan each module and, potentially, each class. Furthermore, and maybe as a simplification, we need to decide if this is to apply to all components of TS (e.g., JTS, Web Services etc.) or just some (e.g., ArjunaCore). > Allow multiple transaction managers with different configurations to operate in a single JVM > -------------------------------------------------------------------------------------------- > > Key: JBTM-846 > URL: https://issues.jboss.org/browse/JBTM-846 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTA, JTS, Recovery, Transaction Core, XTS > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > This will require removal of much of the static configuration state such as StateManager references to ObjectStore -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1839) blacktie pom.xml has hardcoded WildFly versions

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1839?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1839: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/371 > blacktie pom.xml has hardcoded WildFly versions > ----------------------------------------------- > > Key: JBTM-1839 > URL: https://issues.jboss.org/browse/JBTM-1839 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M4 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1839) blacktie pom.xml has hardcoded WildFly versions

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1839: ----------------------------------- Summary: blacktie pom.xml has hardcoded WildFly versions Key: JBTM-1839 URL: https://issues.jboss.org/browse/JBTM-1839 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: BlackTie, Build System Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M4 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1823) Narayana fails to build on a codebase not checked out of SCM

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1823?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1823. --------------------------------- Resolution: Done Resolved for master here: https://github.com/jbosstm/narayana/commit/5762628e1005ba2d45e9f1d12527d0... And for 4.17 here: https://github.com/jbosstm/narayana/commit/8b4a4722c1f13b66ee07723936bced... > Narayana fails to build on a codebase not checked out of SCM > ------------------------------------------------------------ > > Key: JBTM-1823 > URL: https://issues.jboss.org/browse/JBTM-1823 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4, 4.17.5 > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M4, 4.17.6 > > > To reproduce: > * go Here: https://github.com/jbosstm/narayana/releases/4.17.4.Final > * Download and extract the zip > * run: './build.sh clean install -DskipTests' > * Observe: > {code} > [ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0:create (default) on project arjunacore: Cannot get the revision information from the scm repository : > [ERROR] Exception while executing SCM command. UnsupportedOperationException > [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/MojoExecutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :arjunacore > {code} > Alternatively, it works if you do this: > {code} > git clone git@github.com:jbosstm/narayana.git > git checkout 4.17.4.Final > ./build.sh clean install -DskipTests > {code} > It seems to be because the maven plugin is expecting the code to be checked out of SCM. We need to make the build tolerant of this scenario. > NOTE: it also happens for the 4.17.5.Final zip. -- 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, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2013