September 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2411) Investigate jgroups-raft and whether this can help with cloud object store

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2411?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2411: ----------------------------------- Fix Version/s: 5.next (was: 5.9.8.Final) > Investigate jgroups-raft and whether this can help with cloud object store > -------------------------------------------------------------------------- > > Key: JBTM-2411 > URL: https://issues.jboss.org/browse/JBTM-2411 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Recovery, Transaction Core > Reporter: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > > http://belaban.blogspot.ch/2015/05/release-of-jgroups-raft-02.html -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2419) Consider reducing the number of JMH perf test forks on PRs

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2419?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2419: ----------------------------------- Fix Version/s: 5.next (was: 5.9.8.Final) > Consider reducing the number of JMH perf test forks on PRs > ---------------------------------------------------------- > > Key: JBTM-2419 > URL: https://issues.jboss.org/browse/JBTM-2419 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > We run our JMH tests multiple times in order to estimate run-to-run variance. The [JMH docs|http://hg.openjdk.java.net/code-tools/jmh/file/tip/jmh-samples/src/m...] state: > bq. JVMs are complex systems, and the non-determinism is inherent for them. This requires us to always account the run-to-run variance as the one of the effects in our experiments. Forking aggregates the results across several JVM launches. > Currently we set the number of forks to 10. We run each test 6 times with each run lasting 1 min. Since we have 10 tests this means it takes 10 * 10 * 6 minutes for the benchmarks to complete. In the future we want to keep adding new performance tests and the time taken to run a PR will become prohibitive. I would like to propose one of the following solutions: > - reduce the number of forks; > - run a subset of performance tests on each PR and then run them all once a week or so on the main build > My preference is to reduce the number of forks to 3. Note that the PR requester has the option to disable performance tests for his PR (by including !PERF in the comment section). -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2440: ----------------------------------- Fix Version/s: 5.next (was: 5.9.8.Final) > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2463) QA suite failure: TestGroup_rawresources01_3

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2463?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2463: ----------------------------------- Fix Version/s: 5.next (was: 5.9.8.Final) > QA suite failure: TestGroup_rawresources01_3 > -------------------------------------------- > > Key: JBTM-2463 > URL: https://issues.jboss.org/browse/JBTM-2463 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Thomas Jenkinson > Priority: Minor > Fix For: 5.next > > Attachments: testoutput-idlj.tar > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-jdbcobjectstore/152/DB... -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2483) Investigate ways to test Docker quickstarts

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2483?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2483: ----------------------------------- Fix Version/s: 5.next (was: 5.9.8.Final) > Investigate ways to test Docker quickstarts > ------------------------------------------- > > Key: JBTM-2483 > URL: https://issues.jboss.org/browse/JBTM-2483 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud > Reporter: Gytis Trikleris > Priority: Major > Fix For: 5.next > > > Currently there is only one quickstart for docker (https://github.com/jbosstm/quickstart/tree/master/jts-docker), but its tests are disabled by default. However, it would be good to run them in our CI. > We'll have the same problem in the future with Kubernetes quickstarts. > Maybe Arquillian Cube is something what could help? -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2484) JTSRemote_TimeoutTest from jtsremote tests failed on local cluster

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2484?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2484: ----------------------------------- Fix Version/s: 5.next (was: 5.9.8.Final) > JTSRemote_TimeoutTest from jtsremote tests failed on local cluster > ------------------------------------------------------------------ > > Key: JBTM-2484 > URL: https://issues.jboss.org/browse/JBTM-2484 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Attachments: JTSRemote_TimeoutTest.tar > > > The only error is is in the client when it tries to rollback the transaction (see attached logs): > bq. FATAL: ARJUNA022006: The ORB has not been initialized yet -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2867) Investigate un-_workList protected access to _work object

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2867?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2867: ----------------------------------- Fix Version/s: 5.next (was: 5.9.8.Final) > Investigate un-_workList protected access to _work object > --------------------------------------------------------- > > Key: JBTM-2867 > URL: https://issues.jboss.org/browse/JBTM-2867 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > > During investigation of JBTM-2865 it was detected that the _work object can be accessed outside of the _workList synchronized block. Notably this seems to be a .remove() operation on it which can mutate the struct and may cause issues. > For example, this looks wrong: > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef209... > If > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef209... -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2855) Consider using assertions to validate locking assumptions

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2855?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2855: ----------------------------------- Fix Version/s: 5.next (was: 5.9.8.Final) > Consider using assertions to validate locking assumptions > --------------------------------------------------------- > > Key: JBTM-2855 > URL: https://issues.jboss.org/browse/JBTM-2855 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.5.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Some methods in BasicAction assume that other methods will acquire monitors before calling them; it would aid both maintenance/readability and testing if we such methods have assert Thread.holdsLock(this); at their beginning point. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2833) Move deprecated tooling classes into an internal package

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2833?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2833: ----------------------------------- Fix Version/s: 5.next (was: 5.9.8.Final) > Move deprecated tooling classes into an internal package > -------------------------------------------------------- > > Key: JBTM-2833 > URL: https://issues.jboss.org/browse/JBTM-2833 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tooling > Affects Versions: 5.5.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > commit 66a9291f56f (JBTM-2308]) "Mark classes deprecated since we need to rejig package names" marked many/most of the tooling instrumentation classes deprecated - these need to be moved to internal packages and the then marked as not deprecated. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2832) Blacktie TestTPGetRely::test_tpgetrply_with_TPGETANY fail

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2832?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2832: ----------------------------------- Fix Version/s: 5.next (was: 5.9.8.Final) > Blacktie TestTPGetRely::test_tpgetrply_with_TPGETANY fail > --------------------------------------------------------- > > Key: JBTM-2832 > URL: https://issues.jboss.org/browse/JBTM-2832 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Zheng Feng > Priority: Minor > Fix For: 5.next > > Attachments: CIfailure.zip > > > [exec] 1) test: TestTPGetRply::test_tpgetrply_with_TPGETANY (F) line: 272 C:\hudson\workspace\narayana-catelyn\blacktie\xatmi\src\test\cpp\TestTPGetRply.cxx > [exec] assertion failed > [exec] - Expression: _w12pq_u > [exec] -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 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 September 2019