October 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2326: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2326 > URL: https://issues.jboss.org/browse/JBTM-2326 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Tooling > Reporter: Thomas Jenkinson > Priority: Minor > Fix For: 5.next > > > Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com... so it might be useful to others. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2339) MongoDB extension for Compensations

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2339?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2339: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > MongoDB extension for Compensations > ----------------------------------- > > Key: JBTM-2339 > URL: https://issues.jboss.org/browse/JBTM-2339 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations > Reporter: Gytis Trikleris > Priority: Major > Fix For: 5.next > > > Investigate the feasibility of MongoDB compensations patent implementation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2329) Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2329?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2329: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2329 > URL: https://issues.jboss.org/browse/JBTM-2329 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > If an AbstractRecord type has resulted in a heuristic state, it would be useful to provide some form of management API to clear the state on the resource manager. > After discussion on the forum, it seems likely the API would be something like: > Update AbstractRecord to change the return type of value() to the HeuristicManagement interface (rather than Object). Although value() is maybe not the most accurate term and it does appear that this is used internally by XAResourceRecord in an unintended manner (i.e. not dealing with HeuristicInformation. > Add a new interface of modify the existing HeuristicInformation (the current version of which is to be deprecated in: JBTM-2328) > {code} > public interface HeuristicManagement > { > public void resolve() throws CouldNotResolveException; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2372) Create integration test for JBTM-2356

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2372?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2372: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Create integration test for JBTM-2356 > ------------------------------------- > > Key: JBTM-2372 > URL: https://issues.jboss.org/browse/JBTM-2372 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > There was an integration test for it: https://github.com/jbosstm/narayana/commit/5b278de35b9095a27e27514cca4eea.... > However, it was failing on CI intermittently and had to be reverted. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2366) Revise the Narayana architecture diagram on narayana.io

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2366?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2366: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Revise the Narayana architecture diagram on narayana.io > ------------------------------------------------------- > > Key: JBTM-2366 > URL: https://issues.jboss.org/browse/JBTM-2366 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > Attachments: narayana-components-diagram-v2.png > > > There are a lot of new components in the system now that are not reflected in the current architecture diagram. We should try to revise it to make it current with the architecture we have today. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2411) Investigate jgroups-raft and whether this can help with cloud object store

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2411?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2411: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Investigate jgroups-raft and whether this can help with cloud object store > -------------------------------------------------------------------------- > > Key: JBTM-2411 > URL: https://issues.jboss.org/browse/JBTM-2411 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Recovery, Transaction Core > Reporter: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > > http://belaban.blogspot.ch/2015/05/release-of-jgroups-raft-02.html -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2419) Consider reducing the number of JMH perf test forks on PRs

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2419?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2419: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Consider reducing the number of JMH perf test forks on PRs > ---------------------------------------------------------- > > Key: JBTM-2419 > URL: https://issues.jboss.org/browse/JBTM-2419 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > We run our JMH tests multiple times in order to estimate run-to-run variance. The [JMH docs|http://hg.openjdk.java.net/code-tools/jmh/file/tip/jmh-samples/src/m...] state: > bq. JVMs are complex systems, and the non-determinism is inherent for them. This requires us to always account the run-to-run variance as the one of the effects in our experiments. Forking aggregates the results across several JVM launches. > Currently we set the number of forks to 10. We run each test 6 times with each run lasting 1 min. Since we have 10 tests this means it takes 10 * 10 * 6 minutes for the benchmarks to complete. In the future we want to keep adding new performance tests and the time taken to run a PR will become prohibitive. I would like to propose one of the following solutions: > - reduce the number of forks; > - run a subset of performance tests on each PR and then run them all once a week or so on the main build > My preference is to reduce the number of forks to 3. Note that the PR requester has the option to disable performance tests for his PR (by including !PERF in the comment section). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2440: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2483) Investigate ways to test Docker quickstarts

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2483?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2483: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Investigate ways to test Docker quickstarts > ------------------------------------------- > > Key: JBTM-2483 > URL: https://issues.jboss.org/browse/JBTM-2483 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud > Reporter: Gytis Trikleris > Priority: Major > Fix For: 5.next > > > Currently there is only one quickstart for docker (https://github.com/jbosstm/quickstart/tree/master/jts-docker), but its tests are disabled by default. However, it would be good to run them in our CI. > We'll have the same problem in the future with Kubernetes quickstarts. > Maybe Arquillian Cube is something what could help? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2463) QA suite failure: TestGroup_rawresources01_3

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2463?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2463: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > QA suite failure: TestGroup_rawresources01_3 > -------------------------------------------- > > Key: JBTM-2463 > URL: https://issues.jboss.org/browse/JBTM-2463 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Thomas Jenkinson > Priority: Minor > Fix For: 5.next > > Attachments: testoutput-idlj.tar > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-jdbcobjectstore/152/DB... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 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 October 2019