August 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1871) Automatically add the "org.jboss.xts" dependency for XTS applications

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1871?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1871: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Automatically add the "org.jboss.xts" dependency for XTS applications > --------------------------------------------------------------------- > > Key: JBTM-1871 > URL: https://issues.jboss.org/browse/JBTM-1871 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: TxBridge, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 6.0.0.Final > > > At deployment time we should automatically add the org.jboss.xts dependency for applications that need it. > We should be able to detect deployments that use XTS annotations (i.e those provided by the Compensations API) through Jandex. I'm not sure how we would detect those that don't use annotations; something to investigate. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1871) Automatically add the "org.jboss.xts" dependency for XTS applications

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1871?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1871: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 6.0.0.Final) > Automatically add the "org.jboss.xts" dependency for XTS applications > --------------------------------------------------------------------- > > Key: JBTM-1871 > URL: https://issues.jboss.org/browse/JBTM-1871 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: TxBridge, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M5 > > > At deployment time we should automatically add the org.jboss.xts dependency for applications that need it. > We should be able to detect deployments that use XTS annotations (i.e those provided by the Compensations API) through Jandex. I'm not sure how we would detect those that don't use annotations; something to investigate. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1854) Hornetq failures in CI test suite

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1854: ----------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.M5) > Hornetq failures in CI test suite > --------------------------------- > > Key: JBTM-1854 > URL: https://issues.jboss.org/browse/JBTM-1854 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0.Final > > Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz > > > The first CI job link includes: > CurrentTests01_Test036 > jtsremote JTSRemote_ImplicitPropagationTest > crashrecovery02_2 CrashRecovery02_2 - all of them > crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10 > crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them) > The second CI job link includes: > JTSRemote_ImplicitPropagationTest failure > CrashRecovery02_2_Test46 hang -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1681) EJB support for Compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1681?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1681: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > EJB support for Compensations API > --------------------------------- > > Key: JBTM-1681 > URL: https://issues.jboss.org/browse/JBTM-1681 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 6.0.0.Final > > > We need to be able to use all the annotations on EJBs and also allow allow the handler implementations to be EJBs. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1679) Make @CompensationScoped beans available during recovery

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1679?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1679: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Make @CompensationScoped beans available during recovery > -------------------------------------------------------- > > Key: JBTM-1679 > URL: https://issues.jboss.org/browse/JBTM-1679 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 6.0.0.Final > > -- 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, 9 months

1
0
0 / 0

[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 updated JBTM-1494: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-846) Allow transactional MSC and WildFly EJB container to operate with different configurations for transaction/recovery manager in a single JVM

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-846?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-846: ------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Allow transactional MSC and WildFly EJB container to operate with different configurations for transaction/recovery manager 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: 6.0.0.Final > > > ** This Jira is a work in progress - I (Paul) will update the details here once the requirements in https://community.jboss.org/message/828391 are clarified. ** > The use case provided for this is to run a separate transaction/recovery manager for Transactional MSC to the one that WildFly is using for its (JTA/JTS) EJB container. > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1639) Improve XTS Api for looking up Recovery Manager to prevent developer from poling

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1639?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1639: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Improve XTS Api for looking up Recovery Manager to prevent developer from poling > -------------------------------------------------------------------------------- > > Key: JBTM-1639 > URL: https://issues.jboss.org/browse/JBTM-1639 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 6.0.0.Final > > > Currently the developer needs to poll for the RecoveryManager as it's possible that the application can be deployed before the XTS subsystem has finished startup. > This issue was worked around in JBTM-1522 and in the TXBridge tests, by having the application poll until the RM was not null. > Two possible solutions: > Have a blocking call to XTSATRecoveryManager.getRecoveryManager() that doesn't return until there is an RM available. if we use the existing java method, we need to analyse all usages to make sure returning null is not a valid outcome. > Another solution is to find out how to delay the application's initialisation until after XTS has started. This puts the burden on the application developer to implement, but requires no changes to the XTS code. See JBTM-1522 for alternative mechanisms for initialising the application. I tried three and none of them fired after the server had booted. > To Reproduce > Put breakpoints on: > Application's usage of: XTSATRecoveryManager.getRecoveryManager(); //Stop all threads > XTSATRecoveryManager.setRecoveryManager() // stop on Thread only > Copy your application to the deploy directory (xtstest.war is a good choice). Now start the server with debugging enabled (suspend=y). To reproduce this you will see the XTSATRecoveryManager.setRecoveryManager() BP fire, and then shortly after the XTSATRecoveryManager.getRecoveryManager() BP will fire. Allow the getRecoveryManager to continue and you will notice it is null. Fix this problem, and the getRecoveryManager will wait until the setRecoveryManager is complete and thus always return a non-null RM. > Once this is fixed, find all occurrence of the polling work-around and have them use the solution to this issue. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1359) HA Recovery Manager

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1359?page=com.atlassian.jira.plugin.... ] Work on JBTM-1359 stopped by Michael Musgrove. > HA Recovery Manager > ------------------- > > Key: JBTM-1359 > URL: https://issues.jboss.org/browse/JBTM-1359 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA, JTS, Recovery, XTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 6.0.0.Final > > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > JTA should work, but must consider JTS and XTS too (encoded IP addresses in log records) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1190) TXFramework prefixes @Path value to TX id

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1190?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1190. --------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) Resolution: Won't Fix Applies to AT support in REST-AT which is being dropped in favour of JTA bridging. > TXFramework prefixes @Path value to TX id > ----------------------------------------- > > Key: JBTM-1190 > URL: https://issues.jboss.org/browse/JBTM-1190 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > For example, a service with @Path("/restaurant") results in a terminator url of: "http://localhost:8080/test/restaurant0_ffffc0a80068_2a160422_4fe20541_155...". Notice the missing '/' between restaurant and the txid. -- 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, 9 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 August 2013