March 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3260) On publishing a new Narayana release there should be created Quarkus PR to update Narayana version

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-3260?page=com.atlassian.jira.plugin... ] Mayank Kunwar updated JBTM-3260: -------------------------------- Git Pull Request: https://github.com/quarkusio/quarkus/pull/7977 (was: https://github.com/jbosstm/narayana/pull/1569) > On publishing a new Narayana release there should be created Quarkus PR to update Narayana version > -------------------------------------------------------------------------------------------------- > > Key: JBTM-3260 > URL: https://issues.redhat.com/browse/JBTM-3260 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Affects Versions: 5.10.3.Final > Reporter: Ondrej Chaloupka > Assignee: Mayank Kunwar > Priority: Major > > As currently when a Narayana minor release is published it's usual to create a WildFly pull request which updates the Narayana version to the most up-to-date. > This functionality is automatized in the release script: > https://github.com/jbosstm/narayana/blob/5.10.4.Final/narayana-release-pr... > It would be good to have a similar functionality for the Quarkus. Narayana is the component managing JTA trasaction there and it would be good to pass there the newest version as well. > Narayana version could be updated at: > https://github.com/quarkusio/quarkus/blob/1.2.1.Final/bom/runtime/pom.xml... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3260) On publishing a new Narayana release there should be created Quarkus PR to update Narayana version

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-3260?page=com.atlassian.jira.plugin... ] Mayank Kunwar commented on JBTM-3260: ------------------------------------- Added Narayana dependencies to quarkus dependabot config.xml file. Here are the changes : https://github.com/quarkusio/quarkus/pull/7977 Dependabot will automatically raise PR with latest version changes, to quarkus repo, whenever publishing a new Narayana release. > On publishing a new Narayana release there should be created Quarkus PR to update Narayana version > -------------------------------------------------------------------------------------------------- > > Key: JBTM-3260 > URL: https://issues.redhat.com/browse/JBTM-3260 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Affects Versions: 5.10.3.Final > Reporter: Ondrej Chaloupka > Assignee: Mayank Kunwar > Priority: Major > > As currently when a Narayana minor release is published it's usual to create a WildFly pull request which updates the Narayana version to the most up-to-date. > This functionality is automatized in the release script: > https://github.com/jbosstm/narayana/blob/5.10.4.Final/narayana-release-pr... > It would be good to have a similar functionality for the Quarkus. Narayana is the component managing JTA trasaction there and it would be good to pass there the newest version as well. > Narayana version could be updated at: > https://github.com/quarkusio/quarkus/blob/1.2.1.Final/bom/runtime/pom.xml... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

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

by Anonymous (Jira)

