June 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3017) Provide a check to see if the last recovery scan "cleaned" the store.

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3017?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-3017: ------------------------------------ Reopened because the recoveryProblems flag was not getting reset on the first pass. There should be extra tests to cover this bug too. > Provide a check to see if the last recovery scan "cleaned" the store. > ---------------------------------------------------------------------- > > Key: JBTM-3017 > URL: https://issues.jboss.org/browse/JBTM-3017 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery, Tooling > Affects Versions: 5.8.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > There are some recovery manager use cases where the user needs to know that the log store is empty and that all orphans have been detected (for example it is possible that some resource managers were not available during the last scan). > This feature would be particularly useful when running on OpenShift in order to determine when it is safe scale down and reclaim the space used by a pod. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3039) Add a bean method to report whether or not all XAResources were contaced during the last recovery scan

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3039?page=com.atlassian.jira.plugin.... ] Michael Musgrove closed JBTM-3039. ---------------------------------- Resolution: Rejected Rejected since the functionality is already provided by https://issues.jboss.org/browse/JBTM-3017 > Add a bean method to report whether or not all XAResources were contaced during the last recovery scan > ------------------------------------------------------------------------------------------------------ > > Key: JBTM-3039 > URL: https://issues.jboss.org/browse/JBTM-3039 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Affects Versions: 5.5.30.Final, 5.8.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.5.31.Final, 5.next > > > There are some recovery manager use cases where the user needs to know that all orphans have been detected (for example it is possible that some registered resource managers were not contactable during the last scan). > This feature would be particularly useful when running on OpenShift in order to determine when it is safe to scale down and reclaim the space used by a pod. > The proposal is to validate that the recover() method was successfully invoked on all currently registered resources. The proposed new method should report whether or not there were any errors or warnings during last recovery scan made by the XARecoveryModule. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3017) Provide a check to see if the last recovery scan "cleaned" the store.

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3017?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-3017. ------------------------------------ Resolution: Done Closing again since the requirement is for a programmatic mechanism to obtain the status of the last scan and this feature already exists in the current fix (by calling jtaLogger.isRecoveryProblems()). > Provide a check to see if the last recovery scan "cleaned" the store. > ---------------------------------------------------------------------- > > Key: JBTM-3017 > URL: https://issues.jboss.org/browse/JBTM-3017 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery, Tooling > Affects Versions: 5.8.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > There are some recovery manager use cases where the user needs to know that the log store is empty and that all orphans have been detected (for example it is possible that some resource managers were not available during the last scan). > This feature would be particularly useful when running on OpenShift in order to determine when it is safe scale down and reclaim the space used by a pod. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3030) Moving the tomcat-jta to the JWS web-servers repo

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-3030?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-3030: --------------------------------- Thanks [~jfclere], no other ones need to be added. > Moving the tomcat-jta to the JWS web-servers repo > ------------------------------------------------- > > Key: JBTM-3030 > URL: https://issues.jboss.org/browse/JBTM-3030 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tomcat > Reporter: Amos Feng > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3030) Moving the tomcat-jta to the JWS web-servers repo

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/JBTM-3030?page=com.atlassian.jira.plugin.... ] Jean-Frederic Clere commented on JBTM-3030: ------------------------------------------- OK let's move it to https://github.com/web-servers and add [~zhfeng] to our people. [~zhfeng] any other committers to add? > Moving the tomcat-jta to the JWS web-servers repo > ------------------------------------------------- > > Key: JBTM-3030 > URL: https://issues.jboss.org/browse/JBTM-3030 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tomcat > Reporter: Amos Feng > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3039) Add a bean method to report whether or not all XAResources were contaced during the last recovery scan

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-3039: -------------------------------------- Summary: Add a bean method to report whether or not all XAResources were contaced during the last recovery scan Key: JBTM-3039 URL: https://issues.jboss.org/browse/JBTM-3039 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Recovery Affects Versions: 5.8.2.Final, 5.5.30.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.5.31.Final, 5.next There are some recovery manager use cases where the user needs to know that all orphans have been detected (for example it is possible that some registered resource managers were not contactable during the last scan). This feature would be particularly useful when running on OpenShift in order to determine when it is safe to scale down and reclaim the space used by a pod. The proposal is to validate that the recover() method was successfully invoked on all currently registered resources. The proposed new method should report whether or not there were any errors or warnings during last recovery scan made by the XARecoveryModule. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3017) Provide a check to see if the last recovery scan "cleaned" the store.

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3017?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-3017: ------------------------------------ I have reopened JBTM-3017 so that the program returns a standard code according to the conventions defined in System.exit(n). > Provide a check to see if the last recovery scan "cleaned" the store. > ---------------------------------------------------------------------- > > Key: JBTM-3017 > URL: https://issues.jboss.org/browse/JBTM-3017 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery, Tooling > Affects Versions: 5.8.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > There are some recovery manager use cases where the user needs to know that the log store is empty and that all orphans have been detected (for example it is possible that some resource managers were not available during the last scan). > This feature would be particularly useful when running on OpenShift in order to determine when it is safe scale down and reclaim the space used by a pod. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3038) Include the checkstyle plugin in LRA maven poms

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3038?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3038: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Include the checkstyle plugin in LRA maven poms > ----------------------------------------------- > > Key: JBTM-3038 > URL: https://issues.jboss.org/browse/JBTM-3038 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.8.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > To achieve a level of consistency of code it would be advantageous to include a formal set of checkstyle rules in this project. > Since a primary user of the LRA coordinator and LRA APIs are microprofile-lra and thorntail it makes sense to use the ruleset from one of those projects. For example, thorntail uses: > {code} >  > <dependency> > <groupId>org.wildfly.swarm</groupId> > <artifactId>checkstyle-config</artifactId> > <version>1</version> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3038) Include the checkstyle plugin in LRA maven poms

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3038?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3038: ----------------------------------- Description: To achieve a level of consistency of code it would be advantageous to include a formal set of checkstyle rules in this project. Since a primary user of the LRA coordinator and LRA APIs are microprofile-lra and thorntail it makes sense to use the ruleset from one of those projects. For example, thorntail uses: {code}  <dependency> <groupId>org.wildfly.swarm</groupId> <artifactId>checkstyle-config</artifactId> <version>1</version> </dependency> {code} was: To achieve a level of consistency of code it would be advantageous to include a formal set of checkstyle rules in this project. Since a primary user of the LRA coordinator and LRA APIs are microprofile-lra and thorntail it makes sense to use the ruleset from one of those projects. For example, thorntail uses: {code}  <dependency> <groupId>org.wildfly.swarm</groupId> <artifactId>checkstyle-config</artifactId> <version>1</version> </dependency> {code} Note that thorntail and wildfly appear to use the same ruleset. > Include the checkstyle plugin in LRA maven poms > ----------------------------------------------- > > Key: JBTM-3038 > URL: https://issues.jboss.org/browse/JBTM-3038 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.8.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > To achieve a level of consistency of code it would be advantageous to include a formal set of checkstyle rules in this project. > Since a primary user of the LRA coordinator and LRA APIs are microprofile-lra and thorntail it makes sense to use the ruleset from one of those projects. For example, thorntail uses: > {code} >  > <dependency> > <groupId>org.wildfly.swarm</groupId> > <artifactId>checkstyle-config</artifactId> > <version>1</version> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3038) Include the checkstyle plugin in LRA maven poms

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3038?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3038: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1337 > Include the checkstyle plugin in LRA maven poms > ----------------------------------------------- > > Key: JBTM-3038 > URL: https://issues.jboss.org/browse/JBTM-3038 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.8.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > To achieve a level of consistency of code it would be advantageous to include a formal set of checkstyle rules in this project. > Since a primary user of the LRA coordinator and LRA APIs are microprofile-lra and thorntail it makes sense to use the ruleset from one of those projects. For example, thorntail uses: > {code} >  > <dependency> > <groupId>org.wildfly.swarm</groupId> > <artifactId>checkstyle-config</artifactId> > <version>1</version> > </dependency> > {code} > Note that thorntail and wildfly appear to use the same ruleset. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 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 June 2018