November 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2558) CI report generator error while getting issue info

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2558?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2558: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/ci-report-generator/pull/3 > CI report generator error while getting issue info > -------------------------------------------------- > > Key: JBTM-2558 > URL: https://issues.jboss.org/browse/JBTM-2558 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: CI Report Generator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > {code} > Aggregating narayana build 979 > Aggregating narayana build 978 > Aggregating narayana build 863 > Aggregating narayana build 858 > Aggregating narayana build 830 > Aggregating narayana build 779 > Aggregating narayana build 638 > Aggregating narayana build 550 > Aggregating narayana-benchmarks build 56 > [31mGot an error while getting issue info: [object Object] > [39m[31m > [39m[31mTypeError: Uncaught, unspecified "error" event. > at TypeError (<anonymous>) > at DestroyableTransform.emit (events.js:74:15) > at DestroyableTransform.onerror (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:604:12) > at DestroyableTransform.emit (events.js:95:17) > at onwriteError (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:345:10) > at onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:363:5) > at WritableState.onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:123:5) > at afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:84:5) > at TransformState.afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:59:12) > at /home/hudson/workspace/ci-report-generator/streams/jiraInfoStream.js:23:17 > [39m[33mWarning: [36m-> [39m[31merror [39m[31m8[39m [36m/home/hudson/workspace/ci-report-generator/index.js[39m (8883ms) Use --force to continue.[39m > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2558) CI report generator error while getting issue info

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2558: ------------------------------------- Summary: CI report generator error while getting issue info Key: JBTM-2558 URL: https://issues.jboss.org/browse/JBTM-2558 Project: JBoss Transaction Manager Issue Type: Bug Components: CI Report Generator Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next {code} Aggregating narayana build 979 Aggregating narayana build 978 Aggregating narayana build 863 Aggregating narayana build 858 Aggregating narayana build 830 Aggregating narayana build 779 Aggregating narayana build 638 Aggregating narayana build 550 Aggregating narayana-benchmarks build 56 [31mGot an error while getting issue info: [object Object] [39m[31m [39m[31mTypeError: Uncaught, unspecified "error" event. at TypeError (<anonymous>) at DestroyableTransform.emit (events.js:74:15) at DestroyableTransform.onerror (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:604:12) at DestroyableTransform.emit (events.js:95:17) at onwriteError (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:345:10) at onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:363:5) at WritableState.onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:123:5) at afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:84:5) at TransformState.afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:59:12) at /home/hudson/workspace/ci-report-generator/streams/jiraInfoStream.js:23:17 [39m[33mWarning: [36m-> [39m[31merror [39m[31m8[39m [36m/home/hudson/workspace/ci-report-generator/index.js[39m (8883ms) Use --force to continue.[39m {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2554: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/939 > CrashRecovery05_2 failures on JacORB > ------------------------------------ > > Key: JBTM-2554 > URL: https://issues.jboss.org/browse/JBTM-2554 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.next > > > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2556) Improve OSGi integration

by Guillaume Nodet (JIRA)

[ https://issues.jboss.org/browse/JBTM-2556?page=com.atlassian.jira.plugin.... ] Guillaume Nodet reassigned JBTM-2556: ------------------------------------- Assignee: Guillaume Nodet (was: Amos Feng) > Improve OSGi integration > ------------------------ > > Key: JBTM-2556 > URL: https://issues.jboss.org/browse/JBTM-2556 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Amos Feng > Assignee: Guillaume Nodet > Fix For: 5.next > > > support configuration using ConfigAdmin > track org.jboss.tm.XAResourceRecovery services for recovery > In order to support correctly stopping / restarting / reconfiguring the transaction manager, we build our own class loader to load the core jars. > This ensure that all static fields will be correctly reloaded when starting again after configuration change. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2557) Support Spring PlatformTransactionManager

by Guillaume Nodet (JIRA)

[ https://issues.jboss.org/browse/JBTM-2557?page=com.atlassian.jira.plugin.... ] Guillaume Nodet reassigned JBTM-2557: ------------------------------------- Assignee: Guillaume Nodet (was: Amos Feng) > Support Spring PlatformTransactionManager > ----------------------------------------- > > Key: JBTM-2557 > URL: https://issues.jboss.org/browse/JBTM-2557 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Reporter: Amos Feng > Assignee: Guillaume Nodet > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2557) Support Spring PlatformTransactionManager

by Amos Feng (JIRA)

Amos Feng created JBTM-2557: ------------------------------- Summary: Support Spring PlatformTransactionManager Key: JBTM-2557 URL: https://issues.jboss.org/browse/JBTM-2557 Project: JBoss Transaction Manager Issue Type: Feature Request Components: JTA Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2556) Improve OSGi integration

by Amos Feng (JIRA)

Amos Feng created JBTM-2556: ------------------------------- Summary: Improve OSGi integration Key: JBTM-2556 URL: https://issues.jboss.org/browse/JBTM-2556 Project: JBoss Transaction Manager Issue Type: Enhancement Components: JTA Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next support configuration using ConfigAdmin track org.jboss.tm.XAResourceRecovery services for recovery In order to support correctly stopping / restarting / reconfiguring the transaction manager, we build our own class loader to load the core jars. This ensure that all static fields will be correctly reloaded when starting again after configuration change. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2555) JOTM benchmark produces too many rollback exceptions

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2555?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2555: ----------------------------------- Fix Version/s: 5.next > JOTM benchmark produces too many rollback exceptions > ---------------------------------------------------- > > Key: JBTM-2555 > URL: https://issues.jboss.org/browse/JBTM-2555 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-benchmarks/52/ > The rollbacks are most likely due to transaction timeouts (even though I set the threshold for failure to not more than 10 rollbacks). > It is possible that JOTM just cannot cope with the number of threads we using to produce the benchmark. I have tried to reproduce the failures with a standalone junit test and using JMH on my laptop without success. > I am going to remove JOTM from the comparison matrix (see job narayana-benchmarks) until this JIRA is resolved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2555) JOTM benchmark produces too many rollback exceptions

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2555: -------------------------------------- Summary: JOTM benchmark produces too many rollback exceptions Key: JBTM-2555 URL: https://issues.jboss.org/browse/JBTM-2555 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Michael Musgrove Assignee: Michael Musgrove http://albany.eng.hst.ams2.redhat.com/job/narayana-benchmarks/52/ The rollbacks are most likely due to transaction timeouts (even though I set the threshold for failure to not more than 10 rollbacks). It is possible that JOTM just cannot cope with the number of threads we using to produce the benchmark. I have tried to reproduce the failures with a standalone junit test and using JMH on my laptop without success. I am going to remove JOTM from the comparison matrix (see job narayana-benchmarks) until this JIRA is resolved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2552) Benchmark script should accept extra script arguments

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2552?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2552. ------------------------------------ Release Notes Text: The benchmark script already supports passing extra arguments via a variable called JVM_ARGS Resolution: Rejected > Benchmark script should accept extra script arguments > ----------------------------------------------------- > > Key: JBTM-2552 > URL: https://issues.jboss.org/browse/JBTM-2552 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.7.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The launch script for running benchmarks (narayana/scripts/hudson/benchmark.sh in the repo https://github.com/jbosstm/performance) should propagate any script arguments through to the benchmark script. > I plan to use this for configuring things like the transaction timeout value and to configure how many commit failures are tolerated before failing the job. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2015