October 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2318) Too verbose startup?

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2318: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Too verbose startup? > -------------------- > > Key: JBTM-2318 > URL: https://issues.jboss.org/browse/JBTM-2318 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > At startup of the most basic example we see ... > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService > INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init> > INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start > INFO: ARJUNA012170: TransactionStatusManager started on port 52185 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > There's a separate conversation to be had about whether the INFO should be there (DEBUG maybe?) but ignoring those why do we print the other lines at all? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 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 Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2329?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2329: ----------------------------------- Assignee: (was: Michael Musgrove) > 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 > Fix For: 5.later > > > 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 (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[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 Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2326: ----------------------------------- Assignee: (was: Michael Musgrove) > 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: Tom Jenkinson > Fix For: 5.later > > > 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 (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[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 Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2326: ----------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > 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: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.later > > > 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 (v6.4.11#64026)

8 years, 7 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 Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2329?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2329: ----------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > 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 > Assignee: Michael Musgrove > Fix For: 5.later > > > 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 (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2463?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2463: ----------------------------------- Assignee: (was: Tom Jenkinson) > 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: Tom Jenkinson > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-jdbcobjectstore/152/DB... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2505) Java heap space issue on Brandon

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2505?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2505: ----------------------------------- Assignee: (was: Tom Jenkinson) > Java heap space issue on Brandon > -------------------------------- > > Key: JBTM-2505 > URL: https://issues.jboss.org/browse/JBTM-2505 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.2.5.Final > Reporter: Gytis Trikleris > Attachments: consoleText.txt > > > narayana-AS800 build fails whenever it runs on Brandon due to not enough java heap space. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2115) Not all classes are under code coverage

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2115: -------------------------------- Priority: Major (was: Minor) > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2534) HQStore hanging on QA_JTS_JDKORB

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2534?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2534: -------------------------------- Priority: Critical (was: Major) > HQStore hanging on QA_JTS_JDKORB > -------------------------------- > > Key: JBTM-2534 > URL: https://issues.jboss.org/browse/JBTM-2534 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2530) jacoco failures

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2530: ------------------------------------- Thanks Mike, I just wondered if it was borked due to not managing to build something and so falls back to trying to instrument JDK classes as that was all it had. nps > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 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 2015