November 2015 - jbossts-issues - Jboss List Archives

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

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2559?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2559: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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)

8 years, 5 months

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 resolved JBTM-2534. ------------------------------------ Resolution: Done Job http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/134/ shows the issue as fixed > 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)

8 years, 5 months

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 resolved JBTM-2555. ------------------------------------ Resolution: Done Main fix was to reduce the number of threads used to run the workload to just 300 > 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)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2560) Add generics

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/JBTM-2560?page=com.atlassian.jira.plugin.... ] Philippe Marschall updated JBTM-2560: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/943 > Add generics > ------------ > > Key: JBTM-2560 > URL: https://issues.jboss.org/browse/JBTM-2560 > Project: JBoss Transaction Manager > Issue Type: Patch > Components: JTA, Recovery, Transaction Core, TxBridge, XTS > Reporter: Philippe Marschall > Assignee: Gytis Trikleris > > Since the source level is Java 5+ the code base can be properly generified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2560) Add generics

by Philippe Marschall (JIRA)

Philippe Marschall created JBTM-2560: ---------------------------------------- Summary: Add generics Key: JBTM-2560 URL: https://issues.jboss.org/browse/JBTM-2560 Project: JBoss Transaction Manager Issue Type: Patch Components: JTA, Recovery, Transaction Core, TxBridge, XTS Reporter: Philippe Marschall Assignee: Gytis Trikleris Since the source level is Java 5+ the code base can be properly generified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2537) Remove the need to build WildFly in IBM ORB job config

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2537: ---------------------------------------- The build is also failing processing idl files: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/149 so more investigation is needed. > Remove the need to build WildFly in IBM ORB job config > ------------------------------------------------------ > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2537) Remove the need to build WildFly in IBM ORB job config

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.... ] Michael Musgrove edited comment on JBTM-2537 at 11/13/15 8:03 AM: ------------------------------------------------------------------ WFLY does not currently support the IBM orb so we should postpone testing with WFLY until such time that it has such support. Note also that we still need to get recovery working with IBM orb (JBTM-2110) so the job does not run any of the tests. was (Author: mmusgrov): WFLY does not currently support the IBM orb so we should postpone testing with WFLY until such time that it has such support. Note also that we still need to get recovery working with IBM orb (JBTM-2110) so the job does not run the QA tests. > Remove the need to build WildFly in IBM ORB job config > ------------------------------------------------------ > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2318) Too verbose startup?

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2318: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Too verbose startup? > -------------------- > > Key: JBTM-2318 > URL: https://issues.jboss.org/browse/JBTM-2318 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > At startup of the most basic example we see ... > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService > INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init> > INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start > INFO: ARJUNA012170: TransactionStatusManager started on port 52185 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > There's a separate conversation to be had about whether the INFO should be there (DEBUG maybe?) but ignoring those why do we print the other lines at all? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2537) Remove the need to build WildFly in IBM ORB job config

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2537: ---------------------------------------- WFLY does not currently support the IBM orb so we should postpone testing with WFLY until such time that it has such support. Note also that we still need to get recovery working with IBM orb (JBTM-2110) so the job does not run the QA tests. > Remove the need to build WildFly in IBM ORB job config > ------------------------------------------------------ > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2537) Remove the need to build WildFly in IBM ORB job config

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2537: -------------------------------- Description: I guess it finally caught us after an .m2 wipe? http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... was: I am not sure if this might really need a WFLY change instead of JBTM? I guess it finally caught us after an .m2 wipe? http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... > Remove the need to build WildFly in IBM ORB job config > ------------------------------------------------------ > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 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 November 2015