June 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2170) Jacoco failed to create QA code coverage report

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2170?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2170: ------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/121/ > Jacoco failed to create QA code coverage report > ----------------------------------------------- > > Key: JBTM-2170 > URL: https://issues.jboss.org/browse/JBTM-2170 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/118 > {code} > BUILD SUCCESSFUL > Total time: 510 minutes 46 seconds > generating test coverage report > Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml > jacoco-report: > [jacoco:report] Loading execution data file /home/hudson/workspace/narayana-codeCoverage/qa/testoutput/jacoco-qa.exec > BUILD FAILED > /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml:540: Error while creating report > Total time: 8 seconds > Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml > has-testoutput-output: > testoutput.zip: > [echo] archiving testoutput to testoutput-jacorb.zip > [zip] Building zip: /home/hudson/workspace/narayana-codeCoverage/qa/testoutput-jacorb.zip > BUILD SUCCESSFUL > Total time: 9 seconds > + rm -rf /home/hudson/.m2/repository/org/jboss/narayana > + cd qa > + ant -f run-tests.xml jacoco-report > Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml > jacoco-report: > [jacoco:report] Loading execution data file /home/hudson/workspace/narayana-codeCoverage/qa/testoutput/jacoco-qa.exec > BUILD FAILED > /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml:540: Error while creating report > Total time: 9 seconds > Build step 'Execute shell' marked build as failure > Archiving artifacts > Sending e-mails to: gtrikler(a)redhat.com > Finished: FAILURE > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2186) Probing the object store raises an error if the recovery manager has not performed a first pass

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2186: ----------------------------------- Summary: Probing the object store raises an error if the recovery manager has not performed a first pass Key: JBTM-2186 URL: https://issues.jboss.org/browse/JBTM-2186 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Resource Manager Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 4.17.21, 5.0.3 ObjectStoreBrowser::probe requires that the recovery manager performs the first pass of recovery to load in the current in doubt Xids. This is not currently done so the user gets an error. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2185) Re-enable the CMR integration test

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2185?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2185: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/665 > Re-enable the CMR integration test > ---------------------------------- > > Key: JBTM-2185 > URL: https://issues.jboss.org/browse/JBTM-2185 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.3 > > > For some reason the CMR integration test was disabled/not fully added so re-enable it in master. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2185) Re-enable the CMR integration test

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2185: ----------------------------------- Summary: Re-enable the CMR integration test Key: JBTM-2185 URL: https://issues.jboss.org/browse/JBTM-2185 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.3 For some reason the CMR integration test was disabled/not fully added so re-enable it in master. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2161) Allow the list of jndi names to contact in the CMR recovery module to be refreshed when a new CMR resource is added

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2161?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2161: ------------------------------------- Moved to WFLY-3347 > Allow the list of jndi names to contact in the CMR recovery module to be refreshed when a new CMR resource is added > ------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2161 > URL: https://issues.jboss.org/browse/JBTM-2161 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Resource Manager > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Currently the list is fixed at startup time as it is stored in a list, as there is no real performance impact of checking the list once every 120 seconds and it will allow resources to be more dynamically added (at least for recovery). > It would assist with: https://bugzilla.redhat.com/show_bug.cgi?id=1091308 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2161) Allow the list of jndi names to contact in the CMR recovery module to be refreshed when a new CMR resource is added

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2161?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2161: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com> changed the Status of [bug 1091308|https://bugzilla.redhat.com/show_bug.cgi?id=1091308] from ON_QA to ASSIGNED > Allow the list of jndi names to contact in the CMR recovery module to be refreshed when a new CMR resource is added > ------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2161 > URL: https://issues.jboss.org/browse/JBTM-2161 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Resource Manager > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Currently the list is fixed at startup time as it is stored in a list, as there is no real performance impact of checking the list once every 120 seconds and it will allow resources to be more dynamically added (at least for recovery). > It would assist with: https://bugzilla.redhat.com/show_bug.cgi?id=1091308 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2161) Allow the list of jndi names to contact in the CMR recovery module to be refreshed when a new CMR resource is added

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2161?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2161: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1091308|https://bugzilla.redhat.com/show_bug.cgi?id=1091308] from MODIFIED to ON_QA > Allow the list of jndi names to contact in the CMR recovery module to be refreshed when a new CMR resource is added > ------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2161 > URL: https://issues.jboss.org/browse/JBTM-2161 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Resource Manager > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Currently the list is fixed at startup time as it is stored in a list, as there is no real performance impact of checking the list once every 120 seconds and it will allow resources to be more dynamically added (at least for recovery). > It would assist with: https://bugzilla.redhat.com/show_bug.cgi?id=1091308 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2151) Create a Quickstart showing MongoDB and Compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2151?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-2151: ------------------------------------- I hope to resolve it soon as I need it for part 2 of my mongodb blog post. I think I can run an embedded server, so could be relatively easy to do. > Create a Quickstart showing MongoDB and Compensations API > --------------------------------------------------------- > > Key: JBTM-2151 > URL: https://issues.jboss.org/browse/JBTM-2151 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.3 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2151) Create a Quickstart showing MongoDB and Compensations API

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2151?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2151: ------------------------------------- Should I remove the fix version number as I don't believe this is work that is currently scheduled? > Create a Quickstart showing MongoDB and Compensations API > --------------------------------------------------------- > > Key: JBTM-2151 > URL: https://issues.jboss.org/browse/JBTM-2151 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.3 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2184: ----------------------------------- Assignee: Tom Jenkinson (was: Paul Robinson) > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > Fix For: 5.0.3 > > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

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