September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1042) GC: No relationship between generic parameter and method argument (GC_UNRELATED_TYPES)

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1042?page=com.atlassian.jira.plugin.... ] Paul Robinson reassigned JBTM-1042: ----------------------------------- Assignee: Paul Robinson (was: Amos Feng) > GC: No relationship between generic parameter and method argument (GC_UNRELATED_TYPES) > -------------------------------------------------------------------------------------- > > Key: JBTM-1042 > URL: https://issues.jboss.org/browse/JBTM-1042 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Amos Feng > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > 1.XTS/recovery > org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple Line 132 > com.arjuna.ats.arjuna.common.Uid is incompatible with expected argument type String in org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple.isParticipantPresent(Uid) > 2.XTS/recovery > org.jboss.jbossts.xts.recovery.participant.ba.XTSBARecoveryManagerImple Line 128 > com.arjuna.ats.arjuna.common.Uid is incompatible with expected argument type String in org.jboss.jbossts.xts.recovery.participant.ba.XTSBARecoveryManagerImple.isParticipantPresent(Uid) -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1783) no matching injection point in ArjunaCore/arjuna/test/byteman-scripts/reaper.txt

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1783?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1783: ----------------------------------- Assignee: Tom Jenkinson (was: Amos Feng) > no matching injection point in ArjunaCore/arjuna/test/byteman-scripts/reaper.txt > --------------------------------------------------------------------------------- > > Key: JBTM-1783 > URL: https://issues.jboss.org/browse/JBTM-1783 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Amos Feng > Assignee: Tom Jenkinson > Fix For: 5.0.0.M5 > > Original Estimate: 3 days > Time Spent: 2 hours > Remaining Estimate: 2 days, 6 hours > > {noformat} > [INFO] Checking 3 byteman scripts in /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes > [WARNING] WARNING : Warning type checking rule "pause transaction reaper 3" loaded from /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes/reaper.txt line 65 against method check() void > org.jboss.byteman.rule.exception.TypeWarningException: no matching injection point for method check() void > [WARNING] WARNING : Warning type checking rule "pause transaction reaper 3" loaded from /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes/reaper.txt line 65 > org.jboss.byteman.rule.exception.TypeWarningException: failed to find any matching trigger method in class com.arjuna.ats.arjuna.coordinator.TransactionReaper > [WARNING] WARNING : Warning type checking rule "pause transaction reaper 4" loaded from /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes/reaper.txt line 79 against method check() void > org.jboss.byteman.rule.exception.TypeWarningException: no matching injection point for method check() void > [WARNING] WARNING : Warning type checking rule "pause transaction reaper 4" loaded from /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes/reaper.txt line 79 > org.jboss.byteman.rule.exception.TypeWarningException: failed to find any matching trigger method in class com.arjuna.ats.arjuna.coordinator.TransactionReaper > [WARNING] WARNING : Warning type checking rule "pause transaction reaper worker 4" loaded from /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes/reaper.txt line 186 against method doCancellations() void > org.jboss.byteman.rule.exception.TypeWarningException: no matching injection point for method doCancellations() void > [WARNING] WARNING : Warning type checking rule "pause transaction reaper worker 4" loaded from /home/zhfeng/src/zhfeng/narayana/ArjunaCore/arjuna/target/test-classes/reaper.txt line 186 > org.jboss.byteman.rule.exception.TypeWarningException: failed to find any matching trigger method in class com.arjuna.ats.arjuna.coordinator.TransactionReaper > {noformat} -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1917) XTS*RecoveryManager.getRecoveryManager() can return null if application deployed before XTS starts

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1917?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1917: ------------------------------------- Lets poll for it in the getRecoveryManager() call for now (with a timeout) > XTS*RecoveryManager.getRecoveryManager() can return null if application deployed before XTS starts > -------------------------------------------------------------------------------------------------- > > Key: JBTM-1917 > URL: https://issues.jboss.org/browse/JBTM-1917 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M5 > > > The problem is that there is currently no way of specifying that an application depends on XTS. Therefore it's possible that when the server starts, that the application can be deployed before XTS is started, thus a call to XTSBARecoveryManager.getRecoveryManager() or XTSATRecoveryManager.getRecoveryManager() will return null. > The workaround is to poll for the RecoveryManager until it is not null. > The fix is to have the RecoveryManager injected into the application via a Deployment Unit Processor that has a dependency on the XTS service. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1863) RESTAT Integration API does not allow participants to leave a transaction early

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1863?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1863: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.M5) > RESTAT Integration API does not allow participants to leave a transaction early > ------------------------------------------------------------------------------- > > Key: JBTM-1863 > URL: https://issues.jboss.org/browse/JBTM-1863 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 6.0.0.Final > > > The restat integration API class org.jboss. narayana.rest.integration.api.ParticipantsManager interface does not allow participants to leave the transaction early (in the spec a participant can DELETE the participant-recovery URI to notify the coordinator that it is leaving the transaction early). > Question: The reportHeuristic method allows participants to leave the transaction after the termination protocol has started. To keep the interface simple would it be sensible to replace reportHeuristic with something that covered leaving a transaction at any time or would that be confusing normal operations with error conditions? If so then maybe just the converse of enlist? -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1864) Implement volatile participant interface for REST-AT integration API

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1864?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1864: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.M5) > Implement volatile participant interface for REST-AT integration API > -------------------------------------------------------------------- > > Key: JBTM-1864 > URL: https://issues.jboss.org/browse/JBTM-1864 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1721) REST-AT participant support framework should support synchronizations

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1721?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1721. --------------------------------- Resolution: Done > REST-AT participant support framework should support synchronizations > --------------------------------------------------------------------- > > Key: JBTM-1721 > URL: https://issues.jboss.org/browse/JBTM-1721 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: REST > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5 > > > JBTM-1365 introduced an interface for simplifying participant registration into a REST-AT transaction by providing a callback for prepare/commit/rollback support. Please can we also have a similar mechanism for synchronizations. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1699) Changes to the transaction SPI

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1699?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1699: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.M5) > Changes to the transaction SPI > ------------------------------ > > Key: JBTM-1699 > URL: https://issues.jboss.org/browse/JBTM-1699 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 6.0.0.Final > > Original Estimate: 1 week, 3 days > Remaining Estimate: 1 week, 3 days > > wildfly is using a number of our internal com.arjuna interfaces which we would like to resolve by providing the same functionality in the transactions SPI. > Additionally the current SPI contains a number of unused classes which need removing. > I have created https://github.com/jbosstm/jboss-transaction-spi to manage the changes. To avoid any potential confusion and to make it clear who is responsible for the SPI we will be changing the package names. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1558) Prune redundant code from jboss-transaction-spi

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1558?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1558: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.M5) > Prune redundant code from jboss-transaction-spi > ----------------------------------------------- > > Key: JBTM-1558 > URL: https://issues.jboss.org/browse/JBTM-1558 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 6.0.0.Final > > Attachments: as8.zip, ij-tx-spi.txt > > > We can use jboss-transaction-spi to get started > There is much old code in jboss-transaction-spi that does not get used in AS7 and does not apply to Narayana. > Run tattletale over AS8, identify redundant methods and add new SPI functions if necessary -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1932) Consider using the same jboss-parent as other JBoss community projects such as WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1932?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1932: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.M5) > Consider using the same jboss-parent as other JBoss community projects such as WildFly > -------------------------------------------------------------------------------------- > > Key: JBTM-1932 > URL: https://issues.jboss.org/browse/JBTM-1932 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0.Final > > > It would standardise the versions of the build plugins we use and would ensure that we build with java versions that are compatible with WildFly. On the flip side it will restrict our community options although many of the variables do appear to be configurable: > https://github.com/jboss/jboss-parent-pom/ -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1924) Build does not stop on Windows if there is a build failure on the AS and it is not a pull request

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1924?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1924: -------------------------------- Priority: Minor (was: Major) > Build does not stop on Windows if there is a build failure on the AS and it is not a pull request > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1924 > URL: https://issues.jboss.org/browse/JBTM-1924 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Priority: Minor > > You can see the AS failed to build: > http://172.17.131.2/job/narayana-windows2008-taconic/415/console > I suspect it is something to do with: > call build.bat clean install "-DskipTests" "-Drelease=true" || (call:comment_on_pull "AS Failed %BUILD_URL%" && exit -1) > Maybe commit on pull is returning false because nothing is done? -- 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

11 years, 2 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 September 2013