March 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2634) Create Narayana Spring Boot starter quickstart

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2634?page=com.atlassian.jira.plugin.... ] Work on JBTM-2634 started by Gytis Trikleris. --------------------------------------------- > Create Narayana Spring Boot starter quickstart > ---------------------------------------------- > > Key: JBTM-2634 > URL: https://issues.jboss.org/browse/JBTM-2634 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Create a demonstrator application for Narayana Spring Boot starter before raising pull request to Spring. This would allow to make a better review of the Narayana Spring Boot integration on the forum. > Quickstart should have a simple example of JTA and crash recovery. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2634) Create Narayana Spring Boot starter quickstart

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2634: ------------------------------------- Summary: Create Narayana Spring Boot starter quickstart Key: JBTM-2634 URL: https://issues.jboss.org/browse/JBTM-2634 Project: JBoss Transaction Manager Issue Type: Sub-task Components: Demonstrator, JTA Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next Create a demonstrator application for Narayana Spring Boot starter before raising pull request to Spring. This would allow to make a better review of the Narayana Spring Boot integration on the forum. Quickstart should have a simple example of JTA and crash recovery. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2626) Journal Store QA test failures

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2626. --------------------------------- Resolution: Done > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: jstack.25002.jacorb > > > There was a single test failure on each of the following CI runs: > crashrecovery05_2 CrashRecovery05_2_Test080 failed on the idlj run on the jobs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA... > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS... > and jtatests01 JTATests01_Test006 failed on the jacorb run of job: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2626) Journal Store QA test failures

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2626: ----------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: jstack.25002.jacorb > > > There was a single test failure on each of the following CI runs: > crashrecovery05_2 CrashRecovery05_2_Test080 failed on the idlj run on the jobs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA... > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS... > and jtatests01 JTATests01_Test006 failed on the jacorb run of job: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2626) Journal Store QA test failures

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.... ] Work on JBTM-2626 started by Tom Jenkinson. ------------------------------------------- > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Fix For: 5.next > > Attachments: jstack.25002.jacorb > > > There was a single test failure on each of the following CI runs: > crashrecovery05_2 CrashRecovery05_2_Test080 failed on the idlj run on the jobs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA... > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS... > and jtatests01 JTATests01_Test006 failed on the jacorb run of job: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2633) Arquillian server startup timeout should be configurable in tests

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2633?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondřej Chaloupka created pull request #987 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Arquillian server startup timeout should be configurable in tests > ----------------------------------------------------------------- > > Key: JBTM-2633 > URL: https://issues.jboss.org/browse/JBTM-2633 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.2.14.Final > Reporter: Ondřej Chaloupka > Assignee: Ondřej Chaloupka > > Arquillian configuration for tests which lays in _arquillian.xml_ currently does not permit changing timeou for server startup. Default timeout for server startup is 60 seconds. If server is not up and running till that time Arquillian stops the serve process and {{LifecycleException}} is thrown informing that server was not started. > If tests (like txbridge or xts) are run with container which uses _jdbc object store_ and connection to database is slow. It could happen that 60 seconds is not enough for serve being started and tests start to fail. The easy solution is to wait a bit more for server would be started. > Then add configuration property {{startupTimeoutInSeconds}} to {{arquillian.xml}} files which are configured to start jboss/wildfly server and let user to configure the option. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2633) Arquillian server startup timeout should be configurable in tests

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created JBTM-2633: -------------------------------------- Summary: Arquillian server startup timeout should be configurable in tests Key: JBTM-2633 URL: https://issues.jboss.org/browse/JBTM-2633 Project: JBoss Transaction Manager Issue Type: Task Components: Testing Affects Versions: 5.2.14.Final Reporter: Ondřej Chaloupka Assignee: Ondřej Chaloupka Arquillian configuration for tests which lays in _arquillian.xml_ currently does not permit changing timeou for server startup. Default timeout for server startup is 60 seconds. If server is not up and running till that time Arquillian stops the serve process and {{LifecycleException}} is thrown informing that server was not started. If tests (like txbridge or xts) are run with container which uses _jdbc object store_ and connection to database is slow. It could happen that 60 seconds is not enough for serve being started and tests start to fail. The easy solution is to wait a bit more for server would be started. Then add configuration property {{startupTimeoutInSeconds}} to {{arquillian.xml}} files which are configured to start jboss/wildfly server and let user to configure the option. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2632?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2632: -------------------------------- Fix Version/s: 5.next > Allow the setting of an initial delay in PeriodRecovery > ------------------------------------------------------- > > Key: JBTM-2632 > URL: https://issues.jboss.org/browse/JBTM-2632 > 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)

8 years, 1 month

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2632?page=com.atlassian.jira.plugin.... ] Tom Jenkinson moved JBEAP-3667 to JBTM-2632: -------------------------------------------- Project: JBoss Transaction Manager (was: JBoss Enterprise Application Platform) Key: JBTM-2632 (was: JBEAP-3667) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Recovery (was: Transactions) Target Release: (was: 7.backlog.GA) Affects Version/s: (was: 7.backlog.GA) > Allow the setting of an initial delay in PeriodRecovery > ------------------------------------------------------- > > Key: JBTM-2632 > URL: https://issues.jboss.org/browse/JBTM-2632 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Matthew Robson > Assignee: Tom Jenkinson > > 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)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1804: ---------------------------------- Fix Version/s: 5.next (was: 5.3.1.Final) > JTS remote tests not run and no code coverage > --------------------------------------------- > > Key: JBTM-1804 > URL: https://issues.jboss.org/browse/JBTM-1804 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build. > It would then be beneficial to have them instrumented by emma to get code coverage. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 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 2016