April 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2647) Extend compensations BAControler to allow enlistment of handlers by instance

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2647?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2647: ---------------------------------- Fix Version/s: 5.next (was: 5.3.2.Final) > Extend compensations BAControler to allow enlistment of handlers by instance > ---------------------------------------------------------------------------- > > Key: JBTM-2647 > URL: https://issues.jboss.org/browse/JBTM-2647 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently BAControler allows enlistment of handler only by class. It later creates instances using those classes when finishing the compensating transaction. Because of that it should be easy to allow enlisting of instances. This would allow using labdas when implementing handlers. Also instance could carry some extra information needed to compensate the transaction. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2650) Remove typo from BAControler interface and its implementations

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2650?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2650: ---------------------------------- Fix Version/s: 5.next (was: 5.3.2.Final) > Remove typo from BAControler interface and its implementations > -------------------------------------------------------------- > > Key: JBTM-2650 > URL: https://issues.jboss.org/browse/JBTM-2650 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Fix typos in BAControler, LocalBAControler, and RemoteBAControler names. Also variables when those classes are used also have typos. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2648) Failing .Narayana qa testcase crashrecovery12 method CrashRecovery12_Test03 when journal object store is used

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2648?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2648: ---------------------------------- Fix Version/s: 5.next (was: 5.3.2.Final) > Failing .Narayana qa testcase crashrecovery12 method CrashRecovery12_Test03 when journal object store is used > ------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2648 > URL: https://issues.jboss.org/browse/JBTM-2648 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.14.Final > Reporter: Ondřej Chaloupka > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: TEST-org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12.txt, testoutput.zip > > > When using journal object store (amq) then we experience failues of test {{crashrecovery12 CrashRecovery12_Test03}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2298) Write an atomic app that uses JTS and JacORB containers

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2298. --------------------------------- > Write an atomic app that uses JTS and JacORB containers > ------------------------------------------------------- > > Key: JBTM-2298 > URL: https://issues.jboss.org/browse/JBTM-2298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.3.2.Final > > > When I created the initial docker (POC) image I did so using a standard Fedora base image. We should also look at supporting the Project Atomic docker image, since it's important for Red Hat. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2626. --------------------------------- > 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.3.2.Final > > 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, 8 months

1
0
0 / 0

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2633?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2633. --------------------------------- > 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 > Fix For: 5.3.2.Final > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2638) Initiate connection in JmsXAResourceRecoveryHelper.getXAResources instead of recover

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2638?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2638. --------------------------------- > Initiate connection in JmsXAResourceRecoveryHelper.getXAResources instead of recover > ------------------------------------------------------------------------------------ > > Key: JBTM-2638 > URL: https://issues.jboss.org/browse/JBTM-2638 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.3.2.Final > > > Initially I've added assertions in JmsXAResourceRecoveryHelper to check if the recovery scan was started and delegate was initialised. However, XARecoveryModule only catches XAException, so if assertion fails periodic recovery cannot handle it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2649) Inconsistent behavior of journal object store for heuristic state

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2649?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2649. --------------------------------- > Inconsistent behavior of journal object store for heuristic state > ----------------------------------------------------------------- > > Key: JBTM-2649 > URL: https://issues.jboss.org/browse/JBTM-2649 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.2.15.Final, 5.3.2.Final > > > We do experience inconsistent behavior of journal object store (amq) against shadow store. This starts to happen from EAP7/Narayana 5.2.14.Final. > Our test case: > * enlist activemq JMS resource > * enlist test XA resource > * prepare JMS resource > * prepare test XA resource > * commit JMS resource > * commit test XA resource > ** byteman force {{topLevelCommit}} to return {{XAException.XA_HEURRB}} > 2PC result for XA resource is {{TwoPhaseOutcome.HEURISTIC_HAZARD}} and client gets {{javax.transaction.HeuristicMixedException}} > * probing log and showing state of transactions {{/subsystem=transactions/log-store=log-store:probe}} > ** expecting one indoubt participant in HEURISTIC state > * calling operation {{recovery}} on all transaction's participants > * do recovery > This works fine when Shadow log store or jdbc object store is used. For AMQ object log store the participant is first not in HEURISTIC state but is in state PREPARED. And second there is not only one participant of transaction in-doubt but they're returned two participants. > Then during recovery process the periodic recovery also can see two participants for recovery (that's my feeling from log). Not only one as expected as first resource was already correctly committed (that's how shadow log store works). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2640) Add username and password to JmsXAResourceRecoveryHelper

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2640?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2640. --------------------------------- > Add username and password to JmsXAResourceRecoveryHelper > -------------------------------------------------------- > > Key: JBTM-2640 > URL: https://issues.jboss.org/browse/JBTM-2640 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.3.2.Final > > > In some scenarios user name and password might be needed during the recovery of JMS resources. For those cases JmsXAResourceRecoveryHelper should be able to take username and password as an argument and use them when creating connections. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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