November 2015 - jbossts-issues - Jboss List Archives

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

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2556?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2556: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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-2496) Investigate using of camel for content based routing in the Blacktie

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2496?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2496: --------------------------------- I think it might be related to the hornetq upgrade to the activemq artimes. We need the camel-jms to read/write the messages from the queues. > Investigate using of camel for content based routing in the Blacktie > -------------------------------------------------------------------- > > Key: JBTM-2496 > URL: https://issues.jboss.org/browse/JBTM-2496 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.later > > > The current cbr quickstart is out-of-date by using the jboss-esb and it needs to investigate the camel -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2496) Investigate using of camel for content based routing in the Blacktie

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2496?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2496: ------------------------------------- Thanks Amos - what is missing to make it work with WildFly 10, please? > Investigate using of camel for content based routing in the Blacktie > -------------------------------------------------------------------- > > Key: JBTM-2496 > URL: https://issues.jboss.org/browse/JBTM-2496 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.later > > > The current cbr quickstart is out-of-date by using the jboss-esb and it needs to investigate the camel -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2496) Investigate using of camel for content based routing in the Blacktie

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2496?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2496: --------------------------------- I just remove all the out-of-date codes and the wildfly-camel 3.0.1 works with wildfly-9.0.1.Final currently. The example can be found at https://github.com/zhfeng/blacktie-cbr > Investigate using of camel for content based routing in the Blacktie > -------------------------------------------------------------------- > > Key: JBTM-2496 > URL: https://issues.jboss.org/browse/JBTM-2496 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.later > > > The current cbr quickstart is out-of-date by using the jboss-esb and it needs to investigate the camel -- 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: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/939, https://github.com/jbosstm/narayana/pull/941 (was: 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-2534) HQStore crashrec failures on QA_JTS_JDKORB

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2534?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-2534: ------------------------------------ The fix breaks some of the non journal store tests on JacORB (eg narayana job 978) > HQStore crashrec failures on QA_JTS_JDKORB > ------------------------------------------ > > Key: JBTM-2534 > URL: https://issues.jboss.org/browse/JBTM-2534 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > Killed this one: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/... > Normally run to completion but lots of crash rec failures: > {quote} > Total time: 525 minutes 19 seconds > Test Failures: > crashrecovery02_2 CrashRecovery02_2_Test01 Fail (0m50.031s) > crashrecovery02_2 CrashRecovery02_2_Test06 Fail (0m43.914s) > crashrecovery02_2 CrashRecovery02_2_Test07 Fail (0m48.270s) > crashrecovery02_2 CrashRecovery02_2_Test08 Fail (0m48.340s) > crashrecovery02_2 CrashRecovery02_2_Test09 Fail (0m48.014s) > crashrecovery02_2 CrashRecovery02_2_Test10 Fail (0m47.865s) > crashrecovery02_2 CrashRecovery02_2_Test11 Fail (0m48.756s) > crashrecovery02_2 CrashRecovery02_2_Test12 Fail (0m47.992s) > crashrecovery02_2 CrashRecovery02_2_Test13 Fail (0m47.840s) > crashrecovery02_2 CrashRecovery02_2_Test14 Fail (0m47.948s) > crashrecovery02_2 CrashRecovery02_2_Test15 Fail (0m47.742s) > crashrecovery02_2 CrashRecovery02_2_Test16 Fail (0m48.953s) > crashrecovery02_2 CrashRecovery02_2_Test02 Fail (0m48.202s) > crashrecovery02_2 CrashRecovery02_2_Test03 Fail (2m3.776s) > crashrecovery02_2 CrashRecovery02_2_Test04 Fail (0m47.686s) > crashrecovery02_2 CrashRecovery02_2_Test05 Fail (0m47.859s) > crashrecovery02_2 CrashRecovery02_2_Test17 Fail (0m48.029s) > crashrecovery02_2 CrashRecovery02_2_Test18 Fail (0m47.658s) > crashrecovery02_2 CrashRecovery02_2_Test19 Fail (0m47.775s) > crashrecovery02_2 CrashRecovery02_2_Test20 Fail (0m48.086s) > crashrecovery02_2 CrashRecovery02_2_Test21 Fail (0m47.979s) > crashrecovery02_2 CrashRecovery02_2_Test22 Fail (0m48.137s) > crashrecovery02_2 CrashRecovery02_2_Test23 Fail (0m48.267s) > crashrecovery02_2 CrashRecovery02_2_Test24 Fail (0m48.100s) > crashrecovery02_2 CrashRecovery02_2_Test25 Fail (0m47.787s) > crashrecovery05_1 CrashRecovery05_1_Test01 Fail (1m17.781s) > crashrecovery05_1 CrashRecovery05_1_Test10 Fail (1m18.510s) > crashrecovery05_1 CrashRecovery05_1_Test06 Fail (1m17.647s) > crashrecovery05_1 CrashRecovery05_1_Test07 Fail (1m17.572s) > crashrecovery05_1 CrashRecovery05_1_Test08 Fail (1m17.365s) > crashrecovery05_1 CrashRecovery05_1_Test09 Fail (1m17.263s) > crashrecovery05_2 CrashRecovery05_2_Test051 Fail (2m3.491s) > crashrecovery05_2 CrashRecovery05_2_Test052 Fail (0m48.481s) > crashrecovery05_2 CrashRecovery05_2_Test053 Fail (2m3.698s) > crashrecovery05_2 CrashRecovery05_2_Test054 Fail (0m47.293s) > crashrecovery05_2 CrashRecovery05_2_Test055 Fail (0m48.382s) > crashrecovery05_2 CrashRecovery05_2_Test056 Fail (0m43.458s) > crashrecovery05_2 CrashRecovery05_2_Test057 Fail (0m49.076s) > crashrecovery05_2 CrashRecovery05_2_Test058 Fail (0m43.988s) > crashrecovery05_2 CrashRecovery05_2_Test059 Fail (0m48.177s) > crashrecovery05_2 CrashRecovery05_2_Test060 Fail (0m47.995s) > crashrecovery05_2 CrashRecovery05_2_Test061 Fail (0m48.266s) > crashrecovery05_2 CrashRecovery05_2_Test062 Fail (0m47.852s) > crashrecovery05_2 CrashRecovery05_2_Test063 Fail (2m3.059s) > crashrecovery05_2 CrashRecovery05_2_Test064 Fail (0m47.332s) > crashrecovery05_2 CrashRecovery05_2_Test065 Fail (0m47.226s) > crashrecovery05_2 CrashRecovery05_2_Test066 Fail (0m47.141s) > crashrecovery05_2 CrashRecovery05_2_Test067 Fail (0m47.195s) > crashrecovery05_2 CrashRecovery05_2_Test068 Fail (0m47.464s) > crashrecovery05_2 CrashRecovery05_2_Test069 Fail (0m49.360s) > crashrecovery05_2 CrashRecovery05_2_Test070 Fail (0m47.700s) > crashrecovery05_2 CrashRecovery05_2_Test071 Fail (0m47.782s) > crashrecovery05_2 CrashRecovery05_2_Test072 Fail (0m47.736s) > crashrecovery05_2 CrashRecovery05_2_Test073 Fail (0m47.438s) > crashrecovery05_2 CrashRecovery05_2_Test074 Fail (0m47.701s) > crashrecovery05_2 CrashRecovery05_2_Test075 Fail (0m47.385s) > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m10.036s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m54.372s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m10.928s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m55.124s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m54.970s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m50.656s) > crashrecovery05_2 CrashRecovery05_2_Test082 Fail (0m54.356s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m50.052s) > crashrecovery05_2 CrashRecovery05_2_Test084 Fail (0m53.605s) > crashrecovery05_2 CrashRecovery05_2_Test085 Fail (0m54.694s) > crashrecovery05_2 CrashRecovery05_2_Test086 Fail (0m54.147s) > crashrecovery05_2 CrashRecovery05_2_Test087 Fail (0m54.397s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m11.261s) > crashrecovery05_2 CrashRecovery05_2_Test089 Fail (0m54.332s) > crashrecovery05_2 CrashRecovery05_2_Test090 Fail (0m55.264s) > crashrecovery05_2 CrashRecovery05_2_Test091 Fail (0m54.471s) > crashrecovery05_2 CrashRecovery05_2_Test092 Fail (0m54.046s) > crashrecovery05_2 CrashRecovery05_2_Test093 Fail (0m54.249s) > crashrecovery05_2 CrashRecovery05_2_Test094 Fail (0m54.388s) > crashrecovery05_2 CrashRecovery05_2_Test095 Fail (0m53.763s) > crashrecovery05_2 CrashRecovery05_2_Test096 Fail (0m54.313s) > crashrecovery05_2 CrashRecovery05_2_Test097 Fail (0m54.069s) > crashrecovery05_2 CrashRecovery05_2_Test098 Fail (0m54.290s) > crashrecovery05_2 CrashRecovery05_2_Test099 Fail (0m55.164s) > crashrecovery05_2 CrashRecovery05_2_Test100 Fail (0m54.189s) > crashrecovery05_2 CrashRecovery05_2_Test002 Fail (0m46.793s) > crashrecovery05_2 CrashRecovery05_2_Test003 Fail (2m2.944s) > crashrecovery05_2 CrashRecovery05_2_Test005 Fail (0m46.742s) > crashrecovery05_2 CrashRecovery05_2_Test006 Fail (0m42.978s) > crashrecovery05_2 CrashRecovery05_2_Test028 Fail (2m9.683s) > crashrecovery05_2 CrashRecovery05_2_Test031 Fail (0m49.745s) > crashrecovery12 CrashRecovery12_Test03 Fail (0m15.884s) > Buildfile: /home/hudson/workspace/narayana-hqstore/PROFILE/QA_JTS_JDKORB/jdk/jdk8.latest/label/linux/qa/run-tests.xml > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2559) CrashRecovery02_2_Test28 failure on JDKORB and with journal storage

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2559: ------------------------------------- Summary: CrashRecovery02_2_Test28 failure on JDKORB and with journal storage Key: JBTM-2559 URL: https://issues.jboss.org/browse/JBTM-2559 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Gytis Trikleris Assignee: Michael Musgrove Fix For: 5.next -- 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 Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2554: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/job/narayana-jdbcobjectstore/168/ > 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-2554) CrashRecovery05_2 failures on JacORB

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2554: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/job/narayana/980/ > 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-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: Resolved (was: Pull Request Sent) Resolution: Done > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2015