July 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1860) Please document AtomicAction and TransactionStatusManager scanner.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1860: -------------------------------- Component/s: Documentation (was: Transaction Core) > Please document AtomicAction and TransactionStatusManager scanner. > ------------------------------------------------------------------ > > Key: JBTM-1860 > URL: https://issues.jboss.org/browse/JBTM-1860 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Environment: JBoss EAP 5.x and 6.x > Reporter: Tom Ross > Assignee: Tom Ross > > JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them. > Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1860) Please document AtomicAction and TransactionStatusManager scanner.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1860: ----------------------------------- Assignee: Tom Jenkinson (was: Tom Ross) > Please document AtomicAction and TransactionStatusManager scanner. > ------------------------------------------------------------------ > > Key: JBTM-1860 > URL: https://issues.jboss.org/browse/JBTM-1860 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Environment: JBoss EAP 5.x and 6.x > Reporter: Tom Ross > Assignee: Tom Jenkinson > > JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them. > Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1789) Simplify deploy plugin configuration and don't deploy uber (shaded) jars

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1789?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1789: -------------------------------- Fix Version/s: 5.next > Simplify deploy plugin configuration and don't deploy uber (shaded) jars > ------------------------------------------------------------------------ > > Key: JBTM-1789 > URL: https://issues.jboss.org/browse/JBTM-1789 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Reporter: Paul Gier > Assignee: Paul Gier > Fix For: 5.next > > > There is currently configuration of the maven deploy plugin in several modules to either deploy or not deploy artifacts and poms to the Maven repo. The configuration could be simplified using properties, and the uber jars (generated by the shade plugin) should not be deployed to the Maven repository. > Here is the current deployment status and proposed for the modules. > ||Module Name||Current Deployment||Proposed|| > | Narayana: all | deployed | deployed | > | Narayana: common | deployed | deployed | > | Narayana: Arjunacore | deployed | deployed | > | Narayana: ArjunaCore arjuna | deployed | deployed | > | Narayana: ArjunaCore txoj | deployed | deployed | > | Narayana: ArjunaCore arjunacore | deployed | {color:red} skipped {color} | > | Narayana: ArjunaJTA | deployed | deployed | > | Narayana: ArjunaJTA jta | deployed | deployed | > | Narayana: ArjunaJTA cdi | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTA jdbc | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTA narayana-jta | deployed | {color:red} skipped {color} | > | Narayana: XTS | deployed | deployed | > | Narayana: XTS byteman_support | deployed | deployed | > | Narayana: XTS WSAS | skipped | skipped | > | Narayana: XTS WSAS xts-test-servlet | skipped | skipped | > | Narayana: XTS WS-C | skipped | skipped | > | Narayana: XTS WSCF | skipped | skipped | > | Narayana: XTS WS-T | skipped | skipped | > | Narayana: XTS WSTX | skipped | skipped | > | Narayana: XTS recovery | skipped | skipped | > | Narayana: XTS bridge | skipped | skipped | > | Narayana: XTS sar | skipped | skipped | > | Narayana: XTS jbossxts | deployed | deployed | > | Narayana: XTS localjunit | skipped | skipped | > | Narayana: XTS localjunit unit | skipped | skipped | > | Narayana: XTS WSTX11-interop | skipped | skipped | > | Narayana: XTS WSTFSC07-interop | skipped | skipped | > | Narayana: XTS localjunit xtstest | skipped | skipped | > | Narayana: XTS localjunit crash-recovery-tests | skipped | skipped | > | Narayana: ArjunaJTS | deployed | deployed | > | Narayana: ArjunaJTS idl | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS idl jacorb | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS orbportability | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS jts | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS jtax | skipped | {color:red} deployed {color} | > | Narayana: ArjuntaJTS narayana-jts-jacorb | deployed | {color:red} skipped {color} | > | Narayana: ArjunaJTS integration | deployed | deployed | > | Narayana: rest-tx | deployed | deployed | > | Narayana: rest-tx util | deployed | deployed | > | Narayana: rest-tx tx (RESTful API for Atomic Transactions) | deployed | deployed | > | Narayana: rest-tx webservice | skipped | skipped | > | Narayana: rest-tx integration | deployed | deployed | > | Narayana: txbridge | deployed | deployed | > | Narayana: fileio | deployed | deployed | > | Narayana: STM | skipped | skipped | > | Narayana: txframework | deployed | deployed | > | Narayana: narayana-full | skipped | skipped | > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1789) Simplify deploy plugin configuration and don't deploy uber (shaded) jars

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1789?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1789: ----------------------------------- Assignee: Tom Jenkinson (was: Paul Gier) > Simplify deploy plugin configuration and don't deploy uber (shaded) jars > ------------------------------------------------------------------------ > > Key: JBTM-1789 > URL: https://issues.jboss.org/browse/JBTM-1789 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Reporter: Paul Gier > Assignee: Tom Jenkinson > Fix For: 5.next > > > There is currently configuration of the maven deploy plugin in several modules to either deploy or not deploy artifacts and poms to the Maven repo. The configuration could be simplified using properties, and the uber jars (generated by the shade plugin) should not be deployed to the Maven repository. > Here is the current deployment status and proposed for the modules. > ||Module Name||Current Deployment||Proposed|| > | Narayana: all | deployed | deployed | > | Narayana: common | deployed | deployed | > | Narayana: Arjunacore | deployed | deployed | > | Narayana: ArjunaCore arjuna | deployed | deployed | > | Narayana: ArjunaCore txoj | deployed | deployed | > | Narayana: ArjunaCore arjunacore | deployed | {color:red} skipped {color} | > | Narayana: ArjunaJTA | deployed | deployed | > | Narayana: ArjunaJTA jta | deployed | deployed | > | Narayana: ArjunaJTA cdi | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTA jdbc | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTA narayana-jta | deployed | {color:red} skipped {color} | > | Narayana: XTS | deployed | deployed | > | Narayana: XTS byteman_support | deployed | deployed | > | Narayana: XTS WSAS | skipped | skipped | > | Narayana: XTS WSAS xts-test-servlet | skipped | skipped | > | Narayana: XTS WS-C | skipped | skipped | > | Narayana: XTS WSCF | skipped | skipped | > | Narayana: XTS WS-T | skipped | skipped | > | Narayana: XTS WSTX | skipped | skipped | > | Narayana: XTS recovery | skipped | skipped | > | Narayana: XTS bridge | skipped | skipped | > | Narayana: XTS sar | skipped | skipped | > | Narayana: XTS jbossxts | deployed | deployed | > | Narayana: XTS localjunit | skipped | skipped | > | Narayana: XTS localjunit unit | skipped | skipped | > | Narayana: XTS WSTX11-interop | skipped | skipped | > | Narayana: XTS WSTFSC07-interop | skipped | skipped | > | Narayana: XTS localjunit xtstest | skipped | skipped | > | Narayana: XTS localjunit crash-recovery-tests | skipped | skipped | > | Narayana: ArjunaJTS | deployed | deployed | > | Narayana: ArjunaJTS idl | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS idl jacorb | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS orbportability | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS jts | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS jtax | skipped | {color:red} deployed {color} | > | Narayana: ArjuntaJTS narayana-jts-jacorb | deployed | {color:red} skipped {color} | > | Narayana: ArjunaJTS integration | deployed | deployed | > | Narayana: rest-tx | deployed | deployed | > | Narayana: rest-tx util | deployed | deployed | > | Narayana: rest-tx tx (RESTful API for Atomic Transactions) | deployed | deployed | > | Narayana: rest-tx webservice | skipped | skipped | > | Narayana: rest-tx integration | deployed | deployed | > | Narayana: txbridge | deployed | deployed | > | Narayana: fileio | deployed | deployed | > | Narayana: STM | skipped | skipped | > | Narayana: txframework | deployed | deployed | > | Narayana: narayana-full | skipped | skipped | > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1718) Resolve the ParticipantCompletion race condition

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1718?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1718: -------------------------------- Fix Version/s: (was: 6.later) > Resolve the ParticipantCompletion race condition > ------------------------------------------------ > > Key: JBTM-1718 > URL: https://issues.jboss.org/browse/JBTM-1718 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Paul Robinson > > This issue is documented here: JBTM-1429 > In the documentation for JBTM-1429, we state that this issue is unlikely to happen in a distributed environment. This is true, however, the Compensations API is designed to work local-only as well as distributed over WS-BA. Therefore it is much more likely to happen in a production environment. > Therefore we need to remove this race condition. It can be done in a proprietary mannor as we are not interoperating with another implementation ion local-only mode. When distributing the transaction we fall back to the standard protocol that is susceptible to the race condition. However, as we stated in the docs, this condition is unlikely to manifest in a distributed environment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1718) Resolve the ParticipantCompletion race condition

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1718?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1718: ----------------------------------- Assignee: (was: Gytis Trikleris) > Resolve the ParticipantCompletion race condition > ------------------------------------------------ > > Key: JBTM-1718 > URL: https://issues.jboss.org/browse/JBTM-1718 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Paul Robinson > > This issue is documented here: JBTM-1429 > In the documentation for JBTM-1429, we state that this issue is unlikely to happen in a distributed environment. This is true, however, the Compensations API is designed to work local-only as well as distributed over WS-BA. Therefore it is much more likely to happen in a production environment. > Therefore we need to remove this race condition. It can be done in a proprietary mannor as we are not interoperating with another implementation ion local-only mode. When distributing the transaction we fall back to the standard protocol that is susceptible to the race condition. However, as we stated in the docs, this condition is unlikely to manifest in a distributed environment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1688) TXBridge doesn't support "loops" or "diamonds"

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1688?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1688: ----------------------------------- Assignee: (was: Gytis Trikleris) > TXBridge doesn't support "loops" or "diamonds" > ---------------------------------------------- > > Key: JBTM-1688 > URL: https://issues.jboss.org/browse/JBTM-1688 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge, XTS > Reporter: Paul Robinson > > See here: http://docs.jboss.org/jbosstm/5.0.0.M2/guides/txbridge_guide/index.html#d... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1639?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1639: -------------------------------- Fix Version/s: 5.next (was: 6.later) > 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 > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > 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 was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1688) TXBridge doesn't support "loops" or "diamonds"

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1688?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1688: -------------------------------- Fix Version/s: (was: 6.later) > TXBridge doesn't support "loops" or "diamonds" > ---------------------------------------------- > > Key: JBTM-1688 > URL: https://issues.jboss.org/browse/JBTM-1688 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > > See here: http://docs.jboss.org/jbosstm/5.0.0.M2/guides/txbridge_guide/index.html#d... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1523) Try to have XTS enabled in standalone-full.xml

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1523?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1523. ------------------------------- Fix Version/s: (was: 6.later) Resolution: Won't Fix > Try to have XTS enabled in standalone-full.xml > ---------------------------------------------- > > Key: JBTM-1523 > URL: https://issues.jboss.org/browse/JBTM-1523 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration, XTS > Reporter: Paul Robinson > > The problem is that XTS currently increases boot time by about 50%. Therefore it has to live in its own configuration. > If we can reduce this boot cost, we may be able to get it included in standalone-full.xml. > I think the main problem is the time it takes to register all the XTS Web Service endpoints. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 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 July 2015