August 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2722) AtomicTransaction equals method is incorrect

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2722?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2722: -------------------------------- Fix Version/s: 5.next > AtomicTransaction equals method is incorrect > -------------------------------------------- > > Key: JBTM-2722 > URL: https://issues.jboss.org/browse/JBTM-2722 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.3.3.Final > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Fix For: 5.next > > > Method returns false even for equal objects. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2720) Allow the setting of an initial delay in PeriodRecovery

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2720?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2720: -------------------------------- Fix Version/s: 5.next > Allow the setting of an initial delay in PeriodRecovery > ------------------------------------------------------- > > Key: JBTM-2720 > URL: https://issues.jboss.org/browse/JBTM-2720 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Matthew Robson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently Periodic Recovery kicks off at the same interval on every server. As a domain mode cluster grows in size, this leads to significant contention in the DB, especially for RAC implementations. Completion time goes from milliseconds with 1 server to 20+ seconds with 20+ servers. > In an effort to avoid this, an offset the initial start of Periodic Recovery could be provided for the nodes in the cluster. > Periodic Recovery currently leverages 2 properties: > <system-properties> > <property name="RecoveryEnvironmentBean.periodicRecoveryPeriod" value="120"/> > <property name="RecoveryEnvironmentBean.recoveryBackoffPeriod" value="10"/> > </system-properties> > The proposal would be to add a 3rd property, 'RecoveryEnvironmentBean.periodicRecoveryInitilizationOffset' which, when set, would be used for each node. If not set, it would default to current behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2542?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2542: -------------------------------- Fix Version/s: 5.later (was: 5.next) > Migrate performance tests to the performance repo > ------------------------------------------------- > > Key: JBTM-2542 > URL: https://issues.jboss.org/browse/JBTM-2542 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > 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/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 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2724) Blacktie should not override maven-assembly-plugin version from parent

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2724?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2724: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Blacktie should not override maven-assembly-plugin version from parent > ---------------------------------------------------------------------- > > Key: JBTM-2724 > URL: https://issues.jboss.org/browse/JBTM-2724 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.3.3.Final > Environment: windows (http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/1089) > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > One of our PRs (http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/1089) ran on windows and failed due to a version issue with the maven-assembly-plugin. The blacktie/blacktie/pom.xml overrides the version set in the parent: > {quote} >  > <version>2.4</version> > {quote} > We should either retest without the version override or try to find another solution if the latest version of the plugin still has the same issue ([~zhfeng] are you aware of any alternative?). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2727) Add debug profile

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2727?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2727: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add debug profile > ----------------- > > Key: JBTM-2727 > URL: https://issues.jboss.org/browse/JBTM-2727 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Optional > Fix For: 5.next > > > Add debug profile to the main pom.xml to make it easier to debug arquillian tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2724) Blacktie should not override maven-assembly-plugin version from parent

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2724?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2724: ---------------------------- Fix Version/s: 5.next > Blacktie should not override maven-assembly-plugin version from parent > ---------------------------------------------------------------------- > > Key: JBTM-2724 > URL: https://issues.jboss.org/browse/JBTM-2724 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.3.3.Final > Environment: windows (http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/1089) > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > One of our PRs (http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/1089) ran on windows and failed due to a version issue with the maven-assembly-plugin. The blacktie/blacktie/pom.xml overrides the version set in the parent: > {quote} >  > <version>2.4</version> > {quote} > We should either retest without the version override or try to find another solution if the latest version of the plugin still has the same issue ([~zhfeng] are you aware of any alternative?). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2724) Blacktie should not override maven-assembly-plugin version from parent

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2724?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Amos Feng created pull request #1051 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Blacktie should not override maven-assembly-plugin version from parent > ---------------------------------------------------------------------- > > Key: JBTM-2724 > URL: https://issues.jboss.org/browse/JBTM-2724 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.3.3.Final > Environment: windows (http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/1089) > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > One of our PRs (http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/1089) ran on windows and failed due to a version issue with the maven-assembly-plugin. The blacktie/blacktie/pom.xml overrides the version set in the parent: > {quote} >  > <version>2.4</version> > {quote} > We should either retest without the version override or try to find another solution if the latest version of the plugin still has the same issue ([~zhfeng] are you aware of any alternative?). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2729) Upgrade the zip to 3.0 in the CI el5 servers

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2729?page=com.atlassian.jira.plugin.... ] Amos Feng resolved JBTM-2729. ----------------------------- Resolution: Done > Upgrade the zip to 3.0 in the CI el5 servers > -------------------------------------------- > > Key: JBTM-2729 > URL: https://issues.jboss.org/browse/JBTM-2729 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2729) Upgrade the zip to 3.0 in the CI el5 servers

by Amos Feng (JIRA)

Amos Feng created JBTM-2729: ------------------------------- Summary: Upgrade the zip to 3.0 in the CI el5 servers Key: JBTM-2729 URL: https://issues.jboss.org/browse/JBTM-2729 Project: JBoss Transaction Manager Issue Type: Task Components: BlackTie Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2724) Blacktie should not override maven-assembly-plugin version from parent

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2724?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2724: --------------------------------- It looks like we have to upgrade the zip from 2.31 to 3.0 in the el5 server. > Blacktie should not override maven-assembly-plugin version from parent > ---------------------------------------------------------------------- > > Key: JBTM-2724 > URL: https://issues.jboss.org/browse/JBTM-2724 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.3.3.Final > Environment: windows (http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/1089) > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Blocker > > One of our PRs (http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/1089) ran on windows and failed due to a version issue with the maven-assembly-plugin. The blacktie/blacktie/pom.xml overrides the version set in the parent: > {quote} >  > <version>2.4</version> > {quote} > We should either retest without the version override or try to find another solution if the latest version of the plugin still has the same issue ([~zhfeng] are you aware of any alternative?). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 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 August 2016