December 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2316) Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage and remove performance tool

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2316?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2316: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/797 > Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage and remove performance tool > ------------------------------------------------------------------------------------------------- > > Key: JBTM-2316 > URL: https://issues.jboss.org/browse/JBTM-2316 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > I can't see the transactional driver or JTAx stuff in the code-coverage report and I also don't think its worth aggregating in the performance test harness into the coverage numbers. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2316) Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage and remove performance tool

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2316?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2316: ----------------------------------- Fix Version/s: 5.0.5 (was: 5.x.y) > Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage and remove performance tool > ------------------------------------------------------------------------------------------------- > > Key: JBTM-2316 > URL: https://issues.jboss.org/browse/JBTM-2316 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > I can't see the transactional driver or JTAx stuff in the code-coverage report and I also don't think its worth aggregating in the performance test harness into the coverage numbers. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2316) Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage and remove performance tool

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2316?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2316: ---------------------------------------- Both are producing reports now: - ArjunaJTS/jtax was missing because the surefire test config was overwriting the jacoco:prepare-agent args I fixed that by moving the Xss setting to the codeCoverage profile in the top level pom - jdbc coverate was missing because it was skipped > Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage and remove performance tool > ------------------------------------------------------------------------------------------------- > > Key: JBTM-2316 > URL: https://issues.jboss.org/browse/JBTM-2316 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > I can't see the transactional driver or JTAx stuff in the code-coverage report and I also don't think its worth aggregating in the performance test harness into the coverage numbers. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

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 resolved JBTM-2306. ------------------------------------ Resolution: Done The relevant unit test is https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/jtax/tests/clas... which I created whilst fixing JBTM-2308 > 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.x.y > > > 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.11#6341)

9 years, 11 months

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 updated JBTM-2306: ----------------------------------- Fix Version/s: 5.0.4 (was: 6.x.y) > 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: 5.0.4 > > > 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.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2321) apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 not found during Blacktie build

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2321?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2321: --------------------------------- sure, I will do > apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 not found during Blacktie build > ------------------------------------------------------------------------------------- > > Key: JBTM-2321 > URL: https://issues.jboss.org/browse/JBTM-2321 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Build System > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-quickstart... > {code} > [ERROR] Failed to execute goal on project blacktie-C: Could not resolve dependencies for project org.jboss.narayana.blacktie:blacktie-C:pom:5.0.5.Final-SNAPSHOT: Could not find artifact apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 in jbossThirdParty (https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/) -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2324) Add STM capabilities to Ceylon

by Mark Little (JIRA)

Mark Little created JBTM-2324: --------------------------------- Summary: Add STM capabilities to Ceylon Key: JBTM-2324 URL: https://issues.jboss.org/browse/JBTM-2324 Project: JBoss Transaction Manager Issue Type: Feature Request Components: STM Affects Versions: 5.0.4 Reporter: Mark Little Assignee: Mark Little -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2308: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 1168973|https://bugzilla.redhat.com/show_bug.cgi?id=1168973] from ASSIGNED to POST > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.0.5 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2308. ------------------------------------ Resolution: Done > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.0.5 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-2308: ------------------------------------ Added master to the target releases - waiting for PR 796 > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.0.5 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 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 December 2014