November 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2551) CrashRecovery02_1_Test05 failure on IPv6

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2551?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2551: ----------------------------------- Attachment: CrashRecovery02_1_Test05.tar output and traces for the failing test > CrashRecovery02_1_Test05 failure on IPv6 > ---------------------------------------- > > Key: JBTM-2551 > URL: https://issues.jboss.org/browse/JBTM-2551 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.7.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Attachments: CrashRecovery02_1_Test05.tar > > > We had a single failure in the JacORB qa test run on the job: > http://172.17.130.4:8083/job/narayana-dualstack/66 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2551) CrashRecovery02_1_Test05 failure on IPv6

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2551: -------------------------------------- Summary: CrashRecovery02_1_Test05 failure on IPv6 Key: JBTM-2551 URL: https://issues.jboss.org/browse/JBTM-2551 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Affects Versions: 5.2.7.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 5.next We had a single failure in the JacORB qa test run on the job: http://172.17.130.4:8083/job/narayana-dualstack/66 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2544) RTS inbound bridge recovery does not work with JTS

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2544?page=com.atlassian.jira.plugin.... ] Work on JBTM-2544 started by Gytis Trikleris. --------------------------------------------- > RTS inbound bridge recovery does not work with JTS > -------------------------------------------------- > > Key: JBTM-2544 > URL: https://issues.jboss.org/browse/JBTM-2544 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > If JTS is enabled, crash scenario when system fails just before the commit does not complete correctly. Instead of being committed, resource is rolled back by XARecoveryModule. > In JTA case, XARecoveryModule does not find any XAResourceRecords and bridge recovery is handled by InboundBridgeRecoveryModule. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2532) Enable code coverage for XTS

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2532?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2532: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/937 > Enable code coverage for XTS > ---------------------------- > > Key: JBTM-2532 > URL: https://issues.jboss.org/browse/JBTM-2532 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2538) Benchmarking failure

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2538?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2538: ---------------------------------------- I forgot to push part of the fix (disables carol trace logging which is not thread safe). I have pushed commit b186643 and restarted the job > Benchmarking failure > -------------------- > > Key: JBTM-2538 > URL: https://issues.jboss.org/browse/JBTM-2538 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2550) ClassNotFoundException when restore_state from the object store during recovering

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2550: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/935 > ClassNotFoundException when restore_state from the object store during recovering > --------------------------------------------------------------------------------- > > Key: JBTM-2550 > URL: https://issues.jboss.org/browse/JBTM-2550 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.next > > > This exception happens with using the IBM MQ rar in the wildfly. > com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR. Now we catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2550) ClassNotFoundException when restore_state from the object store during recovering

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2550: ---------------------------- Component/s: Recovery > ClassNotFoundException when restore_state from the object store during recovering > --------------------------------------------------------------------------------- > > Key: JBTM-2550 > URL: https://issues.jboss.org/browse/JBTM-2550 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.next > > > This exception happens with using the IBM MQ rar in the wildfly. > com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR. Now we catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2550) ClassNotFoundException when restore_state from the object store during recovering

by Amos Feng (JIRA)

Amos Feng created JBTM-2550: ------------------------------- Summary: ClassNotFoundException when restore_state from the object store during recovering Key: JBTM-2550 URL: https://issues.jboss.org/browse/JBTM-2550 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Amos Feng Assignee: Amos Feng Priority: Critical Fix For: 5.next This exception happens with using the IBM MQ rar in the wildfly. com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR. Now we catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2550) ClassNotFoundException when restore_state from the object store during recovering

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2550: ---------------------------- Steps to Reproduce: (was: This exception happens with using the IBM MQ rar in the wildfly. com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR. Now we catch this exception and try to get from the helpers.) > ClassNotFoundException when restore_state from the object store during recovering > --------------------------------------------------------------------------------- > > Key: JBTM-2550 > URL: https://issues.jboss.org/browse/JBTM-2550 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.next > > > This exception happens with using the IBM MQ rar in the wildfly. > com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR. Now we catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2547) CrashRecovery02_2_Test01 failure

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2547?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2547: ----------------------------------- Summary: CrashRecovery02_2_Test01 failure (was: CrashRecovery02_2_Test01 failure) > CrashRecovery02_2_Test01 failure > --------------------------------- > > Key: JBTM-2547 > URL: https://issues.jboss.org/browse/JBTM-2547 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.7.Final > Environment: Run the QA testsuite using the JdkORB > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The root cause of the failure is that StatusChecker#getStatus gets a different exception when trying to obtain the transaction status. With JacORB it gets OBJECT_NOT_EXIST but with JdkORB orb it gets CORBA.BAD_OPERATION. In the former case we assume that the original transaction is dead and get a fresh one to do recovery on. In the later case we log the error and abort the replay attempt. > The recommended fix is to mark the original as dead when we get CORBA.BAD_OPERATION when doing the status lookup. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2015