[ https://issues.redhat.com/browse/JBTM-2440?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when pull request #883 was created in GitHub --------------------------------------------------------------------------------- Status: Pull Request Sent (was: Reopened) > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.redhat.com/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.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1965) Add support for XADisk

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-1965?page=com.atlassian.jira.plugin... ] Michael Musgrove closed JBTM-1965. ---------------------------------- Resolution: Out of Date XADisk used to be hosted at http://xadisk.java.net/ but the java.net site is now closed and does not appear to have been relocated to anywhere else. The last release was back in 2013 (https://mvnrepository.com/artifact/net.java.xadisk/xadisk) so it looks like it is no longer actively maintained. If the project ever becomes active again we can look at re-opening this issue. > Add support for XADisk > ---------------------- > > Key: JBTM-1965 > URL: https://issues.redhat.com/browse/JBTM-1965 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Affects Versions: 5.0.0.M5 > Reporter: Mark Little > Priority: Major > > Transactions are often used to structure activities within reliable software applications. In Java EE, business logic typically involves accessing transactional resource managers (databases, message queues) within boundaries denoted by calls to the JTA (begin/commit/rollback). The resource managers work with the transaction manager to perform e.g. locking, logging and recovery transparently to the application programmer. However, this separation of concerns is broken with regard to one important resource: the file system. Java's file I/O library does not support transactions, a situation which requires application programmers to implement such support manually in their programs. In this project you will develop a transaction aware resource manager for file I/O in Java. This library will provide application programmers with access to a filesystem that offers ACID semantics. > We already have a transactional file I/O implementation but there are now alternatives available. XADisk (https://xadisk.java.net/) seems to have a vibrant user community, so we should take a look at this. Part of the work will be to compare and contrast the options available. > To undertake this project you should have a good understanding of Java file I/O and some knowledge of transactions (ACID semantics and the JTA). The work will be open source. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-831) performance tweaks

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-831?page=com.atlassian.jira.plugin.... ] Michael Musgrove closed JBTM-831. --------------------------------- Resolution: Out of Date The items on this issue have already been fixed so I am closing as out of date: BeanPopulator.java: Class.getCanonicalName() is a) expensive and b) not cached. Use getName() instead, as bean lookup is frequent in places e.g. for isStatisticsEnabled. # BeanPopulator has already been changed to use getName() # Override equals/hashCode for ReaperElement, as we can outperform the defaults has already been changed (nb hashCode is implemented as_control.get_uid().hashCode() # And Override hashCode on BasicAction have already been changed to use the equals and hashCode methods provided by get_uid() (which is already optimised) > performance tweaks > ------------------ > > Key: JBTM-831 > URL: https://issues.redhat.com/browse/JBTM-831 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Jonathan Halliday > Assignee: Mark Little > Priority: Minor > > assorted performance tweaks -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-831) performance tweaks

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-831?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-831: ----------------------------------- I closed this accidentally. The issue does appear to be already fixed. > performance tweaks > ------------------ > > Key: JBTM-831 > URL: https://issues.redhat.com/browse/JBTM-831 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Jonathan Halliday > Assignee: Mark Little > Priority: Minor > > assorted performance tweaks -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-831) performance tweaks

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-831?page=com.atlassian.jira.plugin.... ] Michael Musgrove closed JBTM-831. --------------------------------- Resolution: Done > performance tweaks > ------------------ > > Key: JBTM-831 > URL: https://issues.redhat.com/browse/JBTM-831 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Jonathan Halliday > Assignee: Mark Little > Priority: Minor > > assorted performance tweaks -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3197) Include an STM quickstart running on Quarkus (including native mode)

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3197?page=com.atlassian.jira.plugin... ] Michael Musgrove closed JBTM-3197. ---------------------------------- Resolution: Duplicate Issue There is already a quickstart for this task in the quarkus repo: https://github.com/quarkusio/quarkus-quickstarts/tree/master/software-tra... Note also that there is a forum thread that asks for a different STM + quarkus quickstart (https://developer.jboss.org/thread/280692). > Include an STM quickstart running on Quarkus (including native mode) > -------------------------------------------------------------------- > > Key: JBTM-3197 > URL: https://issues.redhat.com/browse/JBTM-3197 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator, Quickstarts, STM > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Add a quickstart that shows how to create an STM example running on Quarkus. The quickstart should also include instructions for building a native executable. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2542) Migrate performance tests to the performance repo

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-2542?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-2542: ----------------------------------- Description: We still have lots of performance related unit tests that need migrating: rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceDefaultUnitTest.java ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceVolatileUnitTest.java ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceVolatileUnitTest.java ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceDefaultUnitTest.java ArjunaJTA/jta/tests/classes/com/hp/mwtests/ts/jta/commitmarkable/PerformanceTestCommitMarkableResource.java ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance1.java ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance2.java ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance4.java ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance3.java ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/PerfHammer.java ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/GridWorker.java ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/local/synchronizations/Performance.java was: We still have lots of performance related unit tests that need migrating: rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceDefaultUnitTest.java ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceVolatileUnitTest.java ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceVolatileUnitTest.java ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceDefaultUnitTest.java ArjunaJTA/jta/tests/classes/com/hp/mwtests/ts/jta/commitmarkable/PerformanceTestCommitMarkableResource.java ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance1.java ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance2.java ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance4.java ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance3.java ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance1.java ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance2.java ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance3.java ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/PerfHammer.java ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/GridWorker.java ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/local/synchronizations/Performance.java ArjunaJTA/jta/tests/classes/io/narayana/perf/product/Product.java ArjunaJTA/jta/tests/classes/io/narayana/perf/product/ProductWorker.java > Migrate performance tests to the performance repo > ------------------------------------------------- > > Key: JBTM-2542 > URL: https://issues.redhat.com/browse/JBTM-2542 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Attachments: config.xml, eap-cmp-config.xml > > > We still have lots of performance related unit tests that need migrating: > rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceDefaultUnitTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceVolatileUnitTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceVolatileUnitTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceDefaultUnitTest.java > ArjunaJTA/jta/tests/classes/com/hp/mwtests/ts/jta/commitmarkable/PerformanceTestCommitMarkableResource.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance1.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance2.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance4.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance3.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/PerfHammer.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/GridWorker.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/local/synchronizations/Performance.java -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3137) Too much variance in the performance PR checker

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3137?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3137: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Too much variance in the performance PR checker > ----------------------------------------------- > > Key: JBTM-3137 > URL: https://issues.redhat.com/browse/JBTM-3137 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Mayank Kunwar > Priority: Major > Fix For: 5.next > > > The PERF axis of the PR checker job runs some tests to validate that the PR does not introduce any regressions but the axis is not useful since there is too much variance in the runs. For example PR https://github.com/jbosstm/narayana/pull/1437 ran 3 times each producing wildly different results. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2020