June 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1788) TXBridge quick start example does not build

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1788?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1788: ----------------------------------- Description: The TXBridge example does not build. Build fails with error: {noformat} [ERROR] Failed to execute goal on project jbosstxbridge-demo-service: Could not resolve dependencies for project org.jboss.jbossts:jbosstxbridge-demo-service:jar:4.17.5.Final-SNAPSHOT: The following artifacts could not be resolved: org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT, org.jboss.jbossts.jta:narayana-jta:jar:4.17.5.Final-SNAPSHOT, org.jboss.jbossts:jbosstxbridge:jar:4.17.5.Final-SNAPSHOT: Failure to find org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public-jboss/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1] [ERROR] {noformat} - The README file is out of date and needs updating. The README file also does not explain what the demo supposed to do and what to expect when the application is run. - The demo/README.md says to deploy a jar but it is actually a war that should be deployed - The demo offers an option of running the application with transaction type JTA. That option does not seem to work since it's missing a dependency. There is no explanation as what to do to get it working. - The demo references artifacts built by the XTS demo so the README should state that the XTS demo must be built first. was: The TXBridge example does not build. Build fails with error: {noformat} [ERROR] Failed to execute goal on project jbosstxbridge-demo-service: Could not resolve dependencies for project org.jboss.jbossts:jbosstxbridge-demo-service:jar:4.17.5.Final-SNAPSHOT: The following artifacts could not be resolved: org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT, org.jboss.jbossts.jta:narayana-jta:jar:4.17.5.Final-SNAPSHOT, org.jboss.jbossts:jbosstxbridge:jar:4.17.5.Final-SNAPSHOT: Failure to find org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public-jboss/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1] [ERROR] {noformat} - The README file is out of date and needs updating. The README file also does not explain what the demo supposed to do and what to expect when the application is run. - The demo offers an option of running the application with transaction type JTA. That option does not seem to work since it's missing a dependency. There is no explanation as what to do to get it working. > TXBridge quick start example does not build > ------------------------------------------- > > Key: JBTM-1788 > URL: https://issues.jboss.org/browse/JBTM-1788 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, TxBridge > Affects Versions: 4.17.4 > Environment: JBoss EAP 6.1 > Reporter: Tom Ross > Assignee: Paul Robinson > > The TXBridge example does not build. Build fails with error: > {noformat} > [ERROR] Failed to execute goal on project jbosstxbridge-demo-service: Could not resolve dependencies for project org.jboss.jbossts:jbosstxbridge-demo-service:jar:4.17.5.Final-SNAPSHOT: The following artifacts could not be resolved: org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT, org.jboss.jbossts.jta:narayana-jta:jar:4.17.5.Final-SNAPSHOT, org.jboss.jbossts:jbosstxbridge:jar:4.17.5.Final-SNAPSHOT: Failure to find org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public-jboss/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1] > [ERROR] > {noformat} > - The README file is out of date and needs updating. The README file also does not explain what the demo supposed to do and what to expect when the application is run. > - The demo/README.md says to deploy a jar but it is actually a war that should be deployed > > - The demo offers an option of running the application with transaction type JTA. That option does not seem to work since it's missing a dependency. There is no explanation as what to do to get it working. > - The demo references artifacts built by the XTS demo so the README should state that the XTS demo must be built first. > -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1788) TXBridge quick start example does not build

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1788?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1788: -------------------------------- Assignee: Paul Robinson (was: Tom Jenkinson) > TXBridge quick start example does not build > ------------------------------------------- > > Key: JBTM-1788 > URL: https://issues.jboss.org/browse/JBTM-1788 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator > Affects Versions: 4.17.4 > Environment: JBoss EAP 6.1 > Reporter: Tom Ross > Assignee: Paul Robinson > > The TXBridge example does not build. Build fails with error: > {noformat} > [ERROR] Failed to execute goal on project jbosstxbridge-demo-service: Could not resolve dependencies for project org.jboss.jbossts:jbosstxbridge-demo-service:jar:4.17.5.Final-SNAPSHOT: The following artifacts could not be resolved: org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT, org.jboss.jbossts.jta:narayana-jta:jar:4.17.5.Final-SNAPSHOT, org.jboss.jbossts:jbosstxbridge:jar:4.17.5.Final-SNAPSHOT: Failure to find org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public-jboss/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1] > [ERROR] > {noformat} > - The README file is out of date and needs updating. The README file also does not explain what the demo supposed to do and what to expect when the application is run. > > - The demo offers an option of running the application with transaction type JTA. That option does not seem to work since it's missing a dependency. There is no explanation as what to do to get it working. > -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1788) TXBridge quick start example does not build

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1788?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1788: -------------------------------- Component/s: TxBridge > TXBridge quick start example does not build > ------------------------------------------- > > Key: JBTM-1788 > URL: https://issues.jboss.org/browse/JBTM-1788 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, TxBridge > Affects Versions: 4.17.4 > Environment: JBoss EAP 6.1 > Reporter: Tom Ross > Assignee: Paul Robinson > > The TXBridge example does not build. Build fails with error: > {noformat} > [ERROR] Failed to execute goal on project jbosstxbridge-demo-service: Could not resolve dependencies for project org.jboss.jbossts:jbosstxbridge-demo-service:jar:4.17.5.Final-SNAPSHOT: The following artifacts could not be resolved: org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT, org.jboss.jbossts.jta:narayana-jta:jar:4.17.5.Final-SNAPSHOT, org.jboss.jbossts:jbosstxbridge:jar:4.17.5.Final-SNAPSHOT: Failure to find org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public-jboss/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1] > [ERROR] > {noformat} > - The README file is out of date and needs updating. The README file also does not explain what the demo supposed to do and what to expect when the application is run. > > - The demo offers an option of running the application with transaction type JTA. That option does not seem to work since it's missing a dependency. There is no explanation as what to do to get it working. > -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1788) TXBridge quick start example does not build

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1788?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1788: ------------------------------------- Hi Tom, Those artifacts will not exist unless you are using a tag (when they will then be downloaded from maven central) or unless you have built the corresponding version of JBoss Transactions before, that part of the issue is therefore not a bug in my mind. To test this, please can you try to use the 4.17.4.Final tag: https://github.com/jbosstm/narayana/tree/4.17.4.Final Note, there was a bug (JBTM-1784) this quickstart which is resolved but will affect the 4.17.4.Final tag. The Jira has a workaround documented. That said, the second two parts do need resolving should they be verified by Paul. Thanks, Tom > TXBridge quick start example does not build > ------------------------------------------- > > Key: JBTM-1788 > URL: https://issues.jboss.org/browse/JBTM-1788 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator > Affects Versions: 4.17.4 > Environment: JBoss EAP 6.1 > Reporter: Tom Ross > Assignee: Tom Jenkinson > > The TXBridge example does not build. Build fails with error: > {noformat} > [ERROR] Failed to execute goal on project jbosstxbridge-demo-service: Could not resolve dependencies for project org.jboss.jbossts:jbosstxbridge-demo-service:jar:4.17.5.Final-SNAPSHOT: The following artifacts could not be resolved: org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT, org.jboss.jbossts.jta:narayana-jta:jar:4.17.5.Final-SNAPSHOT, org.jboss.jbossts:jbosstxbridge:jar:4.17.5.Final-SNAPSHOT: Failure to find org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public-jboss/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1] > [ERROR] > {noformat} > - The README file is out of date and needs updating. The README file also does not explain what the demo supposed to do and what to expect when the application is run. > > - The demo offers an option of running the application with transaction type JTA. That option does not seem to work since it's missing a dependency. There is no explanation as what to do to get it working. > -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1784) TXBridge quickstart contains a reference to an artifact that should be brought in via its corresponding uber jar

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1784?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1784: -------------------------------- Workaround Description: Check out tag: git clone https://github.com/jbosstm/quickstart.git git checkout 4.17.4 find . -name \pom.xml -exec sed -i "s/>jta</>narayana-jta</g" {} \; > TXBridge quickstart contains a reference to an artifact that should be brought in via its corresponding uber jar > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1784 > URL: https://issues.jboss.org/browse/JBTM-1784 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation, TxBridge > Affects Versions: 4.17.4 > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 4.17.5 > > > TXBridge/demo/service/pom.xml and TXBridge/demo/service/pom.xml both reference: > <groupId>org.jboss.jbossts.jta</groupId> > <artifactId>jta</artifactId> > When they should reference the uber jar: > <artifactId>narayana-jta</artifactId> > The uber jar is uploaded to maven central whereas the constituent jars are intermediary build artifacts. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1784) TXBridge quickstart contains a reference to an artifact that should be brought in via its corresponding uber jar

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1784?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1784: -------------------------------- Workaround Description: git clone https://github.com/jbosstm/quickstart.git git checkout 4.17.4 find . -name \pom.xml -exec sed -i "s/>jta</>narayana-jta</g" {} \; was: Check out tag: git clone https://github.com/jbosstm/quickstart.git git checkout 4.17.4 find . -name \pom.xml -exec sed -i "s/>jta</>narayana-jta</g" {} \; > TXBridge quickstart contains a reference to an artifact that should be brought in via its corresponding uber jar > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1784 > URL: https://issues.jboss.org/browse/JBTM-1784 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation, TxBridge > Affects Versions: 4.17.4 > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 4.17.5 > > > TXBridge/demo/service/pom.xml and TXBridge/demo/service/pom.xml both reference: > <groupId>org.jboss.jbossts.jta</groupId> > <artifactId>jta</artifactId> > When they should reference the uber jar: > <artifactId>narayana-jta</artifactId> > The uber jar is uploaded to maven central whereas the constituent jars are intermediary build artifacts. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1784) TXBridge quickstart contains a reference to an artifact that should be brought in via its corresponding uber jar

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1784?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1784: -------------------------------- Affects Version/s: 4.17.4 > TXBridge quickstart contains a reference to an artifact that should be brought in via its corresponding uber jar > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1784 > URL: https://issues.jboss.org/browse/JBTM-1784 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation, TxBridge > Affects Versions: 4.17.4 > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 4.17.5 > > > TXBridge/demo/service/pom.xml and TXBridge/demo/service/pom.xml both reference: > <groupId>org.jboss.jbossts.jta</groupId> > <artifactId>jta</artifactId> > When they should reference the uber jar: > <artifactId>narayana-jta</artifactId> > The uber jar is uploaded to maven central whereas the constituent jars are intermediary build artifacts. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1788) TXBridge quick start example does not build

