October 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1494) Produce performance figures to show performance improvements of Compensations over ACID

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1494?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1494: ------------------------------------- Absolutley. Whatever form the results from this work take, we will be sure to make that clear. > Produce performance figures to show performance improvements of Compensations over ACID > --------------------------------------------------------------------------------------- > > Key: JBTM-1494 > URL: https://issues.jboss.org/browse/JBTM-1494 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Performance Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 6.0.0.Final > > > As part of evangelising compensations, it would be useful to show performance comparisons for different classes of applications. > Ideally, these results should show that that, for certain classes of applications, the performance of a compensation-based transaction is a lot better than for an ACID transaction. -- 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, 8 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 closed JBTM-1788. ------------------------------- > 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, 8 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 resolved JBTM-1788. --------------------------------- Resolution: Cannot Reproduce Bug > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-622) Support for crash recovery of tx-inflow with multiple resource managers

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-622?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-622: ------------------------------- Comment: was deleted (was: Brain dump: Can we use the EIS name along with XID to guarantee uniqueness?) > Support for crash recovery of tx-inflow with multiple resource managers > ----------------------------------------------------------------------- > > Key: JBTM-622 > URL: https://issues.jboss.org/browse/JBTM-622 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA, Recovery, Transaction Core > Affects Versions: 4.2.3.CP06 > Reporter: Toshiya Kobayashi > Priority: Minor > Fix For: 6.0.0.Final > > > JCA tx-inflow spec allows the external EIS to provide the Xid for the inflowed transaction. The TM handling the inflowed (i.e. subordinate) transaction uses this Xid verbatim when talking to RMs. > In current implementation, each RM enlisted in the subordinate tx will see the same Xid as originally provided by the EIS. This screws recovery where multiple resources are involved, since a given Xid no longer belongs to exactly one RM, but may be shared by several. We can no longer return a single XAResource to drive the recovery for a given Xid. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1974) Qa tests needs the narayana build being done with parameter idlj-enabled to work

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1974?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1974: ----------------------------------- Assignee: (was: Tom Jenkinson) > Qa tests needs the narayana build being done with parameter idlj-enabled to work > -------------------------------------------------------------------------------- > > Key: JBTM-1974 > URL: https://issues.jboss.org/browse/JBTM-1974 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 5.0.0.M5 > Reporter: Ondřej Chaloupka > Priority: Minor > > When qa tests should be built without compilation errors the prior narayana build has to be run with parameter -Didlj-enabled=true > In the way like > ./build.sh clean install -Prelease -DskipTests -Didlj-enabled=true > This fact should be at least documented in REAME. > Plus it would be nice to avoid this dependence (or put idlj-enabled parameter which activates a profile as default). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-785) Document configuration of standalone client

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-785?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson commented on JBTM-785: ------------------------------------ Hi Paul, Is there any update on this one? Is it covered by any QS? Tom > Document configuration of standalone client > ------------------------------------------- > > Key: JBTM-785 > URL: https://issues.jboss.org/browse/JBTM-785 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, XTS > Affects Versions: 4.12.0 > Reporter: Andrew Dinn > > Need to explain how to set up standalone client so it can be deployed embedded without the need to expose completion initiator service endpoints. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-914) Fix WSTF SC007 Interop tests so they can be run on EAP5 and AS7/EAP6

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-914?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson commented on JBTM-914: ------------------------------------ Hi Paul, I don't think EAP5 support is something we should drive any longer, if you are happy this is resolved on EAP6 can we update the fixversions, subject etc and resolve and close this one? Thanks, Tom > Fix WSTF SC007 Interop tests so they can be run on EAP5 and AS7/EAP6 > -------------------------------------------------------------------- > > Key: JBTM-914 > URL: https://issues.jboss.org/browse/JBTM-914 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Affects Versions: 4.6.1.CP12, 5.0.0.M1 > Reporter: Andrew Dinn > Priority: Minor > > The WSTF interop test scenario 7 (WS-AT interop) was working on AS5 and the early EAP5 releases running on top of JBossWS-Native. However, it has not worked on more recent releases, apparently following changes made to accommodate the move to CXF as the default stack. Later releases fall foul of the presence of SoapAction declarations in the service WSDL. n.b. these changes appear to be the cause of the failure on EAP5 even though the XTS code only runs on WS-Native. Since WSTF is our only option for performing real interop with another vendor we need to get this test to work in, as a minimum, AS6/EAP6 and, preferably EAP5. This may require negotiating a change in the WSDL to remove the SoapAction declarations or it mayjst require workign out how to get the WS stack to accept their presence and still deliver the relevant messages. > Once the WSTF test is sorted out interop testing via the WSTF advertised endpoints shoud be resumed albeit probably manually. SInce SC007 adds nothgin to our QE coverage that is not already covered by the WSTX11 tests it is not critical to run this test for QE purposes. However, once we have a working interop version again it would be prudent to include an automated run of a local WSTF SC007 client against our own local server endpoint in normal XTS test runs so that we detect any brittleness introduced by the dev process as early as possible before we need to test interop via the public WSTF endpoints. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1695) Change the 'common' module to use the normal maven convention for source layout.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1695?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1695. ------------------------------- > Change the 'common' module to use the normal maven convention for source layout. > -------------------------------------------------------------------------------- > > Key: JBTM-1695 > URL: https://issues.jboss.org/browse/JBTM-1695 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.17.4 > Reporter: Weinan Li > Priority: Minor > > The common module doesn't use the normal maven convention for source layout. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1695) Change the 'common' module to use the normal maven convention for source layout.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1695?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1695. --------------------------------- Resolution: Won't Fix I don't believe this will be tackled so marking as won't fix > Change the 'common' module to use the normal maven convention for source layout. > -------------------------------------------------------------------------------- > > Key: JBTM-1695 > URL: https://issues.jboss.org/browse/JBTM-1695 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.17.4 > Reporter: Weinan Li > Priority: Minor > > The common module doesn't use the normal maven convention for source layout. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1695) Change the 'common' module to use the normal maven convention for source layout.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1695?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-1695: --------------------------------- > Change the 'common' module to use the normal maven convention for source layout. > -------------------------------------------------------------------------------- > > Key: JBTM-1695 > URL: https://issues.jboss.org/browse/JBTM-1695 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.17.4 > Reporter: Weinan Li > Priority: Minor > > The common module doesn't use the normal maven convention for source layout. -- 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, 8 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 October 2013