December 2014 - jbossts-issues - Jboss List Archives

[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 updated JBTM-2308: ----------------------------------- Fix Version/s: 5.0.5 > 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)

10 years

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 updated JBTM-2308: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/795, https://github.com/jbosstm/narayana/pull/796 (was: https://github.com/jbosstm/narayana/pull/795) > 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)

10 years

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 updated JBTM-2308: ----------------------------------- Fix Version/s: (was: 5.0.5) > 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 > > > 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)

10 years

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 updated JBTM-2308: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done I will raise a separate JIRA or re-open this one to forward port the changes to the master branch. > 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 > > > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2317) SAX parsing of properties file fails when offline

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2317?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2317. ------------------------------- Resolution: Done > SAX parsing of properties file fails when offline > ------------------------------------------------- > > Key: JBTM-2317 > URL: https://issues.jboss.org/browse/JBTM-2317 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Common > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > The SAX parser verifies DTDs during parsing of the XML files, this is not done for the StAX parser. As our properties files usually link to the Sun DTD for properties on from java.sun.com this causes SAX parsing to fail when offline. > We only have one test that uses SAX parsing (SAX parsing was added for Android). The workaround is to access the XMLReader from the parser and disable validation and loading-external-dtd's. The unit test still works with this disabled so I think it is safe to ignore downloading the Sun properties DTD. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2317) SAX parsing of properties file fails when offline

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2317?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2317: -------------------------------- Issue Type: Bug (was: Enhancement) > SAX parsing of properties file fails when offline > ------------------------------------------------- > > Key: JBTM-2317 > URL: https://issues.jboss.org/browse/JBTM-2317 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Common > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > The SAX parser verifies DTDs during parsing of the XML files, this is not done for the StAX parser. As our properties files usually link to the Sun DTD for properties on from java.sun.com this causes SAX parsing to fail when offline. > We only have one test that uses SAX parsing (SAX parsing was added for Android). The workaround is to access the XMLReader from the parser and disable validation and loading-external-dtd's. The unit test still works with this disabled so I think it is safe to ignore downloading the Sun properties DTD. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2317) SAX parsing of properties file fails when offline

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2317?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-2317: --------------------------------- > SAX parsing of properties file fails when offline > ------------------------------------------------- > > Key: JBTM-2317 > URL: https://issues.jboss.org/browse/JBTM-2317 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > The SAX parser verifies DTDs during parsing of the XML files, this is not done for the StAX parser. As our properties files usually link to the Sun DTD for properties on from java.sun.com this causes SAX parsing to fail when offline. > We only have one test that uses SAX parsing (SAX parsing was added for Android). The workaround is to access the XMLReader from the parser and disable validation and loading-external-dtd's. The unit test still works with this disabled so I think it is safe to ignore downloading the Sun properties DTD. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2313) Aggregate Jacoco code coverage reports

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2313?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2313: -------------------------------- Fix Version/s: 5.0.4 (was: 6.x.y) > Aggregate Jacoco code coverage reports > --------------------------------------- > > Key: JBTM-2313 > URL: https://issues.jboss.org/browse/JBTM-2313 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.4 > > > Either combine the individual jacoco.exec files or see if the Jacoco Jenkins plugin does the job (https://wiki.jenkins-ci.org/display/JENKINS/JaCoCo+Plugin) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2313) Aggregate Jacoco code coverage reports

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2313?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2313. ------------------------------- > Aggregate Jacoco code coverage reports > --------------------------------------- > > Key: JBTM-2313 > URL: https://issues.jboss.org/browse/JBTM-2313 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.4 > > > Either combine the individual jacoco.exec files or see if the Jacoco Jenkins plugin does the job (https://wiki.jenkins-ci.org/display/JENKINS/JaCoCo+Plugin) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2321?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2321: ------------------------------------- I have removed sansa from the config temporarily till this is resolved. Amos, please can you put the tgz of the dependencies on albany userContent location and update the job config to: scp hudson@albany:centos70x64.tgz ~ (cd ~ && tar txf centos70x64.tgz) assuming the format of centos70x64.tgz is .m2/repository/MISSING_DEPS Alternatively we just need to make sure none of the jobs wipe out the entire .m2 but I think it might be easier to do the above. Thanks, Tom (I would do this myself but I can't find a copy of the built dependencies) > 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)

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 December 2014