November 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2302. ------------------------------------ Resolution: Done > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2283) Tooling no longer exposes JTS record types

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2283?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2283: ----------------------------------------------- Hayk Hovsepyan <hhovsepy(a)redhat.com> changed the Status of [bug 1151071|https://bugzilla.redhat.com/show_bug.cgi?id=1151071] from ON_QA to VERIFIED > Tooling no longer exposes JTS record types > ------------------------------------------ > > Key: JBTM-2283 > URL: https://issues.jboss.org/browse/JBTM-2283 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > Transacton records of type StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple are no longer exposed via the tooling. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server"

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1683: --------------------------------- I create a new job http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie-JBTM/job/JBT... to run the test > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.0 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.4 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2299) Why does Blacktie have its own CosTransactions.idl?

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2299?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2299: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/779 > Why does Blacktie have its own CosTransactions.idl? > --------------------------------------------------- > > Key: JBTM-2299 > URL: https://issues.jboss.org/browse/JBTM-2299 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.0.4 > > > Shouldn't it use the one in ArjunaJTS? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2299) Why does Blacktie have its own CosTransactions.idl?

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2299?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2299: --------------------------------- I've sent the PR to remove these idl files > Why does Blacktie have its own CosTransactions.idl? > --------------------------------------------------- > > Key: JBTM-2299 > URL: https://issues.jboss.org/browse/JBTM-2299 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.0.4 > > > Shouldn't it use the one in ArjunaJTS? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2306) Tooling does not display the type of a heuristic

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2306?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2306: ---------------------------------------- The missing bit of the interface is: {code} /** * A reference to the entity that caused the heuristic. * @return the entity reference */ public Object getEntityReference(); {code} I think we would need to firm up the type of reference returned in order for it to be usable for recovery purposes. We would also need to warn users that recovery via this interface may conflict with our existing recovery mechanism. When you say "we need to consider whether it should be added back" - what would be the best mechanism to discuss that, via a forum post or via a JIRA that people can vote up, or something else? > Tooling does not display the type of a heuristic > ------------------------------------------------ > > Key: JBTM-2306 > URL: https://issues.jboss.org/browse/JBTM-2306 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0 > > > The new JMX based tooling for browsing abstract records does not display the particular type of a heuristic *when it's available*. > There is a comment in the javadoc for AbstractRecord which seems to indicate that the particular kind of heuristic may be available: > {code} > /** > * If this abstract record caused a heuristic then it should return an > * object which implements <code>HeuristicInformation</code> > * > * @return <code>Object</code> to be used to order. > */ > public abstract Object value (); > {code} > HeuristicInformation contains a method getHeuristicType() which looks like it may report the particular kind of heuristic.: > {code} > public interface HeuristicInformation { > /** > * The type of heuristic. > * @return the heuristic type > */ > public int getHeuristicType(); > {code} > This JIRA is asking for value() object to be consulted to see if it contains an instance of HeuristicInformation and if so to report it in the JBX MBean corresponding to the AR. > Note that such a change would only affect 3rd party implementers of ARs (since our own code does not set this field). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2302: ----------------------------------------------- Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 1165700|https://bugzilla.redhat.com/show_bug.cgi?id=1165700] from NEW to ASSIGNED > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2306) Tooling does not display the type of a heuristic

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2306?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2306: ----------------------------------- As I was explaining to Tom yesterday, HeuristicInformation was also supposed to return a reference to something which could be used to drive the heuristic at the participant to completion. You've not included the whole interface to see that, but it's important. We may not have ever used it, but we need to consider whether it should be added back - or equivalent. > Tooling does not display the type of a heuristic > ------------------------------------------------ > > Key: JBTM-2306 > URL: https://issues.jboss.org/browse/JBTM-2306 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.0.0 > > > The new JMX based tooling for browsing abstract records does not display the particular type of a heuristic *when it's available*. > There is a comment in the javadoc for AbstractRecord which seems to indicate that the particular kind of heuristic may be available: > {code} > /** > * If this abstract record caused a heuristic then it should return an > * object which implements <code>HeuristicInformation</code> > * > * @return <code>Object</code> to be used to order. > */ > public abstract Object value (); > {code} > HeuristicInformation contains a method getHeuristicType() which looks like it may report the particular kind of heuristic.: > {code} > public interface HeuristicInformation { > /** > * The type of heuristic. > * @return the heuristic type > */ > public int getHeuristicType(); > {code} > This JIRA is asking for value() object to be consulted to see if it contains an instance of HeuristicInformation and if so to report it in the JBX MBean corresponding to the AR. > Note that such a change would only affect 3rd party implementers of ARs (since our own code does not set this field). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2306) Tooling does not display the type of a heuristic

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2306: -------------------------------------- Summary: Tooling does not display the type of a heuristic Key: JBTM-2306 URL: https://issues.jboss.org/browse/JBTM-2306 Project: JBoss Transaction Manager Issue Type: Bug Components: Tooling Affects Versions: 5.0.3 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 6.0.0 The new JMX based tooling for browsing abstract records does not display the particular type of a heuristic *when it's available*. There is a comment in the javadoc for AbstractRecord which seems to indicate that the particular kind of heuristic may be available: {code} /** * If this abstract record caused a heuristic then it should return an * object which implements <code>HeuristicInformation</code> * * @return <code>Object</code> to be used to order. */ public abstract Object value (); {code} HeuristicInformation contains a method getHeuristicType() which looks like it may report the particular kind of heuristic.: {code} public interface HeuristicInformation { /** * The type of heuristic. * @return the heuristic type */ public int getHeuristicType(); {code} This JIRA is asking for value() object to be consulted to see if it contains an instance of HeuristicInformation and if so to report it in the JBX MBean corresponding to the AR. Note that such a change would only affect 3rd party implementers of ARs (since our own code does not set this field). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2305) Incomplete tooling documentation

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2305: -------------------------------------- Summary: Incomplete tooling documentation Key: JBTM-2305 URL: https://issues.jboss.org/browse/JBTM-2305 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Documentation Affects Versions: 5.0.3 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.4 For tooling the docs defer to the wildfly/EAP cli for "5.1.1. Browse and Manage Transactions Using an Application Server". We had some text in the README explaining how to view the tooling MBeans but the equivalent needs to be added to the development_guide too for use with standalone narayana. In addition the docs need to explain how to extend the tooling for new abstract records (basically the user needs to create a JMX MBean for the new type and register it with the ObjStoreBrowser). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2014