by Tom Ross (JIRA)

Tom Ross created JBTM-1788: ------------------------------ Summary: TXBridge quick start example does not build Key: JBTM-1788 URL: https://issues.jboss.org/browse/JBTM-1788 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Demonstrator Affects Versions: 4.17.4 Environment: JBoss EAP 6.1 Reporter: Tom Ross Assignee: Tom Jenkinson The TXBridge example does not build. Build fails with error: {noformat} [ERROR] Failed to execute goal on project jbosstxbridge-demo-service: Could not resolve dependencies for project org.jboss.jbossts:jbosstxbridge-demo-service:jar:4.17.5.Final-SNAPSHOT: The following artifacts could not be resolved: org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT, org.jboss.jbossts.jta:narayana-jta:jar:4.17.5.Final-SNAPSHOT, org.jboss.jbossts:jbosstxbridge:jar:4.17.5.Final-SNAPSHOT: Failure to find org.jboss.jbossts.xts:jbossxts:jar:api:4.17.5.Final-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public-jboss/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1] [ERROR] {noformat} - The README file is out of date and needs updating. The README file also does not explain what the demo supposed to do and what to expect when the application is run. - The demo offers an option of running the application with transaction type JTA. That option does not seem to work since it's missing a dependency. There is no explanation as what to do to get it working. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1340) BeanPopulator overhead needs looking into

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1340?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1340: ------------------------------------- Hi Mark, Please can you upload the test you were using and the name of the tool that outputted the profiling information? We can look at tuning TxStats, I am thinking a listener pattern might help? Before that though, the test and profiler settings would be useful. Thanks, Tom > BeanPopulator overhead needs looking into > ----------------------------------------- > > Key: JBTM-1340 > URL: https://issues.jboss.org/browse/JBTM-1340 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Common > Affects Versions: 4.17.2 > Environment: Mac OS 10.7 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.0.0.M4 > > > During profiling, BeanPopulator can represent a 7% overhead. It may not seem like a lot, but for something as relatively simple as what BeanPopulator should be doing, it seems to be quite a bit. > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.coordinator.TxStats.enabled > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.common.arjPropertyManager.getCoordinatorEnvironmentBean > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance > 2.5% - 1,587 ms - 10,000 inv. java.lang.StringBuilder.<init> > 2.3% - 1,507 ms - 10,000 inv. java.lang.StringBuilder.toString > 0.0% - 320 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.containsKey > 0.0% - 61 µs - 10,000 inv. java.lang.Class.getName > 0.0% - 25 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.get -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1278) Additional debug information required for transaction's Xid with Oracle

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1278?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1278: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Additional debug information required for transaction's Xid with Oracle > ----------------------------------------------------------------------- > > Key: JBTM-1278 > URL: https://issues.jboss.org/browse/JBTM-1278 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.16.1 > Environment: Jboss EAP 5.x > Reporter: Tom Ross > Assignee: Tom Jenkinson > Fix For: 5.0.0.M4 > > > It seems that Oracle is returning different XIDs each time (with the same content) which makes it difficult to debug if the same XID is in more than one scan. Additional debug information is required in Xid to make debugging easier. -- 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

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2013