From issues at jboss.org Mon Nov 2 11:02:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 2 Nov 2015 11:02:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2547) CrashRecovery02_2_Test01 failure In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2547: -------------------------------------- Summary: 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) From issues at jboss.org Mon Nov 2 11:16:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 2 Nov 2015 11:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2548) CrashRecovery05_2_Test076 (through CrashRecovery05_2_Test100) failures In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2548: -------------------------------------- Summary: CrashRecovery05_2_Test076 (through CrashRecovery05_2_Test100) failures Key: JBTM-2548 URL: https://issues.jboss.org/browse/JBTM-2548 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Affects Versions: 5.2.7.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next These tests typically start 2 servers and crash one of them in various ways. Then the two servers are restarted but the tests fail because the recovery port used by one of the two servers is stuck in the TIME-WAIT state so the server restart gets a "Bind: Address Already in Use" error. I propose to fix this by doing a retry and backoff approach. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 2 11:54:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 2 Nov 2015 11:54:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2549) CrashRecovery05_2_Test002 failure In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2549: -------------------------------------- Summary: CrashRecovery05_2_Test002 failure Key: JBTM-2549 URL: https://issues.jboss.org/browse/JBTM-2549 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Affects Versions: 5.2.7.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next There are a number of failures in the CrashRecovery05_1 and CrashRecovery05_2 test groups with a similar root cause: Tests that use AfterCrashServiceImpl01#check_oper and AfterCrashServiceImpl02#check_oper with JdkORB fail because they make invalid assumptions about the return value of RecoveryCoordinator#replay_completion. The OTS spec says "This (replay_completion) non-blocking operation returns the current status of the transaction" but the check_oper() test assumes that the return value represents the transaction status after all resources have been replayed and therefore returns the wrong result to the requesting client. The fix is to ask the resources for their status after the replay_completion attempt (but also waiting for the resource to have been replayed). I tested the hypothesis by forcing a 200ms wait after issuing replay_completion on the RecoveryCoordinator object (but I will use a rendezvous for the actual fix). There is a second problem with the way these tests are coded since they ignore the fact that replay_completion reruns phase 2 on all resources whereas the test relies on it being done on only the requested resource). A test sequence is as follows: # client starts a transaction # asks service1 to create a resource1 # asks service2 to create a resource2 # client commits the transaction (one of which crashes during 2PC) # restart the server (hosting the services) # client asks service1 for the status of the first resource # service1 invokes replay_completion on the RecoveryCoordinator for resource1 # this causes a recovery attempt on both resources # client asks service2 for the status of the second resource # service2 invokes replay_completion on the RecoveryCoordinator for resource2 # but this will fail because the transaction was completed during steps 7 and 8 so the # transaction log no longer exists and the recovery attempt calls rollback on resource2 The fix is to store the transaction Status with the resources and have the service ask the resources for the state (rather than the return value of the replay_completion request). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 3 06:29:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 3 Nov 2015 06:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2548) CrashRecovery05_2_Test076 (through CrashRecovery05_2_Test100) failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124694#comment-13124694 ] Michael Musgrove commented on JBTM-2548: ---------------------------------------- These test failures also require the fix provided by JBTM-2547 > CrashRecovery05_2_Test076 (through CrashRecovery05_2_Test100) failures > ---------------------------------------------------------------------- > > Key: JBTM-2548 > URL: https://issues.jboss.org/browse/JBTM-2548 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.7.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > These tests typically start 2 servers and crash one of them in various ways. > Then the two servers are restarted but the tests fail because the recovery port used by one of the two servers is stuck in the TIME-WAIT state so the server restart gets a "Bind: Address Already in Use" error. > I propose to fix this by doing a retry and backoff approach. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 3 08:06:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 3 Nov 2015 08:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2547) CrashRecovery02_2_Test01 failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Nov 4 03:06:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 4 Nov 2015 03:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) ClassNotFoundException when restore_state from the object store during recovering In-Reply-To: References: Message-ID: 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) From issues at jboss.org Wed Nov 4 03:06:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 4 Nov 2015 03:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) ClassNotFoundException when restore_state from the object store during recovering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Nov 4 03:07:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 4 Nov 2015 03:07:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) ClassNotFoundException when restore_state from the object store during recovering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Nov 4 03:56:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 4 Nov 2015 03:56:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) ClassNotFoundException when restore_state from the object store during recovering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Nov 4 07:33:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 4 Nov 2015 07:33:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2538) Benchmarking failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125337#comment-13125337 ] 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) From issues at jboss.org Thu Nov 5 09:58:01 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 5 Nov 2015 09:58:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2532) Enable code coverage for XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Thu Nov 5 10:21:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 5 Nov 2015 10:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2544) RTS inbound bridge recovery does not work with JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Fri Nov 6 05:15:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 05:15:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2551) CrashRecovery02_1_Test05 failure on IPv6 In-Reply-To: References: Message-ID: 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) From issues at jboss.org Fri Nov 6 05:16:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 05:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2551) CrashRecovery02_1_Test05 failure on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Fri Nov 6 06:18:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 06:18:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2538) Benchmarking failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2538: ----------------------------------- Git Pull Request: https://github.com/jbosstm/performance/pull/25, https://github.com/jbosstm/performance/pull/27 (was: https://github.com/jbosstm/performance/pull/25) > 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) From issues at jboss.org Fri Nov 6 06:54:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 06:54:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2538) Benchmarking failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2538: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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) From issues at jboss.org Fri Nov 6 06:56:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 06:56:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2534) HQStore crashrec failures on QA_JTS_JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2534: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/936 > HQStore crashrec failures on QA_JTS_JDKORB > ------------------------------------------ > > Key: JBTM-2534 > URL: https://issues.jboss.org/browse/JBTM-2534 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > Killed this one: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/127/ > Normally run to completion but lots of crash rec failures: > {quote} > Total time: 525 minutes 19 seconds > Test Failures: > crashrecovery02_2 CrashRecovery02_2_Test01 Fail (0m50.031s) > crashrecovery02_2 CrashRecovery02_2_Test06 Fail (0m43.914s) > crashrecovery02_2 CrashRecovery02_2_Test07 Fail (0m48.270s) > crashrecovery02_2 CrashRecovery02_2_Test08 Fail (0m48.340s) > crashrecovery02_2 CrashRecovery02_2_Test09 Fail (0m48.014s) > crashrecovery02_2 CrashRecovery02_2_Test10 Fail (0m47.865s) > crashrecovery02_2 CrashRecovery02_2_Test11 Fail (0m48.756s) > crashrecovery02_2 CrashRecovery02_2_Test12 Fail (0m47.992s) > crashrecovery02_2 CrashRecovery02_2_Test13 Fail (0m47.840s) > crashrecovery02_2 CrashRecovery02_2_Test14 Fail (0m47.948s) > crashrecovery02_2 CrashRecovery02_2_Test15 Fail (0m47.742s) > crashrecovery02_2 CrashRecovery02_2_Test16 Fail (0m48.953s) > crashrecovery02_2 CrashRecovery02_2_Test02 Fail (0m48.202s) > crashrecovery02_2 CrashRecovery02_2_Test03 Fail (2m3.776s) > crashrecovery02_2 CrashRecovery02_2_Test04 Fail (0m47.686s) > crashrecovery02_2 CrashRecovery02_2_Test05 Fail (0m47.859s) > crashrecovery02_2 CrashRecovery02_2_Test17 Fail (0m48.029s) > crashrecovery02_2 CrashRecovery02_2_Test18 Fail (0m47.658s) > crashrecovery02_2 CrashRecovery02_2_Test19 Fail (0m47.775s) > crashrecovery02_2 CrashRecovery02_2_Test20 Fail (0m48.086s) > crashrecovery02_2 CrashRecovery02_2_Test21 Fail (0m47.979s) > crashrecovery02_2 CrashRecovery02_2_Test22 Fail (0m48.137s) > crashrecovery02_2 CrashRecovery02_2_Test23 Fail (0m48.267s) > crashrecovery02_2 CrashRecovery02_2_Test24 Fail (0m48.100s) > crashrecovery02_2 CrashRecovery02_2_Test25 Fail (0m47.787s) > crashrecovery05_1 CrashRecovery05_1_Test01 Fail (1m17.781s) > crashrecovery05_1 CrashRecovery05_1_Test10 Fail (1m18.510s) > crashrecovery05_1 CrashRecovery05_1_Test06 Fail (1m17.647s) > crashrecovery05_1 CrashRecovery05_1_Test07 Fail (1m17.572s) > crashrecovery05_1 CrashRecovery05_1_Test08 Fail (1m17.365s) > crashrecovery05_1 CrashRecovery05_1_Test09 Fail (1m17.263s) > crashrecovery05_2 CrashRecovery05_2_Test051 Fail (2m3.491s) > crashrecovery05_2 CrashRecovery05_2_Test052 Fail (0m48.481s) > crashrecovery05_2 CrashRecovery05_2_Test053 Fail (2m3.698s) > crashrecovery05_2 CrashRecovery05_2_Test054 Fail (0m47.293s) > crashrecovery05_2 CrashRecovery05_2_Test055 Fail (0m48.382s) > crashrecovery05_2 CrashRecovery05_2_Test056 Fail (0m43.458s) > crashrecovery05_2 CrashRecovery05_2_Test057 Fail (0m49.076s) > crashrecovery05_2 CrashRecovery05_2_Test058 Fail (0m43.988s) > crashrecovery05_2 CrashRecovery05_2_Test059 Fail (0m48.177s) > crashrecovery05_2 CrashRecovery05_2_Test060 Fail (0m47.995s) > crashrecovery05_2 CrashRecovery05_2_Test061 Fail (0m48.266s) > crashrecovery05_2 CrashRecovery05_2_Test062 Fail (0m47.852s) > crashrecovery05_2 CrashRecovery05_2_Test063 Fail (2m3.059s) > crashrecovery05_2 CrashRecovery05_2_Test064 Fail (0m47.332s) > crashrecovery05_2 CrashRecovery05_2_Test065 Fail (0m47.226s) > crashrecovery05_2 CrashRecovery05_2_Test066 Fail (0m47.141s) > crashrecovery05_2 CrashRecovery05_2_Test067 Fail (0m47.195s) > crashrecovery05_2 CrashRecovery05_2_Test068 Fail (0m47.464s) > crashrecovery05_2 CrashRecovery05_2_Test069 Fail (0m49.360s) > crashrecovery05_2 CrashRecovery05_2_Test070 Fail (0m47.700s) > crashrecovery05_2 CrashRecovery05_2_Test071 Fail (0m47.782s) > crashrecovery05_2 CrashRecovery05_2_Test072 Fail (0m47.736s) > crashrecovery05_2 CrashRecovery05_2_Test073 Fail (0m47.438s) > crashrecovery05_2 CrashRecovery05_2_Test074 Fail (0m47.701s) > crashrecovery05_2 CrashRecovery05_2_Test075 Fail (0m47.385s) > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m10.036s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m54.372s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m10.928s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m55.124s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m54.970s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m50.656s) > crashrecovery05_2 CrashRecovery05_2_Test082 Fail (0m54.356s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m50.052s) > crashrecovery05_2 CrashRecovery05_2_Test084 Fail (0m53.605s) > crashrecovery05_2 CrashRecovery05_2_Test085 Fail (0m54.694s) > crashrecovery05_2 CrashRecovery05_2_Test086 Fail (0m54.147s) > crashrecovery05_2 CrashRecovery05_2_Test087 Fail (0m54.397s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m11.261s) > crashrecovery05_2 CrashRecovery05_2_Test089 Fail (0m54.332s) > crashrecovery05_2 CrashRecovery05_2_Test090 Fail (0m55.264s) > crashrecovery05_2 CrashRecovery05_2_Test091 Fail (0m54.471s) > crashrecovery05_2 CrashRecovery05_2_Test092 Fail (0m54.046s) > crashrecovery05_2 CrashRecovery05_2_Test093 Fail (0m54.249s) > crashrecovery05_2 CrashRecovery05_2_Test094 Fail (0m54.388s) > crashrecovery05_2 CrashRecovery05_2_Test095 Fail (0m53.763s) > crashrecovery05_2 CrashRecovery05_2_Test096 Fail (0m54.313s) > crashrecovery05_2 CrashRecovery05_2_Test097 Fail (0m54.069s) > crashrecovery05_2 CrashRecovery05_2_Test098 Fail (0m54.290s) > crashrecovery05_2 CrashRecovery05_2_Test099 Fail (0m55.164s) > crashrecovery05_2 CrashRecovery05_2_Test100 Fail (0m54.189s) > crashrecovery05_2 CrashRecovery05_2_Test002 Fail (0m46.793s) > crashrecovery05_2 CrashRecovery05_2_Test003 Fail (2m2.944s) > crashrecovery05_2 CrashRecovery05_2_Test005 Fail (0m46.742s) > crashrecovery05_2 CrashRecovery05_2_Test006 Fail (0m42.978s) > crashrecovery05_2 CrashRecovery05_2_Test028 Fail (2m9.683s) > crashrecovery05_2 CrashRecovery05_2_Test031 Fail (0m49.745s) > crashrecovery12 CrashRecovery12_Test03 Fail (0m15.884s) > Buildfile: /home/hudson/workspace/narayana-hqstore/PROFILE/QA_JTS_JDKORB/jdk/jdk8.latest/label/linux/qa/run-tests.xml > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 6 06:57:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 06:57:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2547) CrashRecovery02_2_Test01 failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2547: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/936 > 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) From issues at jboss.org Fri Nov 6 06:57:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 06:57:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2547) CrashRecovery02_2_Test01 failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2547: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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) From issues at jboss.org Fri Nov 6 06:58:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 06:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2548) CrashRecovery05_2_Test076 (through CrashRecovery05_2_Test100) failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2548: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/936 > CrashRecovery05_2_Test076 (through CrashRecovery05_2_Test100) failures > ---------------------------------------------------------------------- > > Key: JBTM-2548 > URL: https://issues.jboss.org/browse/JBTM-2548 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.7.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > These tests typically start 2 servers and crash one of them in various ways. > Then the two servers are restarted but the tests fail because the recovery port used by one of the two servers is stuck in the TIME-WAIT state so the server restart gets a "Bind: Address Already in Use" error. > I propose to fix this by doing a retry and backoff approach. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 6 06:58:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 06:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2549) CrashRecovery05_2_Test002 failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2549: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/936 > CrashRecovery05_2_Test002 failure > --------------------------------- > > Key: JBTM-2549 > URL: https://issues.jboss.org/browse/JBTM-2549 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.7.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > There are a number of failures in the CrashRecovery05_1 and CrashRecovery05_2 test groups with a similar root cause: > Tests that use AfterCrashServiceImpl01#check_oper and AfterCrashServiceImpl02#check_oper with JdkORB fail because they make invalid assumptions about the return value of RecoveryCoordinator#replay_completion. The OTS spec says "This (replay_completion) non-blocking operation returns the current status of the transaction" but the check_oper() test assumes that the return value represents the transaction status after all resources have been replayed and therefore returns the wrong result to the requesting client. The fix is to ask the resources for their status after the replay_completion attempt (but also waiting for the resource to have been replayed). I tested the hypothesis by forcing a 200ms wait after issuing replay_completion on the RecoveryCoordinator object (but I will use a rendezvous for the actual fix). > There is a second problem with the way these tests are coded since they ignore the fact that replay_completion reruns phase 2 on all resources whereas the test relies on it being done on only the requested resource). A test sequence is as follows: > # client starts a transaction > # asks service1 to create a resource1 > # asks service2 to create a resource2 > # client commits the transaction (one of which crashes during 2PC) > # restart the server (hosting the services) > # client asks service1 for the status of the first resource > # service1 invokes replay_completion on the RecoveryCoordinator for resource1 > # this causes a recovery attempt on both resources > # client asks service2 for the status of the second resource > # service2 invokes replay_completion on the RecoveryCoordinator for resource2 > # but this will fail because the transaction was completed during steps 7 and 8 so the > # transaction log no longer exists and the recovery attempt calls rollback on resource2 > The fix is to store the transaction Status with the resources and have the service ask the resources for the state (rather than the return value of the replay_completion request). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 6 06:58:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 06:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2548) CrashRecovery05_2_Test076 (through CrashRecovery05_2_Test100) failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2548: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CrashRecovery05_2_Test076 (through CrashRecovery05_2_Test100) failures > ---------------------------------------------------------------------- > > Key: JBTM-2548 > URL: https://issues.jboss.org/browse/JBTM-2548 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.7.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > These tests typically start 2 servers and crash one of them in various ways. > Then the two servers are restarted but the tests fail because the recovery port used by one of the two servers is stuck in the TIME-WAIT state so the server restart gets a "Bind: Address Already in Use" error. > I propose to fix this by doing a retry and backoff approach. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 6 06:58:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 06:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2549) CrashRecovery05_2_Test002 failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2549: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CrashRecovery05_2_Test002 failure > --------------------------------- > > Key: JBTM-2549 > URL: https://issues.jboss.org/browse/JBTM-2549 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.7.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > There are a number of failures in the CrashRecovery05_1 and CrashRecovery05_2 test groups with a similar root cause: > Tests that use AfterCrashServiceImpl01#check_oper and AfterCrashServiceImpl02#check_oper with JdkORB fail because they make invalid assumptions about the return value of RecoveryCoordinator#replay_completion. The OTS spec says "This (replay_completion) non-blocking operation returns the current status of the transaction" but the check_oper() test assumes that the return value represents the transaction status after all resources have been replayed and therefore returns the wrong result to the requesting client. The fix is to ask the resources for their status after the replay_completion attempt (but also waiting for the resource to have been replayed). I tested the hypothesis by forcing a 200ms wait after issuing replay_completion on the RecoveryCoordinator object (but I will use a rendezvous for the actual fix). > There is a second problem with the way these tests are coded since they ignore the fact that replay_completion reruns phase 2 on all resources whereas the test relies on it being done on only the requested resource). A test sequence is as follows: > # client starts a transaction > # asks service1 to create a resource1 > # asks service2 to create a resource2 > # client commits the transaction (one of which crashes during 2PC) > # restart the server (hosting the services) > # client asks service1 for the status of the first resource > # service1 invokes replay_completion on the RecoveryCoordinator for resource1 > # this causes a recovery attempt on both resources > # client asks service2 for the status of the second resource > # service2 invokes replay_completion on the RecoveryCoordinator for resource2 > # but this will fail because the transaction was completed during steps 7 and 8 so the > # transaction log no longer exists and the recovery attempt calls rollback on resource2 > The fix is to store the transaction Status with the resources and have the service ask the resources for the state (rather than the return value of the replay_completion request). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 6 07:00:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 07:00:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2534) HQStore crashrec failures on QA_JTS_JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2534: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > HQStore crashrec failures on QA_JTS_JDKORB > ------------------------------------------ > > Key: JBTM-2534 > URL: https://issues.jboss.org/browse/JBTM-2534 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > Killed this one: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/127/ > Normally run to completion but lots of crash rec failures: > {quote} > Total time: 525 minutes 19 seconds > Test Failures: > crashrecovery02_2 CrashRecovery02_2_Test01 Fail (0m50.031s) > crashrecovery02_2 CrashRecovery02_2_Test06 Fail (0m43.914s) > crashrecovery02_2 CrashRecovery02_2_Test07 Fail (0m48.270s) > crashrecovery02_2 CrashRecovery02_2_Test08 Fail (0m48.340s) > crashrecovery02_2 CrashRecovery02_2_Test09 Fail (0m48.014s) > crashrecovery02_2 CrashRecovery02_2_Test10 Fail (0m47.865s) > crashrecovery02_2 CrashRecovery02_2_Test11 Fail (0m48.756s) > crashrecovery02_2 CrashRecovery02_2_Test12 Fail (0m47.992s) > crashrecovery02_2 CrashRecovery02_2_Test13 Fail (0m47.840s) > crashrecovery02_2 CrashRecovery02_2_Test14 Fail (0m47.948s) > crashrecovery02_2 CrashRecovery02_2_Test15 Fail (0m47.742s) > crashrecovery02_2 CrashRecovery02_2_Test16 Fail (0m48.953s) > crashrecovery02_2 CrashRecovery02_2_Test02 Fail (0m48.202s) > crashrecovery02_2 CrashRecovery02_2_Test03 Fail (2m3.776s) > crashrecovery02_2 CrashRecovery02_2_Test04 Fail (0m47.686s) > crashrecovery02_2 CrashRecovery02_2_Test05 Fail (0m47.859s) > crashrecovery02_2 CrashRecovery02_2_Test17 Fail (0m48.029s) > crashrecovery02_2 CrashRecovery02_2_Test18 Fail (0m47.658s) > crashrecovery02_2 CrashRecovery02_2_Test19 Fail (0m47.775s) > crashrecovery02_2 CrashRecovery02_2_Test20 Fail (0m48.086s) > crashrecovery02_2 CrashRecovery02_2_Test21 Fail (0m47.979s) > crashrecovery02_2 CrashRecovery02_2_Test22 Fail (0m48.137s) > crashrecovery02_2 CrashRecovery02_2_Test23 Fail (0m48.267s) > crashrecovery02_2 CrashRecovery02_2_Test24 Fail (0m48.100s) > crashrecovery02_2 CrashRecovery02_2_Test25 Fail (0m47.787s) > crashrecovery05_1 CrashRecovery05_1_Test01 Fail (1m17.781s) > crashrecovery05_1 CrashRecovery05_1_Test10 Fail (1m18.510s) > crashrecovery05_1 CrashRecovery05_1_Test06 Fail (1m17.647s) > crashrecovery05_1 CrashRecovery05_1_Test07 Fail (1m17.572s) > crashrecovery05_1 CrashRecovery05_1_Test08 Fail (1m17.365s) > crashrecovery05_1 CrashRecovery05_1_Test09 Fail (1m17.263s) > crashrecovery05_2 CrashRecovery05_2_Test051 Fail (2m3.491s) > crashrecovery05_2 CrashRecovery05_2_Test052 Fail (0m48.481s) > crashrecovery05_2 CrashRecovery05_2_Test053 Fail (2m3.698s) > crashrecovery05_2 CrashRecovery05_2_Test054 Fail (0m47.293s) > crashrecovery05_2 CrashRecovery05_2_Test055 Fail (0m48.382s) > crashrecovery05_2 CrashRecovery05_2_Test056 Fail (0m43.458s) > crashrecovery05_2 CrashRecovery05_2_Test057 Fail (0m49.076s) > crashrecovery05_2 CrashRecovery05_2_Test058 Fail (0m43.988s) > crashrecovery05_2 CrashRecovery05_2_Test059 Fail (0m48.177s) > crashrecovery05_2 CrashRecovery05_2_Test060 Fail (0m47.995s) > crashrecovery05_2 CrashRecovery05_2_Test061 Fail (0m48.266s) > crashrecovery05_2 CrashRecovery05_2_Test062 Fail (0m47.852s) > crashrecovery05_2 CrashRecovery05_2_Test063 Fail (2m3.059s) > crashrecovery05_2 CrashRecovery05_2_Test064 Fail (0m47.332s) > crashrecovery05_2 CrashRecovery05_2_Test065 Fail (0m47.226s) > crashrecovery05_2 CrashRecovery05_2_Test066 Fail (0m47.141s) > crashrecovery05_2 CrashRecovery05_2_Test067 Fail (0m47.195s) > crashrecovery05_2 CrashRecovery05_2_Test068 Fail (0m47.464s) > crashrecovery05_2 CrashRecovery05_2_Test069 Fail (0m49.360s) > crashrecovery05_2 CrashRecovery05_2_Test070 Fail (0m47.700s) > crashrecovery05_2 CrashRecovery05_2_Test071 Fail (0m47.782s) > crashrecovery05_2 CrashRecovery05_2_Test072 Fail (0m47.736s) > crashrecovery05_2 CrashRecovery05_2_Test073 Fail (0m47.438s) > crashrecovery05_2 CrashRecovery05_2_Test074 Fail (0m47.701s) > crashrecovery05_2 CrashRecovery05_2_Test075 Fail (0m47.385s) > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m10.036s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m54.372s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m10.928s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m55.124s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m54.970s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m50.656s) > crashrecovery05_2 CrashRecovery05_2_Test082 Fail (0m54.356s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m50.052s) > crashrecovery05_2 CrashRecovery05_2_Test084 Fail (0m53.605s) > crashrecovery05_2 CrashRecovery05_2_Test085 Fail (0m54.694s) > crashrecovery05_2 CrashRecovery05_2_Test086 Fail (0m54.147s) > crashrecovery05_2 CrashRecovery05_2_Test087 Fail (0m54.397s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m11.261s) > crashrecovery05_2 CrashRecovery05_2_Test089 Fail (0m54.332s) > crashrecovery05_2 CrashRecovery05_2_Test090 Fail (0m55.264s) > crashrecovery05_2 CrashRecovery05_2_Test091 Fail (0m54.471s) > crashrecovery05_2 CrashRecovery05_2_Test092 Fail (0m54.046s) > crashrecovery05_2 CrashRecovery05_2_Test093 Fail (0m54.249s) > crashrecovery05_2 CrashRecovery05_2_Test094 Fail (0m54.388s) > crashrecovery05_2 CrashRecovery05_2_Test095 Fail (0m53.763s) > crashrecovery05_2 CrashRecovery05_2_Test096 Fail (0m54.313s) > crashrecovery05_2 CrashRecovery05_2_Test097 Fail (0m54.069s) > crashrecovery05_2 CrashRecovery05_2_Test098 Fail (0m54.290s) > crashrecovery05_2 CrashRecovery05_2_Test099 Fail (0m55.164s) > crashrecovery05_2 CrashRecovery05_2_Test100 Fail (0m54.189s) > crashrecovery05_2 CrashRecovery05_2_Test002 Fail (0m46.793s) > crashrecovery05_2 CrashRecovery05_2_Test003 Fail (2m2.944s) > crashrecovery05_2 CrashRecovery05_2_Test005 Fail (0m46.742s) > crashrecovery05_2 CrashRecovery05_2_Test006 Fail (0m42.978s) > crashrecovery05_2 CrashRecovery05_2_Test028 Fail (2m9.683s) > crashrecovery05_2 CrashRecovery05_2_Test031 Fail (0m49.745s) > crashrecovery12 CrashRecovery12_Test03 Fail (0m15.884s) > Buildfile: /home/hudson/workspace/narayana-hqstore/PROFILE/QA_JTS_JDKORB/jdk/jdk8.latest/label/linux/qa/run-tests.xml > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 6 08:21:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 6 Nov 2015 08:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) ClassNotFoundException when restore_state from the object store during recovering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2550: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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) From issues at jboss.org Fri Nov 6 08:34:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 6 Nov 2015 08:34:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2532) Enable code coverage for XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2532: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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) From issues at jboss.org Fri Nov 6 08:35:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 6 Nov 2015 08:35:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2552) Benchmark script should accept extra script arguments In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2552: -------------------------------------- Summary: Benchmark script should accept extra script arguments Key: JBTM-2552 URL: https://issues.jboss.org/browse/JBTM-2552 Project: JBoss Transaction Manager Issue Type: Bug Components: Performance Testing Affects Versions: 5.2.7.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The launch script for running benchmarks (narayana/scripts/hudson/benchmark.sh in the repo https://github.com/jbosstm/performance) should propagate any script arguments through to the benchmark script. I plan to use this for configuring things like the transaction timeout value and to configure how many commit failures are tolerated before failing the job. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 6 08:35:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 6 Nov 2015 08:35:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2115) Not all classes are under code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2115: ---------------------------------- Description: The following poms contain skipped classes for code coverage: ArjunaCore/arjuna/pom.xml ArjunaJTA/jdbc/pom.xml ArjunaJTA/jta/pom.xml ArjunaJTA/spi/pom.xml XTS/localjunit/pom.xml compensations/pom.xml txframework/pom.xml We should aim to test everything was: The following poms contain skipped classes for code coverage: ArjunaCore/arjuna/pom.xml ArjunaJTA/jdbc/pom.xml ArjunaJTA/jta/pom.xml ArjunaJTA/spi/pom.xml XTS/localjunit/pom.xml We should aim to test everything > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > compensations/pom.xml > txframework/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 01:06:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 9 Nov 2015 01:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2498: ---------------------------- Fix Version/s: 5.next > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 01:28:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 9 Nov 2015 01:28:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126654#comment-13126654 ] Amos Feng commented on JBTM-2498: --------------------------------- I send PR https://github.com/jbosstm/quickstart/pull/155 to wget the initializeJBoss.xml from the narayana repo > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 01:58:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 9 Nov 2015 01:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: Amos Feng created JBTM-2553: ------------------------------- Summary: Investigate the test with byteman do not work with the jacoco Key: JBTM-2553 URL: https://issues.jboss.org/browse/JBTM-2553 Project: JBoss Transaction Manager Issue Type: Sub-task Reporter: Amos Feng Assignee: Amos Feng -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 02:42:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 9 Nov 2015 02:42:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126663#comment-13126663 ] Amos Feng commented on JBTM-2498: --------------------------------- It looks like the quickstart jobs clone and build the narayana so it does not need to wget from the github > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 05:36:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 9 Nov 2015 05:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2554: ------------------------------------- Summary: CrashRecovery05_2 failures on JacORB Key: JBTM-2554 URL: https://issues.jboss.org/browse/JBTM-2554 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Gytis Trikleris Assignee: Michael Musgrove Fix For: 5.next crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s) crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s) crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s) crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s) crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s) crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s) crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s) crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 05:38:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 9 Nov 2015 05:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126731#comment-13126731 ] Gytis Trikleris commented on JBTM-2554: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/979/ > CrashRecovery05_2 failures on JacORB > ------------------------------------ > > Key: JBTM-2554 > URL: https://issues.jboss.org/browse/JBTM-2554 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.next > > > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 05:56:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 9 Nov 2015 05:56:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2552) Benchmark script should accept extra script arguments In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2552. ------------------------------------ Release Notes Text: The benchmark script already supports passing extra arguments via a variable called JVM_ARGS Resolution: Rejected > Benchmark script should accept extra script arguments > ----------------------------------------------------- > > Key: JBTM-2552 > URL: https://issues.jboss.org/browse/JBTM-2552 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.7.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The launch script for running benchmarks (narayana/scripts/hudson/benchmark.sh in the repo https://github.com/jbosstm/performance) should propagate any script arguments through to the benchmark script. > I plan to use this for configuring things like the transaction timeout value and to configure how many commit failures are tolerated before failing the job. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 06:04:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 9 Nov 2015 06:04:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2555) JOTM benchmark produces too many rollback exceptions In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2555: -------------------------------------- Summary: JOTM benchmark produces too many rollback exceptions Key: JBTM-2555 URL: https://issues.jboss.org/browse/JBTM-2555 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Michael Musgrove Assignee: Michael Musgrove http://albany.eng.hst.ams2.redhat.com/job/narayana-benchmarks/52/ The rollbacks are most likely due to transaction timeouts (even though I set the threshold for failure to not more than 10 rollbacks). It is possible that JOTM just cannot cope with the number of threads we using to produce the benchmark. I have tried to reproduce the failures with a standalone junit test and using JMH on my laptop without success. I am going to remove JOTM from the comparison matrix (see job narayana-benchmarks) until this JIRA is resolved. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 06:11:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 9 Nov 2015 06:11:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2555) JOTM benchmark produces too many rollback exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2555: ----------------------------------- Fix Version/s: 5.next > JOTM benchmark produces too many rollback exceptions > ---------------------------------------------------- > > Key: JBTM-2555 > URL: https://issues.jboss.org/browse/JBTM-2555 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-benchmarks/52/ > The rollbacks are most likely due to transaction timeouts (even though I set the threshold for failure to not more than 10 rollbacks). > It is possible that JOTM just cannot cope with the number of threads we using to produce the benchmark. I have tried to reproduce the failures with a standalone junit test and using JMH on my laptop without success. > I am going to remove JOTM from the comparison matrix (see job narayana-benchmarks) until this JIRA is resolved. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 09:13:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 9 Nov 2015 09:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2556) Improve OSGi integration In-Reply-To: References: Message-ID: Amos Feng created JBTM-2556: ------------------------------- Summary: Improve OSGi integration Key: JBTM-2556 URL: https://issues.jboss.org/browse/JBTM-2556 Project: JBoss Transaction Manager Issue Type: Enhancement Components: JTA Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next support configuration using ConfigAdmin track org.jboss.tm.XAResourceRecovery services for recovery In order to support correctly stopping / restarting / reconfiguring the transaction manager, we build our own class loader to load the core jars. This ensure that all static fields will be correctly reloaded when starting again after configuration change. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 09:16:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 9 Nov 2015 09:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2557) Support Spring PlatformTransactionManager In-Reply-To: References: Message-ID: Amos Feng created JBTM-2557: ------------------------------- Summary: Support Spring PlatformTransactionManager Key: JBTM-2557 URL: https://issues.jboss.org/browse/JBTM-2557 Project: JBoss Transaction Manager Issue Type: Feature Request Components: JTA Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 09:37:00 2015 From: issues at jboss.org (Guillaume Nodet (JIRA)) Date: Mon, 9 Nov 2015 09:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2556) Improve OSGi integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned JBTM-2556: ------------------------------------- Assignee: Guillaume Nodet (was: Amos Feng) > Improve OSGi integration > ------------------------ > > Key: JBTM-2556 > URL: https://issues.jboss.org/browse/JBTM-2556 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Amos Feng > Assignee: Guillaume Nodet > Fix For: 5.next > > > support configuration using ConfigAdmin > track org.jboss.tm.XAResourceRecovery services for recovery > In order to support correctly stopping / restarting / reconfiguring the transaction manager, we build our own class loader to load the core jars. > This ensure that all static fields will be correctly reloaded when starting again after configuration change. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 09:37:00 2015 From: issues at jboss.org (Guillaume Nodet (JIRA)) Date: Mon, 9 Nov 2015 09:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2557) Support Spring PlatformTransactionManager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned JBTM-2557: ------------------------------------- Assignee: Guillaume Nodet (was: Amos Feng) > Support Spring PlatformTransactionManager > ----------------------------------------- > > Key: JBTM-2557 > URL: https://issues.jboss.org/browse/JBTM-2557 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Reporter: Amos Feng > Assignee: Guillaume Nodet > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 9 13:21:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 9 Nov 2015 13:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2554: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/939 > CrashRecovery05_2 failures on JacORB > ------------------------------------ > > Key: JBTM-2554 > URL: https://issues.jboss.org/browse/JBTM-2554 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.next > > > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 10 04:01:01 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 10 Nov 2015 04:01:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2558) CI report generator error while getting issue info In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2558: ------------------------------------- Summary: CI report generator error while getting issue info Key: JBTM-2558 URL: https://issues.jboss.org/browse/JBTM-2558 Project: JBoss Transaction Manager Issue Type: Bug Components: CI Report Generator Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next {code} Aggregating narayana build 979 Aggregating narayana build 978 Aggregating narayana build 863 Aggregating narayana build 858 Aggregating narayana build 830 Aggregating narayana build 779 Aggregating narayana build 638 Aggregating narayana build 550 Aggregating narayana-benchmarks build 56 Got an error while getting issue info: [object Object]  TypeError: Uncaught, unspecified "error" event. at TypeError () at DestroyableTransform.emit (events.js:74:15) at DestroyableTransform.onerror (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:604:12) at DestroyableTransform.emit (events.js:95:17) at onwriteError (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:345:10) at onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:363:5) at WritableState.onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:123:5) at afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:84:5) at TransformState.afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:59:12) at /home/hudson/workspace/ci-report-generator/streams/jiraInfoStream.js:23:17 Warning: -> error 8 /home/hudson/workspace/ci-report-generator/index.js (8883ms) Use --force to continue. {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 10 04:17:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 10 Nov 2015 04:17:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2558) CI report generator error while getting issue info In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2558: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/ci-report-generator/pull/3 > CI report generator error while getting issue info > -------------------------------------------------- > > Key: JBTM-2558 > URL: https://issues.jboss.org/browse/JBTM-2558 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: CI Report Generator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > {code} > Aggregating narayana build 979 > Aggregating narayana build 978 > Aggregating narayana build 863 > Aggregating narayana build 858 > Aggregating narayana build 830 > Aggregating narayana build 779 > Aggregating narayana build 638 > Aggregating narayana build 550 > Aggregating narayana-benchmarks build 56 > Got an error while getting issue info: [object Object] >  > TypeError: Uncaught, unspecified "error" event. > at TypeError () > at DestroyableTransform.emit (events.js:74:15) > at DestroyableTransform.onerror (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:604:12) > at DestroyableTransform.emit (events.js:95:17) > at onwriteError (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:345:10) > at onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:363:5) > at WritableState.onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:123:5) > at afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:84:5) > at TransformState.afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:59:12) > at /home/hudson/workspace/ci-report-generator/streams/jiraInfoStream.js:23:17 > Warning: -> error 8 /home/hudson/workspace/ci-report-generator/index.js (8883ms) Use --force to continue. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 10 04:18:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 10 Nov 2015 04:18:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2558) CI report generator error while getting issue info In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2558: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CI report generator error while getting issue info > -------------------------------------------------- > > Key: JBTM-2558 > URL: https://issues.jboss.org/browse/JBTM-2558 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: CI Report Generator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > {code} > Aggregating narayana build 979 > Aggregating narayana build 978 > Aggregating narayana build 863 > Aggregating narayana build 858 > Aggregating narayana build 830 > Aggregating narayana build 779 > Aggregating narayana build 638 > Aggregating narayana build 550 > Aggregating narayana-benchmarks build 56 > Got an error while getting issue info: [object Object] >  > TypeError: Uncaught, unspecified "error" event. > at TypeError () > at DestroyableTransform.emit (events.js:74:15) > at DestroyableTransform.onerror (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:604:12) > at DestroyableTransform.emit (events.js:95:17) > at onwriteError (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:345:10) > at onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:363:5) > at WritableState.onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:123:5) > at afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:84:5) > at TransformState.afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:59:12) > at /home/hudson/workspace/ci-report-generator/streams/jiraInfoStream.js:23:17 > Warning: -> error 8 /home/hudson/workspace/ci-report-generator/index.js (8883ms) Use --force to continue. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 10 05:15:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 10 Nov 2015 05:15:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127178#comment-13127178 ] Gytis Trikleris commented on JBTM-2554: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/job/narayana/980/ > CrashRecovery05_2 failures on JacORB > ------------------------------------ > > Key: JBTM-2554 > URL: https://issues.jboss.org/browse/JBTM-2554 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.next > > > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 10 05:19:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 10 Nov 2015 05:19:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127182#comment-13127182 ] Gytis Trikleris commented on JBTM-2554: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/job/narayana-jdbcobjectstore/168/ > CrashRecovery05_2 failures on JacORB > ------------------------------------ > > Key: JBTM-2554 > URL: https://issues.jboss.org/browse/JBTM-2554 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.next > > > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 10 05:26:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 10 Nov 2015 05:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2559) CrashRecovery02_2_Test28 failure on JDKORB and with journal storage In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2559: ------------------------------------- Summary: CrashRecovery02_2_Test28 failure on JDKORB and with journal storage Key: JBTM-2559 URL: https://issues.jboss.org/browse/JBTM-2559 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Gytis Trikleris Assignee: Michael Musgrove Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 10 05:27:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 10 Nov 2015 05:27:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2534) HQStore crashrec failures on QA_JTS_JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reopened JBTM-2534: ------------------------------------ The fix breaks some of the non journal store tests on JacORB (eg narayana job 978) > HQStore crashrec failures on QA_JTS_JDKORB > ------------------------------------------ > > Key: JBTM-2534 > URL: https://issues.jboss.org/browse/JBTM-2534 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > Killed this one: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/127/ > Normally run to completion but lots of crash rec failures: > {quote} > Total time: 525 minutes 19 seconds > Test Failures: > crashrecovery02_2 CrashRecovery02_2_Test01 Fail (0m50.031s) > crashrecovery02_2 CrashRecovery02_2_Test06 Fail (0m43.914s) > crashrecovery02_2 CrashRecovery02_2_Test07 Fail (0m48.270s) > crashrecovery02_2 CrashRecovery02_2_Test08 Fail (0m48.340s) > crashrecovery02_2 CrashRecovery02_2_Test09 Fail (0m48.014s) > crashrecovery02_2 CrashRecovery02_2_Test10 Fail (0m47.865s) > crashrecovery02_2 CrashRecovery02_2_Test11 Fail (0m48.756s) > crashrecovery02_2 CrashRecovery02_2_Test12 Fail (0m47.992s) > crashrecovery02_2 CrashRecovery02_2_Test13 Fail (0m47.840s) > crashrecovery02_2 CrashRecovery02_2_Test14 Fail (0m47.948s) > crashrecovery02_2 CrashRecovery02_2_Test15 Fail (0m47.742s) > crashrecovery02_2 CrashRecovery02_2_Test16 Fail (0m48.953s) > crashrecovery02_2 CrashRecovery02_2_Test02 Fail (0m48.202s) > crashrecovery02_2 CrashRecovery02_2_Test03 Fail (2m3.776s) > crashrecovery02_2 CrashRecovery02_2_Test04 Fail (0m47.686s) > crashrecovery02_2 CrashRecovery02_2_Test05 Fail (0m47.859s) > crashrecovery02_2 CrashRecovery02_2_Test17 Fail (0m48.029s) > crashrecovery02_2 CrashRecovery02_2_Test18 Fail (0m47.658s) > crashrecovery02_2 CrashRecovery02_2_Test19 Fail (0m47.775s) > crashrecovery02_2 CrashRecovery02_2_Test20 Fail (0m48.086s) > crashrecovery02_2 CrashRecovery02_2_Test21 Fail (0m47.979s) > crashrecovery02_2 CrashRecovery02_2_Test22 Fail (0m48.137s) > crashrecovery02_2 CrashRecovery02_2_Test23 Fail (0m48.267s) > crashrecovery02_2 CrashRecovery02_2_Test24 Fail (0m48.100s) > crashrecovery02_2 CrashRecovery02_2_Test25 Fail (0m47.787s) > crashrecovery05_1 CrashRecovery05_1_Test01 Fail (1m17.781s) > crashrecovery05_1 CrashRecovery05_1_Test10 Fail (1m18.510s) > crashrecovery05_1 CrashRecovery05_1_Test06 Fail (1m17.647s) > crashrecovery05_1 CrashRecovery05_1_Test07 Fail (1m17.572s) > crashrecovery05_1 CrashRecovery05_1_Test08 Fail (1m17.365s) > crashrecovery05_1 CrashRecovery05_1_Test09 Fail (1m17.263s) > crashrecovery05_2 CrashRecovery05_2_Test051 Fail (2m3.491s) > crashrecovery05_2 CrashRecovery05_2_Test052 Fail (0m48.481s) > crashrecovery05_2 CrashRecovery05_2_Test053 Fail (2m3.698s) > crashrecovery05_2 CrashRecovery05_2_Test054 Fail (0m47.293s) > crashrecovery05_2 CrashRecovery05_2_Test055 Fail (0m48.382s) > crashrecovery05_2 CrashRecovery05_2_Test056 Fail (0m43.458s) > crashrecovery05_2 CrashRecovery05_2_Test057 Fail (0m49.076s) > crashrecovery05_2 CrashRecovery05_2_Test058 Fail (0m43.988s) > crashrecovery05_2 CrashRecovery05_2_Test059 Fail (0m48.177s) > crashrecovery05_2 CrashRecovery05_2_Test060 Fail (0m47.995s) > crashrecovery05_2 CrashRecovery05_2_Test061 Fail (0m48.266s) > crashrecovery05_2 CrashRecovery05_2_Test062 Fail (0m47.852s) > crashrecovery05_2 CrashRecovery05_2_Test063 Fail (2m3.059s) > crashrecovery05_2 CrashRecovery05_2_Test064 Fail (0m47.332s) > crashrecovery05_2 CrashRecovery05_2_Test065 Fail (0m47.226s) > crashrecovery05_2 CrashRecovery05_2_Test066 Fail (0m47.141s) > crashrecovery05_2 CrashRecovery05_2_Test067 Fail (0m47.195s) > crashrecovery05_2 CrashRecovery05_2_Test068 Fail (0m47.464s) > crashrecovery05_2 CrashRecovery05_2_Test069 Fail (0m49.360s) > crashrecovery05_2 CrashRecovery05_2_Test070 Fail (0m47.700s) > crashrecovery05_2 CrashRecovery05_2_Test071 Fail (0m47.782s) > crashrecovery05_2 CrashRecovery05_2_Test072 Fail (0m47.736s) > crashrecovery05_2 CrashRecovery05_2_Test073 Fail (0m47.438s) > crashrecovery05_2 CrashRecovery05_2_Test074 Fail (0m47.701s) > crashrecovery05_2 CrashRecovery05_2_Test075 Fail (0m47.385s) > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m10.036s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m54.372s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m10.928s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m55.124s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m54.970s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m50.656s) > crashrecovery05_2 CrashRecovery05_2_Test082 Fail (0m54.356s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m50.052s) > crashrecovery05_2 CrashRecovery05_2_Test084 Fail (0m53.605s) > crashrecovery05_2 CrashRecovery05_2_Test085 Fail (0m54.694s) > crashrecovery05_2 CrashRecovery05_2_Test086 Fail (0m54.147s) > crashrecovery05_2 CrashRecovery05_2_Test087 Fail (0m54.397s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m11.261s) > crashrecovery05_2 CrashRecovery05_2_Test089 Fail (0m54.332s) > crashrecovery05_2 CrashRecovery05_2_Test090 Fail (0m55.264s) > crashrecovery05_2 CrashRecovery05_2_Test091 Fail (0m54.471s) > crashrecovery05_2 CrashRecovery05_2_Test092 Fail (0m54.046s) > crashrecovery05_2 CrashRecovery05_2_Test093 Fail (0m54.249s) > crashrecovery05_2 CrashRecovery05_2_Test094 Fail (0m54.388s) > crashrecovery05_2 CrashRecovery05_2_Test095 Fail (0m53.763s) > crashrecovery05_2 CrashRecovery05_2_Test096 Fail (0m54.313s) > crashrecovery05_2 CrashRecovery05_2_Test097 Fail (0m54.069s) > crashrecovery05_2 CrashRecovery05_2_Test098 Fail (0m54.290s) > crashrecovery05_2 CrashRecovery05_2_Test099 Fail (0m55.164s) > crashrecovery05_2 CrashRecovery05_2_Test100 Fail (0m54.189s) > crashrecovery05_2 CrashRecovery05_2_Test002 Fail (0m46.793s) > crashrecovery05_2 CrashRecovery05_2_Test003 Fail (2m2.944s) > crashrecovery05_2 CrashRecovery05_2_Test005 Fail (0m46.742s) > crashrecovery05_2 CrashRecovery05_2_Test006 Fail (0m42.978s) > crashrecovery05_2 CrashRecovery05_2_Test028 Fail (2m9.683s) > crashrecovery05_2 CrashRecovery05_2_Test031 Fail (0m49.745s) > crashrecovery12 CrashRecovery12_Test03 Fail (0m15.884s) > Buildfile: /home/hudson/workspace/narayana-hqstore/PROFILE/QA_JTS_JDKORB/jdk/jdk8.latest/label/linux/qa/run-tests.xml > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 10 08:42:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 10 Nov 2015 08:42:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2554: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/939, https://github.com/jbosstm/narayana/pull/941 (was: https://github.com/jbosstm/narayana/pull/939) > CrashRecovery05_2 failures on JacORB > ------------------------------------ > > Key: JBTM-2554 > URL: https://issues.jboss.org/browse/JBTM-2554 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.next > > > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Nov 11 00:04:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 11 Nov 2015 00:04:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2496) Investigate using of camel for content based routing in the Blacktie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127576#comment-13127576 ] Amos Feng commented on JBTM-2496: --------------------------------- I just remove all the out-of-date codes and the wildfly-camel 3.0.1 works with wildfly-9.0.1.Final currently. The example can be found at https://github.com/zhfeng/blacktie-cbr > Investigate using of camel for content based routing in the Blacktie > -------------------------------------------------------------------- > > Key: JBTM-2496 > URL: https://issues.jboss.org/browse/JBTM-2496 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.later > > > The current cbr quickstart is out-of-date by using the jboss-esb and it needs to investigate the camel -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Nov 11 05:16:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 11 Nov 2015 05:16:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2496) Investigate using of camel for content based routing in the Blacktie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127649#comment-13127649 ] Tom Jenkinson commented on JBTM-2496: ------------------------------------- Thanks Amos - what is missing to make it work with WildFly 10, please? > Investigate using of camel for content based routing in the Blacktie > -------------------------------------------------------------------- > > Key: JBTM-2496 > URL: https://issues.jboss.org/browse/JBTM-2496 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.later > > > The current cbr quickstart is out-of-date by using the jboss-esb and it needs to investigate the camel -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 12 00:19:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 12 Nov 2015 00:19:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2496) Investigate using of camel for content based routing in the Blacktie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128020#comment-13128020 ] Amos Feng commented on JBTM-2496: --------------------------------- I think it might be related to the hornetq upgrade to the activemq artimes. We need the camel-jms to read/write the messages from the queues. > Investigate using of camel for content based routing in the Blacktie > -------------------------------------------------------------------- > > Key: JBTM-2496 > URL: https://issues.jboss.org/browse/JBTM-2496 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.later > > > The current cbr quickstart is out-of-date by using the jboss-esb and it needs to investigate the camel -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 12 01:41:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 12 Nov 2015 01:41:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2556) Improve OSGi integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2556: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/938 > Improve OSGi integration > ------------------------ > > Key: JBTM-2556 > URL: https://issues.jboss.org/browse/JBTM-2556 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Amos Feng > Assignee: Guillaume Nodet > Fix For: 5.next > > > support configuration using ConfigAdmin > track org.jboss.tm.XAResourceRecovery services for recovery > In order to support correctly stopping / restarting / reconfiguring the transaction manager, we build our own class loader to load the core jars. > This ensure that all static fields will be correctly reloaded when starting again after configuration change. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 12 01:41:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 12 Nov 2015 01:41:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2556) Improve OSGi integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2556: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Improve OSGi integration > ------------------------ > > Key: JBTM-2556 > URL: https://issues.jboss.org/browse/JBTM-2556 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Amos Feng > Assignee: Guillaume Nodet > Fix For: 5.next > > > support configuration using ConfigAdmin > track org.jboss.tm.XAResourceRecovery services for recovery > In order to support correctly stopping / restarting / reconfiguring the transaction manager, we build our own class loader to load the core jars. > This ensure that all static fields will be correctly reloaded when starting again after configuration change. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 12 01:42:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 12 Nov 2015 01:42:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2557) Support Spring PlatformTransactionManager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng resolved JBTM-2557. ----------------------------- Resolution: Done > Support Spring PlatformTransactionManager > ----------------------------------------- > > Key: JBTM-2557 > URL: https://issues.jboss.org/browse/JBTM-2557 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Reporter: Amos Feng > Assignee: Guillaume Nodet > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 12 01:46:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 12 Nov 2015 01:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2545) Use consistent naming scheme for ORB jbossts-properties files in the repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2545: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use consistent naming scheme for ORB jbossts-properties files in the repo > ------------------------------------------------------------------------- > > Key: JBTM-2545 > URL: https://issues.jboss.org/browse/JBTM-2545 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > This simplifies testing makes the tests more consistent. The overall effect on the user is that the default filenames are clearer rather than assuming jacorb. > Plus the fact that narayana-jacorb module has narayana-idlj file in (which is an error IMO) - and the converse is also true. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 12 08:16:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 12 Nov 2015 08:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2544) RTS inbound bridge recovery does not work with JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2544: ----------------------------------- Steps to Reproduce: Add "" to the transaction subsystem configuration in standalone/configuration/standalone-rts.xml Update the openjdk subsystem: /subsystem=iiop-openjdk/:write-attribute(name=transactions,value=full) >From Narayana code base execute the following: {code} ./build.sh -f rts/at/bridge/pom.xml clean test -Parq -Dtest=InboundBridgeRecoveryTestCase#testCrashBeforeCommit {code} was: Add "" to the transaction subsystem configuration in standalone/configuration/standalone-rts.xml >From Narayana code base execute the following: {code} ./build.sh -f rts/at/bridge/pom.xml clean test -Parq -Dtest=InboundBridgeRecoveryTestCase#testCrashBeforeCommit {code} > 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) From issues at jboss.org Fri Nov 13 05:27:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 13 Nov 2015 05:27:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2537: -------------------------------- Summary: Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana (was: Can't build WFLY on a machine that has only built for IBM Orb) > Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana > ----------------------------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > I am not sure if this might really need a WFLY change instead of JBTM? > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 13 05:27:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 13 Nov 2015 05:27:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2537: -------------------------------- Priority: Major (was: Minor) > Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana > ----------------------------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I am not sure if this might really need a WFLY change instead of JBTM? > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 13 05:32:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 13 Nov 2015 05:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128655#comment-13128655 ] Michael Musgrove commented on JBTM-2537: ---------------------------------------- I have updated the CI job (narayana-ibm-jdk) to build the distribution twice to ensure that the default one is still in the m2 repo. > Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana > ----------------------------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I am not sure if this might really need a WFLY change instead of JBTM? > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 13 05:37:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 13 Nov 2015 05:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128655#comment-13128655 ] Michael Musgrove edited comment on JBTM-2537 at 11/13/15 5:36 AM: ------------------------------------------------------------------ I have updated the CI job (narayana-ibm-jdk) to build the distribution twice to ensure that the default one is available in the m2 repo. This should fix it since the build I did after the change progressed past the wildfly build and failed for an unrelated reason. I have started CI job #147 to see if we can get a clean build. was (Author: mmusgrov): I have updated the CI job (narayana-ibm-jdk) to build the distribution twice to ensure that the default one is still in the m2 repo. > Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana > ----------------------------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I am not sure if this might really need a WFLY change instead of JBTM? > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 13 05:52:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 13 Nov 2015 05:52:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128662#comment-13128662 ] Tom Jenkinson commented on JBTM-2537: ------------------------------------- I think the problem is that WildFly can only pull in: {quote} org.jboss.narayana.jts narayana-jts-idlj ${version.org.jboss.narayana} {quote} https://github.com/wildfly/wildfly/blob/master/pom.xml#L4435 It may work now if one of your builds is building that idlj jar but it is still incorrect as WFLY needs updating to build with narayana-jts-ibmorb artifact (and may even need a subsystem change). I think for now we should try to avoid the need to build the app server in our job and wait until WFLY can use the IBM ORB - what do you think? > Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana > ----------------------------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I am not sure if this might really need a WFLY change instead of JBTM? > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 13 05:58:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 13 Nov 2015 05:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Remove the need to build WildFly in IBM ORB job config In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2537: -------------------------------- Summary: Remove the need to build WildFly in IBM ORB job config (was: Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana) > Remove the need to build WildFly in IBM ORB job config > ------------------------------------------------------ > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I am not sure if this might really need a WFLY change instead of JBTM? > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 13 05:59:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 13 Nov 2015 05:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Remove the need to build WildFly in IBM ORB job config In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2537: -------------------------------- Description: I guess it finally caught us after an .m2 wipe? http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console was: I am not sure if this might really need a WFLY change instead of JBTM? I guess it finally caught us after an .m2 wipe? http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console > Remove the need to build WildFly in IBM ORB job config > ------------------------------------------------------ > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 13 06:17:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 13 Nov 2015 06:17:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Remove the need to build WildFly in IBM ORB job config In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128671#comment-13128671 ] Michael Musgrove commented on JBTM-2537: ---------------------------------------- WFLY does not currently support the IBM orb so we should postpone testing with WFLY until such time that it has such support. Note also that we still need to get recovery working with IBM orb (JBTM-2110) so the job does not run the QA tests. > Remove the need to build WildFly in IBM ORB job config > ------------------------------------------------------ > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 13 06:58:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 13 Nov 2015 06:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2318) Too verbose startup? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2318: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Too verbose startup? > -------------------- > > Key: JBTM-2318 > URL: https://issues.jboss.org/browse/JBTM-2318 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > At startup of the most basic example we see ... > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService > INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem > INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start > INFO: ARJUNA012170: TransactionStatusManager started on port 52185 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > There's a separate conversation to be had about whether the INFO should be there (DEBUG maybe?) but ignoring those why do we print the other lines at all? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 13 08:04:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 13 Nov 2015 08:04:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Remove the need to build WildFly in IBM ORB job config In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128671#comment-13128671 ] Michael Musgrove edited comment on JBTM-2537 at 11/13/15 8:03 AM: ------------------------------------------------------------------ WFLY does not currently support the IBM orb so we should postpone testing with WFLY until such time that it has such support. Note also that we still need to get recovery working with IBM orb (JBTM-2110) so the job does not run any of the tests. was (Author: mmusgrov): WFLY does not currently support the IBM orb so we should postpone testing with WFLY until such time that it has such support. Note also that we still need to get recovery working with IBM orb (JBTM-2110) so the job does not run the QA tests. > Remove the need to build WildFly in IBM ORB job config > ------------------------------------------------------ > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 13 09:14:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 13 Nov 2015 09:14:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Remove the need to build WildFly in IBM ORB job config In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128738#comment-13128738 ] Michael Musgrove commented on JBTM-2537: ---------------------------------------- The build is also failing processing idl files: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/149 so more investigation is needed. > Remove the need to build WildFly in IBM ORB job config > ------------------------------------------------------ > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Nov 15 08:24:00 2015 From: issues at jboss.org (Philippe Marschall (JIRA)) Date: Sun, 15 Nov 2015 08:24:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2560) Add generics In-Reply-To: References: Message-ID: Philippe Marschall created JBTM-2560: ---------------------------------------- Summary: Add generics Key: JBTM-2560 URL: https://issues.jboss.org/browse/JBTM-2560 Project: JBoss Transaction Manager Issue Type: Patch Components: JTA, Recovery, Transaction Core, TxBridge, XTS Reporter: Philippe Marschall Assignee: Gytis Trikleris Since the source level is Java 5+ the code base can be properly generified. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Nov 15 08:28:00 2015 From: issues at jboss.org (Philippe Marschall (JIRA)) Date: Sun, 15 Nov 2015 08:28:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2560) Add generics In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philippe Marschall updated JBTM-2560: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/943 > Add generics > ------------ > > Key: JBTM-2560 > URL: https://issues.jboss.org/browse/JBTM-2560 > Project: JBoss Transaction Manager > Issue Type: Patch > Components: JTA, Recovery, Transaction Core, TxBridge, XTS > Reporter: Philippe Marschall > Assignee: Gytis Trikleris > > Since the source level is Java 5+ the code base can be properly generified. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 16 10:47:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 16 Nov 2015 10:47:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2555) JOTM benchmark produces too many rollback exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2555. ------------------------------------ Resolution: Done Main fix was to reduce the number of threads used to run the workload to just 300 > JOTM benchmark produces too many rollback exceptions > ---------------------------------------------------- > > Key: JBTM-2555 > URL: https://issues.jboss.org/browse/JBTM-2555 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-benchmarks/52/ > The rollbacks are most likely due to transaction timeouts (even though I set the threshold for failure to not more than 10 rollbacks). > It is possible that JOTM just cannot cope with the number of threads we using to produce the benchmark. I have tried to reproduce the failures with a standalone junit test and using JMH on my laptop without success. > I am going to remove JOTM from the comparison matrix (see job narayana-benchmarks) until this JIRA is resolved. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 05:23:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Nov 2015 05:23:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2534) HQStore crashrec failures on QA_JTS_JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2534. ------------------------------------ Resolution: Done Job http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/134/ shows the issue as fixed > HQStore crashrec failures on QA_JTS_JDKORB > ------------------------------------------ > > Key: JBTM-2534 > URL: https://issues.jboss.org/browse/JBTM-2534 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > Killed this one: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/127/ > Normally run to completion but lots of crash rec failures: > {quote} > Total time: 525 minutes 19 seconds > Test Failures: > crashrecovery02_2 CrashRecovery02_2_Test01 Fail (0m50.031s) > crashrecovery02_2 CrashRecovery02_2_Test06 Fail (0m43.914s) > crashrecovery02_2 CrashRecovery02_2_Test07 Fail (0m48.270s) > crashrecovery02_2 CrashRecovery02_2_Test08 Fail (0m48.340s) > crashrecovery02_2 CrashRecovery02_2_Test09 Fail (0m48.014s) > crashrecovery02_2 CrashRecovery02_2_Test10 Fail (0m47.865s) > crashrecovery02_2 CrashRecovery02_2_Test11 Fail (0m48.756s) > crashrecovery02_2 CrashRecovery02_2_Test12 Fail (0m47.992s) > crashrecovery02_2 CrashRecovery02_2_Test13 Fail (0m47.840s) > crashrecovery02_2 CrashRecovery02_2_Test14 Fail (0m47.948s) > crashrecovery02_2 CrashRecovery02_2_Test15 Fail (0m47.742s) > crashrecovery02_2 CrashRecovery02_2_Test16 Fail (0m48.953s) > crashrecovery02_2 CrashRecovery02_2_Test02 Fail (0m48.202s) > crashrecovery02_2 CrashRecovery02_2_Test03 Fail (2m3.776s) > crashrecovery02_2 CrashRecovery02_2_Test04 Fail (0m47.686s) > crashrecovery02_2 CrashRecovery02_2_Test05 Fail (0m47.859s) > crashrecovery02_2 CrashRecovery02_2_Test17 Fail (0m48.029s) > crashrecovery02_2 CrashRecovery02_2_Test18 Fail (0m47.658s) > crashrecovery02_2 CrashRecovery02_2_Test19 Fail (0m47.775s) > crashrecovery02_2 CrashRecovery02_2_Test20 Fail (0m48.086s) > crashrecovery02_2 CrashRecovery02_2_Test21 Fail (0m47.979s) > crashrecovery02_2 CrashRecovery02_2_Test22 Fail (0m48.137s) > crashrecovery02_2 CrashRecovery02_2_Test23 Fail (0m48.267s) > crashrecovery02_2 CrashRecovery02_2_Test24 Fail (0m48.100s) > crashrecovery02_2 CrashRecovery02_2_Test25 Fail (0m47.787s) > crashrecovery05_1 CrashRecovery05_1_Test01 Fail (1m17.781s) > crashrecovery05_1 CrashRecovery05_1_Test10 Fail (1m18.510s) > crashrecovery05_1 CrashRecovery05_1_Test06 Fail (1m17.647s) > crashrecovery05_1 CrashRecovery05_1_Test07 Fail (1m17.572s) > crashrecovery05_1 CrashRecovery05_1_Test08 Fail (1m17.365s) > crashrecovery05_1 CrashRecovery05_1_Test09 Fail (1m17.263s) > crashrecovery05_2 CrashRecovery05_2_Test051 Fail (2m3.491s) > crashrecovery05_2 CrashRecovery05_2_Test052 Fail (0m48.481s) > crashrecovery05_2 CrashRecovery05_2_Test053 Fail (2m3.698s) > crashrecovery05_2 CrashRecovery05_2_Test054 Fail (0m47.293s) > crashrecovery05_2 CrashRecovery05_2_Test055 Fail (0m48.382s) > crashrecovery05_2 CrashRecovery05_2_Test056 Fail (0m43.458s) > crashrecovery05_2 CrashRecovery05_2_Test057 Fail (0m49.076s) > crashrecovery05_2 CrashRecovery05_2_Test058 Fail (0m43.988s) > crashrecovery05_2 CrashRecovery05_2_Test059 Fail (0m48.177s) > crashrecovery05_2 CrashRecovery05_2_Test060 Fail (0m47.995s) > crashrecovery05_2 CrashRecovery05_2_Test061 Fail (0m48.266s) > crashrecovery05_2 CrashRecovery05_2_Test062 Fail (0m47.852s) > crashrecovery05_2 CrashRecovery05_2_Test063 Fail (2m3.059s) > crashrecovery05_2 CrashRecovery05_2_Test064 Fail (0m47.332s) > crashrecovery05_2 CrashRecovery05_2_Test065 Fail (0m47.226s) > crashrecovery05_2 CrashRecovery05_2_Test066 Fail (0m47.141s) > crashrecovery05_2 CrashRecovery05_2_Test067 Fail (0m47.195s) > crashrecovery05_2 CrashRecovery05_2_Test068 Fail (0m47.464s) > crashrecovery05_2 CrashRecovery05_2_Test069 Fail (0m49.360s) > crashrecovery05_2 CrashRecovery05_2_Test070 Fail (0m47.700s) > crashrecovery05_2 CrashRecovery05_2_Test071 Fail (0m47.782s) > crashrecovery05_2 CrashRecovery05_2_Test072 Fail (0m47.736s) > crashrecovery05_2 CrashRecovery05_2_Test073 Fail (0m47.438s) > crashrecovery05_2 CrashRecovery05_2_Test074 Fail (0m47.701s) > crashrecovery05_2 CrashRecovery05_2_Test075 Fail (0m47.385s) > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m10.036s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m54.372s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m10.928s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m55.124s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m54.970s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m50.656s) > crashrecovery05_2 CrashRecovery05_2_Test082 Fail (0m54.356s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m50.052s) > crashrecovery05_2 CrashRecovery05_2_Test084 Fail (0m53.605s) > crashrecovery05_2 CrashRecovery05_2_Test085 Fail (0m54.694s) > crashrecovery05_2 CrashRecovery05_2_Test086 Fail (0m54.147s) > crashrecovery05_2 CrashRecovery05_2_Test087 Fail (0m54.397s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m11.261s) > crashrecovery05_2 CrashRecovery05_2_Test089 Fail (0m54.332s) > crashrecovery05_2 CrashRecovery05_2_Test090 Fail (0m55.264s) > crashrecovery05_2 CrashRecovery05_2_Test091 Fail (0m54.471s) > crashrecovery05_2 CrashRecovery05_2_Test092 Fail (0m54.046s) > crashrecovery05_2 CrashRecovery05_2_Test093 Fail (0m54.249s) > crashrecovery05_2 CrashRecovery05_2_Test094 Fail (0m54.388s) > crashrecovery05_2 CrashRecovery05_2_Test095 Fail (0m53.763s) > crashrecovery05_2 CrashRecovery05_2_Test096 Fail (0m54.313s) > crashrecovery05_2 CrashRecovery05_2_Test097 Fail (0m54.069s) > crashrecovery05_2 CrashRecovery05_2_Test098 Fail (0m54.290s) > crashrecovery05_2 CrashRecovery05_2_Test099 Fail (0m55.164s) > crashrecovery05_2 CrashRecovery05_2_Test100 Fail (0m54.189s) > crashrecovery05_2 CrashRecovery05_2_Test002 Fail (0m46.793s) > crashrecovery05_2 CrashRecovery05_2_Test003 Fail (2m2.944s) > crashrecovery05_2 CrashRecovery05_2_Test005 Fail (0m46.742s) > crashrecovery05_2 CrashRecovery05_2_Test006 Fail (0m42.978s) > crashrecovery05_2 CrashRecovery05_2_Test028 Fail (2m9.683s) > crashrecovery05_2 CrashRecovery05_2_Test031 Fail (0m49.745s) > crashrecovery12 CrashRecovery12_Test03 Fail (0m15.884s) > Buildfile: /home/hudson/workspace/narayana-hqstore/PROFILE/QA_JTS_JDKORB/jdk/jdk8.latest/label/linux/qa/run-tests.xml > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 05:35:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Nov 2015 05:35:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2559) CrashRecovery02_2_Test28 failure on JDKORB and with journal storage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2559: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/936, https://github.com/jbosstm/narayana/pull/941, https://github.com/jbosstm/narayana/pull/939 > CrashRecovery02_2_Test28 failure on JDKORB and with journal storage > ------------------------------------------------------------------- > > Key: JBTM-2559 > URL: https://issues.jboss.org/browse/JBTM-2559 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 05:35:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Nov 2015 05:35:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2559) CrashRecovery02_2_Test28 failure on JDKORB and with journal storage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2559: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CrashRecovery02_2_Test28 failure on JDKORB and with journal storage > ------------------------------------------------------------------- > > Key: JBTM-2559 > URL: https://issues.jboss.org/browse/JBTM-2559 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 05:36:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Nov 2015 05:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2554: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/936, https://github.com/jbosstm/narayana/pull/941 (was: https://github.com/jbosstm/narayana/pull/939, https://github.com/jbosstm/narayana/pull/941) > CrashRecovery05_2 failures on JacORB > ------------------------------------ > > Key: JBTM-2554 > URL: https://issues.jboss.org/browse/JBTM-2554 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.next > > > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 05:36:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Nov 2015 05:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2554: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CrashRecovery05_2 failures on JacORB > ------------------------------------ > > Key: JBTM-2554 > URL: https://issues.jboss.org/browse/JBTM-2554 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.next > > > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 05:39:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Nov 2015 05:39:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2551) CrashRecovery02_1_Test05 failure on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2551. ------------------------------------ Resolution: Done This problem has not recurred and there were some fixes in this area that may have resolved the issue (https://github.com/jbosstm/narayana/pull/939 and https://github.com/jbosstm/narayana/pull/941). I am marking the JIRA as resolved for now. > 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) From issues at jboss.org Tue Nov 17 05:41:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Nov 2015 05:41:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2511) Benchmark failure testing REST-AT with undertow In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129547#comment-13129547 ] Michael Musgrove commented on JBTM-2511: ---------------------------------------- I have created a CI job (http://albany.eng.hst.ams2.redhat.com/job/narayana-benchmarks-JBTM-2511) to help track down this issue. > Benchmark failure testing REST-AT with undertow > ----------------------------------------------- > > Key: JBTM-2511 > URL: https://issues.jboss.org/browse/JBTM-2511 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing, REST > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The REST-AT benchmark tests are failing: > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmarks/37/ > and the failure is: > bq. Caused by: javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable > whilst sending a request to a JAX-RS service. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 05:52:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 17 Nov 2015 05:52:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Add an IBM ORB configuration to WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2537: -------------------------------- Summary: Add an IBM ORB configuration to WildFly (was: Remove the need to build WildFly in IBM ORB job config) > Add an IBM ORB configuration to WildFly > --------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 05:53:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 17 Nov 2015 05:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Add an IBM ORB configuration to WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2537: -------------------------------- Description: Placeholder to be moved to WFLY I guess it finally caught us after an .m2 wipe? http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console was: I guess it finally caught us after an .m2 wipe? http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console > Add an IBM ORB configuration to WildFly > --------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Placeholder to be moved to WFLY > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 05:53:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 17 Nov 2015 05:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Add an IBM ORB configuration to WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2537: -------------------------------- Priority: Optional (was: Major) > Add an IBM ORB configuration to WildFly > --------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Placeholder to be moved to WFLY > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 05:53:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 17 Nov 2015 05:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Add an IBM ORB configuration to WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2537: -------------------------------- Issue Type: Feature Request (was: Bug) > Add an IBM ORB configuration to WildFly > --------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Placeholder to be moved to WFLY > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/139/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 06:18:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Nov 2015 06:18:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2542) Migrate performance tests to the performance repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2542: ----------------------------------- Attachment: config.xml The old job conifg show what we used to test > 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 > Fix For: 5.later > > Attachments: 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) From issues at jboss.org Tue Nov 17 06:18:01 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Nov 2015 06:18:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2542) Migrate performance tests to the performance repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129554#comment-13129554 ] Michael Musgrove edited comment on JBTM-2542 at 11/17/15 6:17 AM: ------------------------------------------------------------------ The old jenkins job conifg show what we used to test was (Author: mmusgrov): The old job conifg show what we used to test > 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 > Fix For: 5.later > > Attachments: 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) From issues at jboss.org Tue Nov 17 06:23:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Nov 2015 06:23:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2542) Migrate performance tests to the performance repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2542: ----------------------------------- Attachment: eap-cmp-config.xml Jenkins config for a job that compares EAP5 and EAP6 > 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 > 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) From issues at jboss.org Tue Nov 17 06:37:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Nov 2015 06:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2560) Add generics In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129572#comment-13129572 ] Michael Musgrove commented on JBTM-2560: ---------------------------------------- The JDK collections part of this is just one of the options: * JDK Collections; * Goldman Sachs Collections; * Google Collections (Guava); * javolution; * Highly Scalable Java; * ... > Add generics > ------------ > > Key: JBTM-2560 > URL: https://issues.jboss.org/browse/JBTM-2560 > Project: JBoss Transaction Manager > Issue Type: Patch > Components: JTA, Recovery, Transaction Core, TxBridge, XTS > Reporter: Philippe Marschall > Assignee: Gytis Trikleris > > Since the source level is Java 5+ the code base can be properly generified. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 07:07:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 17 Nov 2015 07:07:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2561) XTS code coverage failures In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2561: ------------------------------------- Summary: XTS code coverage failures Key: JBTM-2561 URL: https://issues.jboss.org/browse/JBTM-2561 Project: JBoss Transaction Manager Issue Type: Bug Components: XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 07:09:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 17 Nov 2015 07:09:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2561) XTS code coverage failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129599#comment-13129599 ] Gytis Trikleris commented on JBTM-2561: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/260/ > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 07:51:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 17 Nov 2015 07:51:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2560) Add generics In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris reassigned JBTM-2560: ------------------------------------- Assignee: (was: Gytis Trikleris) > Add generics > ------------ > > Key: JBTM-2560 > URL: https://issues.jboss.org/browse/JBTM-2560 > Project: JBoss Transaction Manager > Issue Type: Patch > Components: JTA, Recovery, Transaction Core, TxBridge, XTS > Reporter: Philippe Marschall > > Since the source level is Java 5+ the code base can be properly generified. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 07:59:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 17 Nov 2015 07:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2562) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2562: ----------------------------------- Summary: Run quickstarts on IPv6 Key: JBTM-2562 URL: https://issues.jboss.org/browse/JBTM-2562 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator Reporter: Tom Jenkinson Assignee: Michael Musgrove Priority: Minor Fix For: 5.next We should git clone the quickstart as part of http://172.17.130.4:8083/job/narayana-dualstack/ and try to run it as there as JBEAP-1770 was raised to suggest it won't work on IPv6 due to arquillian config. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 09:09:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 17 Nov 2015 09:09:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2522) Update performance comparison tests to use JMH In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2522 stopped by Gytis Trikleris. --------------------------------------------- > Update performance comparison tests to use JMH > ---------------------------------------------- > > Key: JBTM-2522 > URL: https://issues.jboss.org/browse/JBTM-2522 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 09:09:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 17 Nov 2015 09:09:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2544) RTS inbound bridge recovery does not work with JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2544 stopped 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) From issues at jboss.org Tue Nov 17 09:09:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 17 Nov 2015 09:09:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2561) XTS code coverage failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2561 started by Gytis Trikleris. --------------------------------------------- > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 17 11:16:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Nov 2015 11:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2563) Move package com.arjuna.orbportability.common.ant into our qa testsuite In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2563: -------------------------------------- Summary: Move package com.arjuna.orbportability.common.ant into our qa testsuite Key: JBTM-2563 URL: https://issues.jboss.org/browse/JBTM-2563 Project: JBoss Transaction Manager Issue Type: Task Components: Testing Affects Versions: 5.2.7.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Optional Fix For: 5.later The ant task classes in package com.arjuna.orbportability.common.ant (and config file idl-compiler-definitions.xml) used to be used for compiling IDL stubs in the main build. However we have since moved over to maven and now they are only used in the qa testsuite so it would be cleaner if we moved them into the qa test suite directory. Since the classes are public and we'd need to deprecate first I have marked the JIRA as optional (we may decide the effort involved as not being worthwhile). We also have build-anttasks.xml and orbspecific.xml which I don't think are used at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Nov 18 10:09:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 Nov 2015 10:09:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2252) QA suite failure: CrashRecovery05_2_Test030 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2252: -------------------------------- Description: http://albany.eng.hst.ams2.redhat.com/job/narayana/638/ (was: http://172.17.131.2/view/Status/job/narayana/638/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux) > QA suite failure: CrashRecovery05_2_Test030 > -------------------------------------------- > > Key: JBTM-2252 > URL: https://issues.jboss.org/browse/JBTM-2252 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS, Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > Attachments: CrashRecovery05_2_Test030.tar > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/638/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Nov 18 10:09:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 Nov 2015 10:09:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2196) QA suite failure: CrashRecovery05_2_Test034 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2196: -------------------------------- Description: http://albany.eng.hst.ams2.redhat.com/job/narayana/550/ (was: http://172.17.131.2/view/Status/job/narayana/550/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux) > QA suite failure: CrashRecovery05_2_Test034 > ------------------------------------------- > > Key: JBTM-2196 > URL: https://issues.jboss.org/browse/JBTM-2196 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS, Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > Attachments: CrashRecovery05_2_Test034.tar > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/550/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Nov 18 10:31:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 18 Nov 2015 10:31:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2561) XTS code coverage failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2561 stopped by Gytis Trikleris. --------------------------------------------- > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 07:17:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 07:17:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2511) Benchmark failure testing REST-AT with undertow In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130727#comment-13130727 ] Tom Jenkinson commented on JBTM-2511: ------------------------------------- Are we going to move this out to 5.later or downgrade to minor now that (I believe) we have removed RTS from the main job? > Benchmark failure testing REST-AT with undertow > ----------------------------------------------- > > Key: JBTM-2511 > URL: https://issues.jboss.org/browse/JBTM-2511 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing, REST > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The REST-AT benchmark tests are failing: > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmarks/37/ > and the failure is: > bq. Caused by: javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable > whilst sending a request to a JAX-RS service. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 07:19:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 07:19:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) JBossTS: Quickstart tests failed on pure-ipv6 linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson moved WFLY-5637 to JBTM-2564: ------------------------------------------- Project: JBoss Transaction Manager (was: WildFly) Key: JBTM-2564 (was: WFLY-5637) Component/s: Demonstrator (was: IIOP) (was: Transactions) > JBossTS: Quickstart tests failed on pure-ipv6 linux > --------------------------------------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Tom Jenkinson > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 07:19:01 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 19 Nov 2015 07:19:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2511) Benchmark failure testing REST-AT with undertow In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130730#comment-13130730 ] Michael Musgrove commented on JBTM-2511: ---------------------------------------- I will apply both suggestions, thanks > Benchmark failure testing REST-AT with undertow > ----------------------------------------------- > > Key: JBTM-2511 > URL: https://issues.jboss.org/browse/JBTM-2511 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing, REST > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > The REST-AT benchmark tests are failing: > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmarks/37/ > and the failure is: > bq. Caused by: javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable > whilst sending a request to a JAX-RS service. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 07:19:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 07:19:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) JBossTS: Quickstart tests failed on pure-ipv6 linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2564: ----------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > JBossTS: Quickstart tests failed on pure-ipv6 linux > --------------------------------------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 07:19:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 19 Nov 2015 07:19:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2511) Benchmark failure testing REST-AT with undertow In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2511: ----------------------------------- Priority: Minor (was: Major) > Benchmark failure testing REST-AT with undertow > ----------------------------------------------- > > Key: JBTM-2511 > URL: https://issues.jboss.org/browse/JBTM-2511 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing, REST > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > The REST-AT benchmark tests are failing: > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmarks/37/ > and the failure is: > bq. Caused by: javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable > whilst sending a request to a JAX-RS service. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 07:19:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 19 Nov 2015 07:19:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2511) Benchmark failure testing REST-AT with undertow In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2511: ----------------------------------- Fix Version/s: 5.later (was: 5.next) > Benchmark failure testing REST-AT with undertow > ----------------------------------------------- > > Key: JBTM-2511 > URL: https://issues.jboss.org/browse/JBTM-2511 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing, REST > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > The REST-AT benchmark tests are failing: > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmarks/37/ > and the failure is: > bq. Caused by: javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable > whilst sending a request to a JAX-RS service. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 07:19:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 07:19:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) JBossTS: Quickstart tests failed on pure-ipv6 linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2564: -------------------------------- Fix Version/s: 5.next > JBossTS: Quickstart tests failed on pure-ipv6 linux > --------------------------------------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 07:19:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 07:19:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) JBossTS: Quickstart tests failed on pure-ipv6 linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2564: -------------------------------- Priority: Minor (was: Major) > JBossTS: Quickstart tests failed on pure-ipv6 linux > --------------------------------------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 07:28:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 07:28:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130743#comment-13130743 ] Tom Jenkinson commented on JBTM-2553: ------------------------------------- Any more details on this? > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 07:29:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 07:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2495: -------------------------------- Priority: Minor (was: Major) > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 07:29:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 07:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2497) Update or remove references of HornetQ to Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2497: -------------------------------- Priority: Minor (was: Major) > Update or remove references of HornetQ to Artemis > ------------------------------------------------- > > Key: JBTM-2497 > URL: https://issues.jboss.org/browse/JBTM-2497 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Demonstrator, Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > There were reports of HornetQ still in at least the fooapp QS. We should try to remove references to the specific implementation unless necessary and in those cases use the correct name which is now Artemis. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 07:29:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 07:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2498: -------------------------------- Priority: Minor (was: Major) > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 08:07:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 08:07:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2234) out of memory when logging more messages than heap size (surefire issue) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2234: -------------------------------- Priority: Minor (was: Optional) > out of memory when logging more messages than heap size (surefire issue) > ------------------------------------------------------------------------ > > Key: JBTM-2234 > URL: https://issues.jboss.org/browse/JBTM-2234 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.0.2 > Environment: JTS testing > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > Running com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 on JacORB with about 500000 transactions results in an OOM error because surefire keeps in logs in memory until the test has finished. > In this particular test jacorb logs messages at INFO level for each transaction resulting in excessive memory requirements. We can't make the heap too large because the default JVM is 32 bit. However, we could fix it by reducing the jacorb log level to WARN. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 08:10:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 08:10:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2525) Update to add a test for setting the use-journal-store in wildfly transaction susbystem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2525. ------------------------------- Resolution: Duplicate Issue Duplicated by linked WFLY-5406 > Update to add a test for setting the use-journal-store in wildfly transaction susbystem > --------------------------------------------------------------------------------------- > > Key: JBTM-2525 > URL: https://issues.jboss.org/browse/JBTM-2525 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration, Testing > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > It could be useful to add a test in the CI script -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 08:18:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 08:18:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1804: -------------------------------- Parent: JBTM-2115 Issue Type: Sub-task (was: Task) > 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 > 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) From issues at jboss.org Thu Nov 19 08:24:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 08:24:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2562) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2562. ------------------------------- Resolution: Duplicate Issue I moved the WFLY that Hayk created and so this is now a dup. I kept the WFLY as it has more content and links into the JBEAP. I will add your description to it though > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2562 > URL: https://issues.jboss.org/browse/JBTM-2562 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > We should git clone the quickstart as part of http://172.17.130.4:8083/job/narayana-dualstack/ and try to run it as there as JBEAP-1770 was raised to suggest it won't work on IPv6 due to arquillian config. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 08:24:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 08:24:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2562) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2562: --------------------------------- > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2562 > URL: https://issues.jboss.org/browse/JBTM-2562 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > We should git clone the quickstart as part of http://172.17.130.4:8083/job/narayana-dualstack/ and try to run it as there as JBEAP-1770 was raised to suggest it won't work on IPv6 due to arquillian config. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 08:24:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 08:24:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2562) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2562: -------------------------------- Fix Version/s: (was: 5.next) > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2562 > URL: https://issues.jboss.org/browse/JBTM-2562 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > > We should git clone the quickstart as part of http://172.17.130.4:8083/job/narayana-dualstack/ and try to run it as there as JBEAP-1770 was raised to suggest it won't work on IPv6 due to arquillian config. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 08:25:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 08:25:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2562) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2562. ------------------------------- Resolution: Duplicate Issue > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2562 > URL: https://issues.jboss.org/browse/JBTM-2562 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > > We should git clone the quickstart as part of http://172.17.130.4:8083/job/narayana-dualstack/ and try to run it as there as JBEAP-1770 was raised to suggest it won't work on IPv6 due to arquillian config. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 08:25:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 08:25:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) JBossTS: Quickstart tests failed on pure-ipv6 linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130784#comment-13130784 ] Tom Jenkinson commented on JBTM-2564: ------------------------------------- We should git clone the quickstart as part of http://172.17.130.4:8083/job/narayana-dualstack/ and try to run it as there as JBEAP-1770 was raised to suggest it won't work on IPv6 due to arquillian config. > JBossTS: Quickstart tests failed on pure-ipv6 linux > --------------------------------------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 08:25:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 08:25:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2564: -------------------------------- Summary: Run quickstarts on IPv6 (was: JBossTS: Quickstart tests failed on pure-ipv6 linux) > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 08:25:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 08:25:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2564: -------------------------------- Issue Type: Task (was: Bug) > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 08:46:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 08:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2560) Add generics In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2560. ------------------------------- Resolution: Won't Fix Thankyou for the contribution. As discussed on the forum we are not able to merge this type of change but your input was appreciated and hopefully we can work together in the future. > Add generics > ------------ > > Key: JBTM-2560 > URL: https://issues.jboss.org/browse/JBTM-2560 > Project: JBoss Transaction Manager > Issue Type: Patch > Components: JTA, Recovery, Transaction Core, TxBridge, XTS > Reporter: Philippe Marschall > > Since the source level is Java 5+ the code base can be properly generified. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 08:46:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 08:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2560) Add generics In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130813#comment-13130813 ] Tom Jenkinson commented on JBTM-2560: ------------------------------------- https://developer.jboss.org/message/946219?et=watches.email.thread#946219 > Add generics > ------------ > > Key: JBTM-2560 > URL: https://issues.jboss.org/browse/JBTM-2560 > Project: JBoss Transaction Manager > Issue Type: Patch > Components: JTA, Recovery, Transaction Core, TxBridge, XTS > Reporter: Philippe Marschall > > Since the source level is Java 5+ the code base can be properly generified. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 09:34:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 09:34:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2565) ConnectableResourceRecordRecoveryModule uses tooling iterator which does not report errors and can fail in WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson moved WFLY-5707 to JBTM-2565: ------------------------------------------- Project: JBoss Transaction Manager (was: WildFly) Key: JBTM-2565 (was: WFLY-5707) Component/s: Transaction Core (was: Transactions) Affects Version/s: (was: 10.0.0.CR4) Fix Version/s: 5.next (was: 10.0.0.Final) > ConnectableResourceRecordRecoveryModule uses tooling iterator which does not report errors and can fail in WildFly > ------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2565 > URL: https://issues.jboss.org/browse/JBTM-2565 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > It happens to me that when using jdbc object store for transactions with driver loaded as a module then if I start server and stopped it right after the start is finished I can see error [1] and server stay stuck. I need to run {{kill -9}} to server finish. > This seems to be connected with recovery processing. If I start server and not stopping it immediately after it was started then I do not experience this problem. > But if leave server to run for some time and I decide to stop server at time when periodic recovery is in process (e.g. checking {{server.log}} activity by {{tail -F standalone/log/server.log}} then I experience the same problem. > [1] > {code} > WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012251: allObjUids caught exception: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) > at org.jboss.as.naming.service.DefaultNamespaceContextSelectorService$1.getContext(DefaultNamespaceContextSelectorService.java:56) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:233) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DataSourceJDBCAccess.getConnection(DataSourceJDBCAccess.java:53) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCImple_driver.allObjUids(JDBCImple_driver.java:345) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:166) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:122) > at com.arjuna.ats.arjuna.objectstore.ObjectStoreIterator.(ObjectStoreIterator.java:53) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:390) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" java.lang.NullPointerException > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.arjuna.recovery.TransactionStatusConnectionManager.getTransactionStatus(TransactionStatusConnectionManager.java:92) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:399) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 09:37:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 09:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2565) ConnectableResourceRecordRecoveryModule uses tooling iterator which does not report errors and can fail in WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2565: -------------------------------- Steps to Reproduce: (was: # Configure server to use jdbc object store (you can use the attached configuration) ## copy attached {{standalone-full.xml}} to {{$JBOSS_HOME/standalone/configuration}} # Configure jdbc driver as module - you can use attached jdbc module with oracle driver ## {{cd $JBOSS_HOME}} ## {{unzip jdbc-module.zip}} # Start server ## {{./bin/standalone.sh -c standalone-full.xml}} # Stop server by pressing CTRL+C immediatelly when you see message: {{INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: EAP 7.0.0.Alpha1 (WildFly Core 2.0.0.CR8) started in 8432ms - Started 305 of 535 services (331 services are lazy, passive or on-demand)}} ## you need to stop the server during recovery is in process. you can also wait for recovery being run and then stop the server. the period for waiting for recovery could be change from default 2min by adding parameter {{./bin/standalone.sh -c standalone-full.xml -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=30}}) > ConnectableResourceRecordRecoveryModule uses tooling iterator which does not report errors and can fail in WildFly > ------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2565 > URL: https://issues.jboss.org/browse/JBTM-2565 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > It happens to me that when using jdbc object store for transactions with driver loaded as a module then if I start server and stopped it right after the start is finished I can see error [1] and server stay stuck. I need to run {{kill -9}} to server finish. > This seems to be connected with recovery processing. If I start server and not stopping it immediately after it was started then I do not experience this problem. > But if leave server to run for some time and I decide to stop server at time when periodic recovery is in process (e.g. checking {{server.log}} activity by {{tail -F standalone/log/server.log}} then I experience the same problem. > [1] > {code} > WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012251: allObjUids caught exception: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) > at org.jboss.as.naming.service.DefaultNamespaceContextSelectorService$1.getContext(DefaultNamespaceContextSelectorService.java:56) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:233) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DataSourceJDBCAccess.getConnection(DataSourceJDBCAccess.java:53) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCImple_driver.allObjUids(JDBCImple_driver.java:345) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:166) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:122) > at com.arjuna.ats.arjuna.objectstore.ObjectStoreIterator.(ObjectStoreIterator.java:53) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:390) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" java.lang.NullPointerException > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.arjuna.recovery.TransactionStatusConnectionManager.getTransactionStatus(TransactionStatusConnectionManager.java:92) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:399) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 09:45:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 09:45:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2565) ConnectableResourceRecordRecoveryModule uses tooling iterator which does not report errors and can fail in WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2565: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/945 > ConnectableResourceRecordRecoveryModule uses tooling iterator which does not report errors and can fail in WildFly > ------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2565 > URL: https://issues.jboss.org/browse/JBTM-2565 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > It happens to me that when using jdbc object store for transactions with driver loaded as a module then if I start server and stopped it right after the start is finished I can see error [1] and server stay stuck. I need to run {{kill -9}} to server finish. > This seems to be connected with recovery processing. If I start server and not stopping it immediately after it was started then I do not experience this problem. > But if leave server to run for some time and I decide to stop server at time when periodic recovery is in process (e.g. checking {{server.log}} activity by {{tail -F standalone/log/server.log}} then I experience the same problem. > [1] > {code} > WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012251: allObjUids caught exception: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) > at org.jboss.as.naming.service.DefaultNamespaceContextSelectorService$1.getContext(DefaultNamespaceContextSelectorService.java:56) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:233) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DataSourceJDBCAccess.getConnection(DataSourceJDBCAccess.java:53) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCImple_driver.allObjUids(JDBCImple_driver.java:345) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:166) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:122) > at com.arjuna.ats.arjuna.objectstore.ObjectStoreIterator.(ObjectStoreIterator.java:53) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:390) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" java.lang.NullPointerException > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.arjuna.recovery.TransactionStatusConnectionManager.getTransactionStatus(TransactionStatusConnectionManager.java:92) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:399) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 09:48:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 09:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-855: ------------------------------- Priority: Minor (was: Major) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 09:48:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 09:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2480: -------------------------------- Priority: Minor (was: Major) > Provide documentation of how to integrate with Karaf > ---------------------------------------------------- > > Key: JBTM-2480 > URL: https://issues.jboss.org/browse/JBTM-2480 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > This should include recovery information -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 09:49:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 09:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2561) XTS code coverage failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2561: -------------------------------- Parent: JBTM-2115 Issue Type: Sub-task (was: Bug) > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 12:36:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 19 Nov 2015 12:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131043#comment-13131043 ] Michael Musgrove commented on JBTM-2564: ---------------------------------------- [~hhovsepy] tried updating the arquillian config on one of his test machines that has IPv4 disabled and it resolved the problem so I think we are good to go with the fix. > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 12:46:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 12:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2565) ConnectableResourceRecordRecoveryModule uses tooling iterator which does not report errors and can fail in WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2565: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ConnectableResourceRecordRecoveryModule uses tooling iterator which does not report errors and can fail in WildFly > ------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2565 > URL: https://issues.jboss.org/browse/JBTM-2565 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > It happens to me that when using jdbc object store for transactions with driver loaded as a module then if I start server and stopped it right after the start is finished I can see error [1] and server stay stuck. I need to run {{kill -9}} to server finish. > This seems to be connected with recovery processing. If I start server and not stopping it immediately after it was started then I do not experience this problem. > But if leave server to run for some time and I decide to stop server at time when periodic recovery is in process (e.g. checking {{server.log}} activity by {{tail -F standalone/log/server.log}} then I experience the same problem. > [1] > {code} > WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012251: allObjUids caught exception: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) > at org.jboss.as.naming.service.DefaultNamespaceContextSelectorService$1.getContext(DefaultNamespaceContextSelectorService.java:56) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:233) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DataSourceJDBCAccess.getConnection(DataSourceJDBCAccess.java:53) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCImple_driver.allObjUids(JDBCImple_driver.java:345) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:166) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:122) > at com.arjuna.ats.arjuna.objectstore.ObjectStoreIterator.(ObjectStoreIterator.java:53) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:390) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" java.lang.NullPointerException > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.arjuna.recovery.TransactionStatusConnectionManager.getTransactionStatus(TransactionStatusConnectionManager.java:92) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:399) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 12:48:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 12:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2566) ObjectStoreIterator can silently fail if there is an ObjectStoreException in the CTOR In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2566: ----------------------------------- Summary: ObjectStoreIterator can silently fail if there is an ObjectStoreException in the CTOR Key: JBTM-2566 URL: https://issues.jboss.org/browse/JBTM-2566 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Tooling, Transaction Core Reporter: Tom Jenkinson Assignee: Michael Musgrove Fix For: 5.next Detected during https://issues.jboss.org/browse/JBTM-2565 and worked around in CMR but it should be reviewed for the tooling use cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 12:56:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 19 Nov 2015 12:56:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131043#comment-13131043 ] Michael Musgrove edited comment on JBTM-2564 at 11/19/15 12:55 PM: ------------------------------------------------------------------- [~hhovsepy] tried updating the arquillian config on one of his test machines that has IPv4 disabled and it resolved the problem so I think we are good to go with the fix. And the properties that Hayk used were: bq.-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true was (Author: mmusgrov): [~hhovsepy] tried updating the arquillian config on one of his test machines that has IPv4 disabled and it resolved the problem so I think we are good to go with the fix. > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 13:02:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 13:02:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2566) ObjectStoreIterator can silently fail if there is an ObjectStoreException in the CTOR In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2566: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/946 > ObjectStoreIterator can silently fail if there is an ObjectStoreException in the CTOR > ------------------------------------------------------------------------------------- > > Key: JBTM-2566 > URL: https://issues.jboss.org/browse/JBTM-2566 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Tooling, Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Detected during https://issues.jboss.org/browse/JBTM-2565 and worked around in CMR but it should be reviewed for the tooling use cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 19 13:08:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 19 Nov 2015 13:08:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131052#comment-13131052 ] Tom Jenkinson commented on JBTM-2564: ------------------------------------- So do I need to add those to all the quickstart poms? > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:04:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:04:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2565) ConnectableResourceRecordRecoveryModule uses tooling iterator which does not report errors and can fail in WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2565. ------------------------------- > ConnectableResourceRecordRecoveryModule uses tooling iterator which does not report errors and can fail in WildFly > ------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2565 > URL: https://issues.jboss.org/browse/JBTM-2565 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.8.Final > > > It happens to me that when using jdbc object store for transactions with driver loaded as a module then if I start server and stopped it right after the start is finished I can see error [1] and server stay stuck. I need to run {{kill -9}} to server finish. > This seems to be connected with recovery processing. If I start server and not stopping it immediately after it was started then I do not experience this problem. > But if leave server to run for some time and I decide to stop server at time when periodic recovery is in process (e.g. checking {{server.log}} activity by {{tail -F standalone/log/server.log}} then I experience the same problem. > [1] > {code} > WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012251: allObjUids caught exception: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) > at org.jboss.as.naming.service.DefaultNamespaceContextSelectorService$1.getContext(DefaultNamespaceContextSelectorService.java:56) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:233) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DataSourceJDBCAccess.getConnection(DataSourceJDBCAccess.java:53) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCImple_driver.allObjUids(JDBCImple_driver.java:345) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:166) > at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:122) > at com.arjuna.ats.arjuna.objectstore.ObjectStoreIterator.(ObjectStoreIterator.java:53) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:390) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" java.lang.NullPointerException > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.arjuna.recovery.TransactionStatusConnectionManager.getTransactionStatus(TransactionStatusConnectionManager.java:92) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:399) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747) > ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:04:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:04:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2559) CrashRecovery02_2_Test28 failure on JDKORB and with journal storage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2559. ------------------------------- > CrashRecovery02_2_Test28 failure on JDKORB and with journal storage > ------------------------------------------------------------------- > > Key: JBTM-2559 > URL: https://issues.jboss.org/browse/JBTM-2559 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.2.8.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:05:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2558) CI report generator error while getting issue info In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2558. ------------------------------- > CI report generator error while getting issue info > -------------------------------------------------- > > Key: JBTM-2558 > URL: https://issues.jboss.org/browse/JBTM-2558 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: CI Report Generator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.2.8.Final > > > {code} > Aggregating narayana build 979 > Aggregating narayana build 978 > Aggregating narayana build 863 > Aggregating narayana build 858 > Aggregating narayana build 830 > Aggregating narayana build 779 > Aggregating narayana build 638 > Aggregating narayana build 550 > Aggregating narayana-benchmarks build 56 > Got an error while getting issue info: [object Object] >  > TypeError: Uncaught, unspecified "error" event. > at TypeError () > at DestroyableTransform.emit (events.js:74:15) > at DestroyableTransform.onerror (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:604:12) > at DestroyableTransform.emit (events.js:95:17) > at onwriteError (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:345:10) > at onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:363:5) > at WritableState.onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:123:5) > at afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:84:5) > at TransformState.afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:59:12) > at /home/hudson/workspace/ci-report-generator/streams/jiraInfoStream.js:23:17 > Warning: -> error 8 /home/hudson/workspace/ci-report-generator/index.js (8883ms) Use --force to continue. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:05:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2557) Support Spring PlatformTransactionManager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2557. ------------------------------- > Support Spring PlatformTransactionManager > ----------------------------------------- > > Key: JBTM-2557 > URL: https://issues.jboss.org/browse/JBTM-2557 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Reporter: Amos Feng > Assignee: Guillaume Nodet > Fix For: 5.2.8.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:05:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2556) Improve OSGi integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2556. ------------------------------- > Improve OSGi integration > ------------------------ > > Key: JBTM-2556 > URL: https://issues.jboss.org/browse/JBTM-2556 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Amos Feng > Assignee: Guillaume Nodet > Fix For: 5.2.8.Final > > > support configuration using ConfigAdmin > track org.jboss.tm.XAResourceRecovery services for recovery > In order to support correctly stopping / restarting / reconfiguring the transaction manager, we build our own class loader to load the core jars. > This ensure that all static fields will be correctly reloaded when starting again after configuration change. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:05:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2555) JOTM benchmark produces too many rollback exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2555. ------------------------------- > JOTM benchmark produces too many rollback exceptions > ---------------------------------------------------- > > Key: JBTM-2555 > URL: https://issues.jboss.org/browse/JBTM-2555 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.8.Final > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-benchmarks/52/ > The rollbacks are most likely due to transaction timeouts (even though I set the threshold for failure to not more than 10 rollbacks). > It is possible that JOTM just cannot cope with the number of threads we using to produce the benchmark. I have tried to reproduce the failures with a standalone junit test and using JMH on my laptop without success. > I am going to remove JOTM from the comparison matrix (see job narayana-benchmarks) until this JIRA is resolved. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:05:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2554. ------------------------------- > CrashRecovery05_2 failures on JacORB > ------------------------------------ > > Key: JBTM-2554 > URL: https://issues.jboss.org/browse/JBTM-2554 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.2.8.Final > > > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:05:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2552) Benchmark script should accept extra script arguments In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2552. ------------------------------- > Benchmark script should accept extra script arguments > ----------------------------------------------------- > > Key: JBTM-2552 > URL: https://issues.jboss.org/browse/JBTM-2552 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.7.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.8.Final > > > The launch script for running benchmarks (narayana/scripts/hudson/benchmark.sh in the repo https://github.com/jbosstm/performance) should propagate any script arguments through to the benchmark script. > I plan to use this for configuring things like the transaction timeout value and to configure how many commit failures are tolerated before failing the job. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:05:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2551) CrashRecovery02_1_Test05 failure on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2551. ------------------------------- > 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.2.8.Final > > 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) From issues at jboss.org Fri Nov 20 06:05:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) ClassNotFoundException when restore_state from the object store during recovering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2550. ------------------------------- > 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.2.8.Final > > > 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) From issues at jboss.org Fri Nov 20 06:05:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2549) CrashRecovery05_2_Test002 failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2549. ------------------------------- > CrashRecovery05_2_Test002 failure > --------------------------------- > > Key: JBTM-2549 > URL: https://issues.jboss.org/browse/JBTM-2549 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.7.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.8.Final > > > There are a number of failures in the CrashRecovery05_1 and CrashRecovery05_2 test groups with a similar root cause: > Tests that use AfterCrashServiceImpl01#check_oper and AfterCrashServiceImpl02#check_oper with JdkORB fail because they make invalid assumptions about the return value of RecoveryCoordinator#replay_completion. The OTS spec says "This (replay_completion) non-blocking operation returns the current status of the transaction" but the check_oper() test assumes that the return value represents the transaction status after all resources have been replayed and therefore returns the wrong result to the requesting client. The fix is to ask the resources for their status after the replay_completion attempt (but also waiting for the resource to have been replayed). I tested the hypothesis by forcing a 200ms wait after issuing replay_completion on the RecoveryCoordinator object (but I will use a rendezvous for the actual fix). > There is a second problem with the way these tests are coded since they ignore the fact that replay_completion reruns phase 2 on all resources whereas the test relies on it being done on only the requested resource). A test sequence is as follows: > # client starts a transaction > # asks service1 to create a resource1 > # asks service2 to create a resource2 > # client commits the transaction (one of which crashes during 2PC) > # restart the server (hosting the services) > # client asks service1 for the status of the first resource > # service1 invokes replay_completion on the RecoveryCoordinator for resource1 > # this causes a recovery attempt on both resources > # client asks service2 for the status of the second resource > # service2 invokes replay_completion on the RecoveryCoordinator for resource2 > # but this will fail because the transaction was completed during steps 7 and 8 so the > # transaction log no longer exists and the recovery attempt calls rollback on resource2 > The fix is to store the transaction Status with the resources and have the service ask the resources for the state (rather than the return value of the replay_completion request). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:05:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2548) CrashRecovery05_2_Test076 (through CrashRecovery05_2_Test100) failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2548. ------------------------------- > CrashRecovery05_2_Test076 (through CrashRecovery05_2_Test100) failures > ---------------------------------------------------------------------- > > Key: JBTM-2548 > URL: https://issues.jboss.org/browse/JBTM-2548 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.7.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.8.Final > > > These tests typically start 2 servers and crash one of them in various ways. > Then the two servers are restarted but the tests fail because the recovery port used by one of the two servers is stuck in the TIME-WAIT state so the server restart gets a "Bind: Address Already in Use" error. > I propose to fix this by doing a retry and backoff approach. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:05:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2545) Use consistent naming scheme for ORB jbossts-properties files in the repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2545. ------------------------------- > Use consistent naming scheme for ORB jbossts-properties files in the repo > ------------------------------------------------------------------------- > > Key: JBTM-2545 > URL: https://issues.jboss.org/browse/JBTM-2545 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.2.8.Final > > > This simplifies testing makes the tests more consistent. The overall effect on the user is that the default filenames are clearer rather than assuming jacorb. > Plus the fact that narayana-jacorb module has narayana-idlj file in (which is an error IMO) - and the converse is also true. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:05:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2547) CrashRecovery02_2_Test01 failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2547. ------------------------------- > 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.2.8.Final > > > 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) From issues at jboss.org Fri Nov 20 06:05:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2538) Benchmarking failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2538. ------------------------------- > 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.2.8.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:05:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2534) HQStore crashrec failures on QA_JTS_JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2534. ------------------------------- > HQStore crashrec failures on QA_JTS_JDKORB > ------------------------------------------ > > Key: JBTM-2534 > URL: https://issues.jboss.org/browse/JBTM-2534 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.2.8.Final > > > Killed this one: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/127/ > Normally run to completion but lots of crash rec failures: > {quote} > Total time: 525 minutes 19 seconds > Test Failures: > crashrecovery02_2 CrashRecovery02_2_Test01 Fail (0m50.031s) > crashrecovery02_2 CrashRecovery02_2_Test06 Fail (0m43.914s) > crashrecovery02_2 CrashRecovery02_2_Test07 Fail (0m48.270s) > crashrecovery02_2 CrashRecovery02_2_Test08 Fail (0m48.340s) > crashrecovery02_2 CrashRecovery02_2_Test09 Fail (0m48.014s) > crashrecovery02_2 CrashRecovery02_2_Test10 Fail (0m47.865s) > crashrecovery02_2 CrashRecovery02_2_Test11 Fail (0m48.756s) > crashrecovery02_2 CrashRecovery02_2_Test12 Fail (0m47.992s) > crashrecovery02_2 CrashRecovery02_2_Test13 Fail (0m47.840s) > crashrecovery02_2 CrashRecovery02_2_Test14 Fail (0m47.948s) > crashrecovery02_2 CrashRecovery02_2_Test15 Fail (0m47.742s) > crashrecovery02_2 CrashRecovery02_2_Test16 Fail (0m48.953s) > crashrecovery02_2 CrashRecovery02_2_Test02 Fail (0m48.202s) > crashrecovery02_2 CrashRecovery02_2_Test03 Fail (2m3.776s) > crashrecovery02_2 CrashRecovery02_2_Test04 Fail (0m47.686s) > crashrecovery02_2 CrashRecovery02_2_Test05 Fail (0m47.859s) > crashrecovery02_2 CrashRecovery02_2_Test17 Fail (0m48.029s) > crashrecovery02_2 CrashRecovery02_2_Test18 Fail (0m47.658s) > crashrecovery02_2 CrashRecovery02_2_Test19 Fail (0m47.775s) > crashrecovery02_2 CrashRecovery02_2_Test20 Fail (0m48.086s) > crashrecovery02_2 CrashRecovery02_2_Test21 Fail (0m47.979s) > crashrecovery02_2 CrashRecovery02_2_Test22 Fail (0m48.137s) > crashrecovery02_2 CrashRecovery02_2_Test23 Fail (0m48.267s) > crashrecovery02_2 CrashRecovery02_2_Test24 Fail (0m48.100s) > crashrecovery02_2 CrashRecovery02_2_Test25 Fail (0m47.787s) > crashrecovery05_1 CrashRecovery05_1_Test01 Fail (1m17.781s) > crashrecovery05_1 CrashRecovery05_1_Test10 Fail (1m18.510s) > crashrecovery05_1 CrashRecovery05_1_Test06 Fail (1m17.647s) > crashrecovery05_1 CrashRecovery05_1_Test07 Fail (1m17.572s) > crashrecovery05_1 CrashRecovery05_1_Test08 Fail (1m17.365s) > crashrecovery05_1 CrashRecovery05_1_Test09 Fail (1m17.263s) > crashrecovery05_2 CrashRecovery05_2_Test051 Fail (2m3.491s) > crashrecovery05_2 CrashRecovery05_2_Test052 Fail (0m48.481s) > crashrecovery05_2 CrashRecovery05_2_Test053 Fail (2m3.698s) > crashrecovery05_2 CrashRecovery05_2_Test054 Fail (0m47.293s) > crashrecovery05_2 CrashRecovery05_2_Test055 Fail (0m48.382s) > crashrecovery05_2 CrashRecovery05_2_Test056 Fail (0m43.458s) > crashrecovery05_2 CrashRecovery05_2_Test057 Fail (0m49.076s) > crashrecovery05_2 CrashRecovery05_2_Test058 Fail (0m43.988s) > crashrecovery05_2 CrashRecovery05_2_Test059 Fail (0m48.177s) > crashrecovery05_2 CrashRecovery05_2_Test060 Fail (0m47.995s) > crashrecovery05_2 CrashRecovery05_2_Test061 Fail (0m48.266s) > crashrecovery05_2 CrashRecovery05_2_Test062 Fail (0m47.852s) > crashrecovery05_2 CrashRecovery05_2_Test063 Fail (2m3.059s) > crashrecovery05_2 CrashRecovery05_2_Test064 Fail (0m47.332s) > crashrecovery05_2 CrashRecovery05_2_Test065 Fail (0m47.226s) > crashrecovery05_2 CrashRecovery05_2_Test066 Fail (0m47.141s) > crashrecovery05_2 CrashRecovery05_2_Test067 Fail (0m47.195s) > crashrecovery05_2 CrashRecovery05_2_Test068 Fail (0m47.464s) > crashrecovery05_2 CrashRecovery05_2_Test069 Fail (0m49.360s) > crashrecovery05_2 CrashRecovery05_2_Test070 Fail (0m47.700s) > crashrecovery05_2 CrashRecovery05_2_Test071 Fail (0m47.782s) > crashrecovery05_2 CrashRecovery05_2_Test072 Fail (0m47.736s) > crashrecovery05_2 CrashRecovery05_2_Test073 Fail (0m47.438s) > crashrecovery05_2 CrashRecovery05_2_Test074 Fail (0m47.701s) > crashrecovery05_2 CrashRecovery05_2_Test075 Fail (0m47.385s) > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m10.036s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m54.372s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m10.928s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m55.124s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m54.970s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m50.656s) > crashrecovery05_2 CrashRecovery05_2_Test082 Fail (0m54.356s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m50.052s) > crashrecovery05_2 CrashRecovery05_2_Test084 Fail (0m53.605s) > crashrecovery05_2 CrashRecovery05_2_Test085 Fail (0m54.694s) > crashrecovery05_2 CrashRecovery05_2_Test086 Fail (0m54.147s) > crashrecovery05_2 CrashRecovery05_2_Test087 Fail (0m54.397s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m11.261s) > crashrecovery05_2 CrashRecovery05_2_Test089 Fail (0m54.332s) > crashrecovery05_2 CrashRecovery05_2_Test090 Fail (0m55.264s) > crashrecovery05_2 CrashRecovery05_2_Test091 Fail (0m54.471s) > crashrecovery05_2 CrashRecovery05_2_Test092 Fail (0m54.046s) > crashrecovery05_2 CrashRecovery05_2_Test093 Fail (0m54.249s) > crashrecovery05_2 CrashRecovery05_2_Test094 Fail (0m54.388s) > crashrecovery05_2 CrashRecovery05_2_Test095 Fail (0m53.763s) > crashrecovery05_2 CrashRecovery05_2_Test096 Fail (0m54.313s) > crashrecovery05_2 CrashRecovery05_2_Test097 Fail (0m54.069s) > crashrecovery05_2 CrashRecovery05_2_Test098 Fail (0m54.290s) > crashrecovery05_2 CrashRecovery05_2_Test099 Fail (0m55.164s) > crashrecovery05_2 CrashRecovery05_2_Test100 Fail (0m54.189s) > crashrecovery05_2 CrashRecovery05_2_Test002 Fail (0m46.793s) > crashrecovery05_2 CrashRecovery05_2_Test003 Fail (2m2.944s) > crashrecovery05_2 CrashRecovery05_2_Test005 Fail (0m46.742s) > crashrecovery05_2 CrashRecovery05_2_Test006 Fail (0m42.978s) > crashrecovery05_2 CrashRecovery05_2_Test028 Fail (2m9.683s) > crashrecovery05_2 CrashRecovery05_2_Test031 Fail (0m49.745s) > crashrecovery12 CrashRecovery12_Test03 Fail (0m15.884s) > Buildfile: /home/hudson/workspace/narayana-hqstore/PROFILE/QA_JTS_JDKORB/jdk/jdk8.latest/label/linux/qa/run-tests.xml > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2532) Enable code coverage for XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2532. ------------------------------- > 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.2.8.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2318) Too verbose startup? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2318. ------------------------------- > Too verbose startup? > -------------------- > > Key: JBTM-2318 > URL: https://issues.jboss.org/browse/JBTM-2318 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.2.8.Final > > > At startup of the most basic example we see ... > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService > INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem > INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start > INFO: ARJUNA012170: TransactionStatusManager started on port 52185 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > There's a separate conversation to be had about whether the INFO should be there (DEBUG maybe?) but ignoring those why do we print the other lines at all? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2566) ObjectStoreIterator can silently fail if there is an ObjectStoreException in the CTOR In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2566: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > ObjectStoreIterator can silently fail if there is an ObjectStoreException in the CTOR > ------------------------------------------------------------------------------------- > > Key: JBTM-2566 > URL: https://issues.jboss.org/browse/JBTM-2566 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Tooling, Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Detected during https://issues.jboss.org/browse/JBTM-2565 and worked around in CMR but it should be reviewed for the tooling use cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2564: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2561) XTS code coverage failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2561: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2553: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2544) RTS inbound bridge recovery does not work with JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2544: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > 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) From issues at jboss.org Fri Nov 20 06:06:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2522) Update performance comparison tests to use JMH In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2522: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Update performance comparison tests to use JMH > ---------------------------------------------- > > Key: JBTM-2522 > URL: https://issues.jboss.org/browse/JBTM-2522 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2498: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2497) Update or remove references of HornetQ to Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2497: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Update or remove references of HornetQ to Artemis > ------------------------------------------------- > > Key: JBTM-2497 > URL: https://issues.jboss.org/browse/JBTM-2497 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Demonstrator, Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > There were reports of HornetQ still in at least the fooapp QS. We should try to remove references to the specific implementation unless necessary and in those cases use the correct name which is now Artemis. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2495: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2481) Automate NRP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2481: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2480: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Provide documentation of how to integrate with Karaf > ---------------------------------------------------- > > Key: JBTM-2480 > URL: https://issues.jboss.org/browse/JBTM-2480 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > This should include recovery information -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2433: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > TransactionRolledBackException in MultiCloseTest > ------------------------------------------------ > > Key: JBTM-2433 > URL: https://issues.jboss.org/browse/JBTM-2433 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt > > > It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion. > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! > testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2458) Think of the possibility to improve Compensations API with lambdas In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2458: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Think of the possibility to improve Compensations API with lambdas > ------------------------------------------------------------------ > > Key: JBTM-2458 > URL: https://issues.jboss.org/browse/JBTM-2458 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Emmanuel suggested to reduce verbosity in Compensations API by making it possible to use lambdas for handler implementation. > We should try to think of the best API changes to introduce that. > We could rewrite MongoDB quickstart to make it easier to visualise the difference. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2298) Use Project Atomic for docker image(s) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2298: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Use Project Atomic for docker image(s) > -------------------------------------- > > Key: JBTM-2298 > URL: https://issues.jboss.org/browse/JBTM-2298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > > 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) From issues at jboss.org Fri Nov 20 06:06:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2234) out of memory when logging more messages than heap size (surefire issue) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2234: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > out of memory when logging more messages than heap size (surefire issue) > ------------------------------------------------------------------------ > > Key: JBTM-2234 > URL: https://issues.jboss.org/browse/JBTM-2234 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.0.2 > Environment: JTS testing > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > Running com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 on JacORB with about 500000 transactions results in an OOM error because surefire keeps in logs in memory until the test has finished. > In this particular test jacorb logs messages at INFO level for each transaction resulting in excessive memory requirements. We can't make the heap too large because the default JVM is 32 bit. However, we could fix it by reducing the jacorb log level to WARN. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2206) Use synchronized HashMaps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2206: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Use synchronized HashMaps > ------------------------- > > Key: JBTM-2206 > URL: https://issues.jboss.org/browse/JBTM-2206 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Transaction Core > Reporter: Jesper Pedersen > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Change usage of Hashtable into synchronized HashMap's instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2203) Remove ReentrantLock from StateManager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2203: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Remove ReentrantLock from StateManager > -------------------------------------- > > Key: JBTM-2203 > URL: https://issues.jboss.org/browse/JBTM-2203 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Remove unused lock from StateManager, and add the access methods to LockManager instead -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2115) Not all classes are under code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2115: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > compensations/pom.xml > txframework/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-855: ------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:06:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:06:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1804: -------------------------------- Fix Version/s: 5.next (was: 5.2.8.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 > 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) From issues at jboss.org Fri Nov 20 06:07:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:07:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-741: ------------------------------- Fix Version/s: 5.next (was: 5.2.8.Final) > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Fix For: 5.next > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:24:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:24:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2566) ObjectStoreIterator can silently fail if there is an ObjectStoreException in the CTOR In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2566: -------------------------------- Issue Type: Bug (was: Feature Request) > ObjectStoreIterator can silently fail if there is an ObjectStoreException in the CTOR > ------------------------------------------------------------------------------------- > > Key: JBTM-2566 > URL: https://issues.jboss.org/browse/JBTM-2566 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling, Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Detected during https://issues.jboss.org/browse/JBTM-2565 and worked around in CMR but it should be reviewed for the tooling use cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 06:48:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 06:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132084#comment-13132084 ] Tom Jenkinson commented on JBTM-2564: ------------------------------------- Because if so we need to do it in a profile at a guess. Unless those arguments work on an IPv6 box. Do we know which quickstarts need those? [~hhovsepy] - can you raise a PR if you have the fix on your box so we can check it works on our CI cluster too please? > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 07:00:00 2015 From: issues at jboss.org (Hayk Hovsepyan (JIRA)) Date: Fri, 20 Nov 2015 07:00:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132090#comment-13132090 ] Hayk Hovsepyan commented on JBTM-2564: -------------------------------------- It fails for these quickstarts: "jta-1_2-in-wildfly" "compensating-transactions/travel-agent" "rts/at/jta-service/jpa" "rts/at/jta-service/jms" But I do not have a PR for this fix, I thought [~mmusgrov] is going to fix this. /Hayk. > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 07:06:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 07:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132092#comment-13132092 ] Tom Jenkinson commented on JBTM-2564: ------------------------------------- Hi [~hhovsepy] - I thought Mike said you had tested a fix locally? If so, please can you commit it and PR it and I can amend it as necessary? Alternatively just paste in the surefire config you tested as a comment and I will try it here. > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 07:28:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 20 Nov 2015 07:28:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132101#comment-13132101 ] Michael Musgrove commented on JBTM-2564: ---------------------------------------- [~tomjenkinson] The fix we need is a maven profile that will set up the correct IPv6 -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true (same as how we do it on master) and an update to the READMEs. Hayk tested out this fix manually (ie a direct edit of one of the arquillan.xml files) on a server that had IPv4 disabled. > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 07:33:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 20 Nov 2015 07:33:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132102#comment-13132102 ] Michael Musgrove commented on JBTM-2564: ---------------------------------------- [~tomjenkinson] We have jobs that test the fix on dual stack machines: http://172.17.130.4:8083/job/narayana-quickstarts-ipv6/ and http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-ipv6/ > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 20 07:38:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Nov 2015 07:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132105#comment-13132105 ] Tom Jenkinson commented on JBTM-2564: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-ipv6/ ?? I didn't even think we had dualstack machines in ams2? If so we should move the dualstack job onto ams2 cluster instead of ncl one. > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Nov 22 15:36:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sun, 22 Nov 2015 15:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2405) QA suite failure: CrashRecovery05_1_Test04 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-2405. ---------------------------------- Resolution: Duplicate Issue I believe (but cannot be definitive since the logs are missing) that this issue has been fixed by commits made against JBTM-2554 which applied fixes to the server and resource used by the failing test (AfterCrashServiceImpl01 and ResourceImpl02). > QA suite failure: CrashRecovery05_1_Test04 > ------------------------------------------ > > Key: JBTM-2405 > URL: https://issues.jboss.org/browse/JBTM-2405 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/830/PROFILE=QA_JTS_JACORB,jdk=jdk8.latest,label=linux/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Nov 22 15:38:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sun, 22 Nov 2015 15:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2360) QA suite failure: CrashRecovery05_2_Test045 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-2360. ---------------------------------- Resolution: Duplicate Issue I believe (but cannot be definitive since the logs are missing) that this issue has been fixed by commits made against JBTM-2554 which applied fixes to the server and resource used by the failing test (AfterCrashServiceImpl01 and ResourceImpl02). > QA suite failure: CrashRecovery05_2_Test045 > ------------------------------------------- > > Key: JBTM-2360 > URL: https://issues.jboss.org/browse/JBTM-2360 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/779/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux/ > I had a look and there are some messages that suggest that the connection was broken. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Nov 22 15:39:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sun, 22 Nov 2015 15:39:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2126) QA suite failure: CrashRecovery05_2_Test008 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-2126. ---------------------------------- Resolution: Duplicate Issue I believe (but cannot be definitive since the logs are missing) that this issue has been fixed by commits made against JBTM-2554 which applied fixes to the server and resource used by the failing test (AfterCrashServiceImpl01 and ResourceImpl02). > QA suite failure: CrashRecovery05_2_Test008 > ------------------------------------------- > > Key: JBTM-2126 > URL: https://issues.jboss.org/browse/JBTM-2126 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/466/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 23 05:11:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Nov 2015 05:11:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2561) XTS code coverage failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132514#comment-13132514 ] Tom Jenkinson commented on JBTM-2561: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-codeCoverage/261/ > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 23 05:34:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Nov 2015 05:34:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2567) QA Suite Failure: TestGroup_crashrecovery02_2 failed (hqstore/JDKORB) In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2567: ----------------------------------- Summary: QA Suite Failure: TestGroup_crashrecovery02_2 failed (hqstore/JDKORB) Key: JBTM-2567 URL: https://issues.jboss.org/browse/JBTM-2567 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Testing Reporter: Tom Jenkinson Assignee: Gytis Trikleris Priority: Minor Fix For: 5.next http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/135/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 23 05:36:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Nov 2015 05:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2567) QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2567: -------------------------------- Summary: QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB) (was: QA Suite Failure: TestGroup_crashrecovery02_2 failed (hqstore/JDKORB)) > QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB) > ------------------------------------------------------------ > > Key: JBTM-2567 > URL: https://issues.jboss.org/browse/JBTM-2567 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/135/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 23 05:43:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Nov 2015 05:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2561) XTS code coverage failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132529#comment-13132529 ] Tom Jenkinson commented on JBTM-2561: ------------------------------------- Added a repeating job to test this: http://albany.eng.hst.ams2.redhat.com/job/JBTM-2561/ (waiting for [~zhfeng] to update jboss-as/5_BRANCH though) > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 23 09:39:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 23 Nov 2015 09:39:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2561) XTS code coverage failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132685#comment-13132685 ] Amos Feng commented on JBTM-2561: --------------------------------- updated 5_BRANCH to 5.2.9.Final-SNAPSHOT > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 24 07:02:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 24 Nov 2015 07:02:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2567) QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133133#comment-13133133 ] Michael Musgrove commented on JBTM-2567: ---------------------------------------- This failure is similar to the ones we saw in TestGroup_crashrecovery05_2 which I resolved by making some fixes (git sha 5159ae) to the services and resources used by that test group. This new failure in TestGroup_crashrecovery02_2 is using services and resources that look more or less identical to the ones I fixed earlier. I will therefore port those fixes to TestGroup_crashrecovery02_2 > QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB) > ------------------------------------------------------------ > > Key: JBTM-2567 > URL: https://issues.jboss.org/browse/JBTM-2567 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/135/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 24 11:00:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 24 Nov 2015 11:00:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2567) QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reassigned JBTM-2567: -------------------------------------- Assignee: Michael Musgrove (was: Gytis Trikleris) > QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB) > ------------------------------------------------------------ > > Key: JBTM-2567 > URL: https://issues.jboss.org/browse/JBTM-2567 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/135/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Nov 24 17:04:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 24 Nov 2015 17:04:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2568) Add config options to enable fine grained control of what's tested in a PR In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2568: -------------------------------------- Summary: Add config options to enable fine grained control of what's tested in a PR Key: JBTM-2568 URL: https://issues.jboss.org/browse/JBTM-2568 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Testing Affects Versions: 5.2.8.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Optional Fix For: 5.next Currently we have a fixed set of Jenkins CI config profiles when testing PRs (QA_JTS_JDKORB, QA_JTA, XTS, MAIN, BLACKTIE and PERF) and we are allowed to selectively disable one or more of them. It would be handy to be able to control other things such as running QA tests using the journal store (which none of the above QA profiles allow). It would also be a handy shortcut to explicitly set which profile to run (as opposed to which ones to disable). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Nov 25 04:58:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 25 Nov 2015 04:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2298) Use Project Atomic for docker image(s) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133640#comment-13133640 ] Gytis Trikleris commented on JBTM-2298: --------------------------------------- [~marklittle], just wanted to confirm, if by "Project Atomic docker image" you meant Atomic App [1]? [1] http://www.projectatomic.io/docs/atomicapp/ > Use Project Atomic for docker image(s) > -------------------------------------- > > Key: JBTM-2298 > URL: https://issues.jboss.org/browse/JBTM-2298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > > 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) From issues at jboss.org Wed Nov 25 09:20:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 25 Nov 2015 09:20:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2568) Add config options to enable fine grained control of what's tested in a PR In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2568: ----------------------------------- Status: Pull Request Sent (was: Open) > Add config options to enable fine grained control of what's tested in a PR > -------------------------------------------------------------------------- > > Key: JBTM-2568 > URL: https://issues.jboss.org/browse/JBTM-2568 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Affects Versions: 5.2.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Currently we have a fixed set of Jenkins CI config profiles when testing PRs (QA_JTS_JDKORB, QA_JTA, XTS, MAIN, BLACKTIE and PERF) and we are allowed to selectively disable one or more of them. > It would be handy to be able to control other things such as running QA tests using the journal store (which none of the above QA profiles allow). It would also be a handy shortcut to explicitly set which profile to run (as opposed to which ones to disable). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Nov 25 09:20:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 25 Nov 2015 09:20:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2568) Add config options to enable fine grained control of what's tested in a PR In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2568: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add config options to enable fine grained control of what's tested in a PR > -------------------------------------------------------------------------- > > Key: JBTM-2568 > URL: https://issues.jboss.org/browse/JBTM-2568 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Affects Versions: 5.2.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Currently we have a fixed set of Jenkins CI config profiles when testing PRs (QA_JTS_JDKORB, QA_JTA, XTS, MAIN, BLACKTIE and PERF) and we are allowed to selectively disable one or more of them. > It would be handy to be able to control other things such as running QA tests using the journal store (which none of the above QA profiles allow). It would also be a handy shortcut to explicitly set which profile to run (as opposed to which ones to disable). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Nov 25 09:28:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 25 Nov 2015 09:28:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2568) Add config options to enable fine grained control of what's tested in a PR In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133801#comment-13133801 ] Michael Musgrove commented on JBTM-2568: ---------------------------------------- I updated narayana.sh to read any name=value pairs from the pull description and set them as environment variables in the job. In addition, a pair of the form PROFILE=xyz where xyz is one of our standard job axes (QA_JTS_JDKORB, QA_JTA, XTS, MAIN, BLACKTIE, PERF) will just run that single axis for the PR. For example the PR description: bq. PROFILE=QA_JTS_JDKORB QA_PROFILE=-Dprofile=hornetq QA_TESTGROUP=crashrecovery02_2 QA_TESTMETHODS=CrashRecovery02_2_Test31 NARAYANA_TESTS=0 will result in just the QA_JTS_JDKORB axis being run (PROFILE=QA_JTS_JDKORB) using the journal store (QA_PROFILE=-Dprofile=hornetq). The QA_TESTGROUP and QA_TESTMETHODS environment variable settings will result in just a single method being tested. > Add config options to enable fine grained control of what's tested in a PR > -------------------------------------------------------------------------- > > Key: JBTM-2568 > URL: https://issues.jboss.org/browse/JBTM-2568 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Affects Versions: 5.2.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Currently we have a fixed set of Jenkins CI config profiles when testing PRs (QA_JTS_JDKORB, QA_JTA, XTS, MAIN, BLACKTIE and PERF) and we are allowed to selectively disable one or more of them. > It would be handy to be able to control other things such as running QA tests using the journal store (which none of the above QA profiles allow). It would also be a handy shortcut to explicitly set which profile to run (as opposed to which ones to disable). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Nov 25 09:47:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 25 Nov 2015 09:47:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2567) QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2567: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/947 > QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB) > ------------------------------------------------------------ > > Key: JBTM-2567 > URL: https://issues.jboss.org/browse/JBTM-2567 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/135/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Nov 25 15:24:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 25 Nov 2015 15:24:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2568) Add config options to enable fine grained control of what's tested in a PR In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2568: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/948, https://github.com/jbosstm/narayana/pull/950 (was: https://github.com/jbosstm/narayana/pull/948) > Add config options to enable fine grained control of what's tested in a PR > -------------------------------------------------------------------------- > > Key: JBTM-2568 > URL: https://issues.jboss.org/browse/JBTM-2568 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Affects Versions: 5.2.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Currently we have a fixed set of Jenkins CI config profiles when testing PRs (QA_JTS_JDKORB, QA_JTA, XTS, MAIN, BLACKTIE and PERF) and we are allowed to selectively disable one or more of them. > It would be handy to be able to control other things such as running QA tests using the journal store (which none of the above QA profiles allow). It would also be a handy shortcut to explicitly set which profile to run (as opposed to which ones to disable). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 00:56:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 26 Nov 2015 00:56:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134021#comment-13134021 ] Amos Feng commented on JBTM-2553: --------------------------------- It looks like that the byteman script can not be installed when running with the jacoco. > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 02:49:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 26 Nov 2015 02:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134036#comment-13134036 ] Amos Feng commented on JBTM-2553: --------------------------------- I did some debug with the CrashRecovery2 Run with the following command {code} ./build.sh -f ArjunaJTA/jta/pom.xml clean test -Dtest=CrashRecovery2 -Dorg.jboss.byteman.debug -Dorg.jboss.byteman.verbose -PcodeCoverage {code} check the output of the test and it looks like the rule does not be triggered as it can not find the local binding var "$this" The fail2pc rule is {code} RULE Fail 2PC CLASS com.arjuna.ats.arjuna.coordinator.BasicAction METHOD phase2Commit AT ENTRY BIND NOTHING IF readCounter("phase2commit") == 0 DO debug("Called"), incrementCounter("phase2commit"); com.arjuna.ats.arjuna.coordinator.ActionManager.manager().remove($this.get_uid()); RETURN ENDRULE {code} The failure is {code} start:4 triggerPos:0 end:535 (I add this debug message in agent/src/main/java/org/jboss/byteman/agent/adapter/RuleCheckMethodAdapter.java) RuleCheckMethodAdapter.checkBindings : invalid local variable binding $this checking method phase2Commit(Z)V {code} if we run without the jacoco, the start and end is {code} start:0 triggerPos:0 end:327 {code} [~adinn] how do you think about this ? > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 03:58:00 2015 From: issues at jboss.org (Andrew Dinn (JIRA)) Date: Thu, 26 Nov 2015 03:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134047#comment-13134047 ] Andrew Dinn commented on JBTM-2553: ----------------------------------- Hi Amos, thanks for reporting this. I don't know why you are seeing that error. It's very odd because $this is the only local variable reference that we can identify when there is no local variable table. Could you try changing the rule to use $0 instead of $this and see if that makes it work. > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 04:14:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 26 Nov 2015 04:14:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134057#comment-13134057 ] Amos Feng commented on JBTM-2553: --------------------------------- Thanks Adinn, I met this error when running the codeCoverage with the jacoco. The $0 works. So it looks like the issue is related to the script but not the jacoco ? > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 04:18:00 2015 From: issues at jboss.org (Andrew Dinn (JIRA)) Date: Thu, 26 Nov 2015 04:18:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134060#comment-13134060 ] Andrew Dinn commented on JBTM-2553: ----------------------------------- Doh! I see Amos is way ahead of me here (nice work, Amos :-) The trace statement Amos inserted shows that the local variable checking code has found an entry in the local var table for $this but one that starts at bytecode offset 4 and ends at offset 535. The injection code is trying to inject the rule at offset 0 i.e. at entry to the code. This is after transformation by Jacoco. With no transformation the local var this is found tarting at offset 0. I have not yet looked at the Jacoco code but it seems pretty obvious what is happening. When Jacoco inserts profiling instructions into the method it updates the start and end offsets for entries in the local variable table to take account of the new code. One of those profiling instruction sequences will be injected at the start of the method and Jacoco appears to be shifting the local var start offset for this so that it comes into scope after the profiling code rather than at bytecode 0. No doubt it is also shifting the start position for method parameter entries. This is at best unhelpful; actually, I think it is an error because this and the parameters are /always/ in scope from the start of the method even if code is inserted before the start. I thought that ASM fixed this as a special case. Which version of Jacoco is being used here? The latest Jacoco version uses ASM 5 which shoudl deal with this problem. Have you tried updating to a later Jacoco? If that doesn't work I'll take this up with the Jacoco developers. > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 04:19:00 2015 From: issues at jboss.org (Andrew Dinn (JIRA)) Date: Thu, 26 Nov 2015 04:19:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134060#comment-13134060 ] Andrew Dinn edited comment on JBTM-2553 at 11/26/15 4:18 AM: ------------------------------------------------------------- Doh! I see Amos is way ahead of me here (nice work, Amos :-) The trace statement Amos inserted shows that the local variable checking code has found an entry in the local var table for $this but one that starts at bytecode offset 4 and ends at offset 535. The injection code is trying to inject the rule at offset 0 i.e. at entry to the code. This is after transformation by Jacoco. With no transformation the local var this is found starting at offset 0. I have not yet looked at the Jacoco code but it seems pretty obvious what is happening. When Jacoco inserts profiling instructions into the method it updates the start and end offsets for entries in the local variable table to take account of the new code. One of those profiling instruction sequences will be injected at the start of the method and Jacoco appears to be shifting the local var start offset for this so that it comes into scope after the profiling code rather than at bytecode 0. No doubt it is also shifting the start position for method parameter entries. This is at best unhelpful; actually, I think it is an error because this and the parameters are /always/ in scope from the start of the method even if code is inserted before the start. I thought that ASM fixed this as a special case. Which version of Jacoco is being used here? The latest Jacoco version uses ASM 5 which shoudl deal with this problem. Have you tried updating to a later Jacoco? If that doesn't work I'll take this up with the Jacoco developers. was (Author: adinn): Doh! I see Amos is way ahead of me here (nice work, Amos :-) The trace statement Amos inserted shows that the local variable checking code has found an entry in the local var table for $this but one that starts at bytecode offset 4 and ends at offset 535. The injection code is trying to inject the rule at offset 0 i.e. at entry to the code. This is after transformation by Jacoco. With no transformation the local var this is found tarting at offset 0. I have not yet looked at the Jacoco code but it seems pretty obvious what is happening. When Jacoco inserts profiling instructions into the method it updates the start and end offsets for entries in the local variable table to take account of the new code. One of those profiling instruction sequences will be injected at the start of the method and Jacoco appears to be shifting the local var start offset for this so that it comes into scope after the profiling code rather than at bytecode 0. No doubt it is also shifting the start position for method parameter entries. This is at best unhelpful; actually, I think it is an error because this and the parameters are /always/ in scope from the start of the method even if code is inserted before the start. I thought that ASM fixed this as a special case. Which version of Jacoco is being used here? The latest Jacoco version uses ASM 5 which shoudl deal with this problem. Have you tried updating to a later Jacoco? If that doesn't work I'll take this up with the Jacoco developers. > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 04:29:00 2015 From: issues at jboss.org (Andrew Dinn (JIRA)) Date: Thu, 26 Nov 2015 04:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134066#comment-13134066 ] Andrew Dinn commented on JBTM-2553: ----------------------------------- Ok, I googled this problem and found that it is one I already fixed some years ago (!) but only in our fork of Emma. Full details are included here http://sourceforge.net/p/emma/discussion/373865/thread/4530dd98/#d2b4 > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 04:30:00 2015 From: issues at jboss.org (Andrew Dinn (JIRA)) Date: Thu, 26 Nov 2015 04:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134066#comment-13134066 ] Andrew Dinn edited comment on JBTM-2553 at 11/26/15 4:29 AM: ------------------------------------------------------------- Ok, I googled this problem and found that it is one I already fixed some years ago (!) but only in our fork of Emma. Full details are included here http://sourceforge.net/p/emma/discussion/373865/thread/4530dd98/#d2b4 The Jacoco team need to be pointed at this post and told to read, learn and apply :-). was (Author: adinn): Ok, I googled this problem and found that it is one I already fixed some years ago (!) but only in our fork of Emma. Full details are included here http://sourceforge.net/p/emma/discussion/373865/thread/4530dd98/#d2b4 > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 04:30:00 2015 From: issues at jboss.org (Andrew Dinn (JIRA)) Date: Thu, 26 Nov 2015 04:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134066#comment-13134066 ] Andrew Dinn edited comment on JBTM-2553 at 11/26/15 4:29 AM: ------------------------------------------------------------- Ok, I googled this problem and found that it is one I already fixed some years ago (!) but only in our fork of Emma. Full details are included here http://sourceforge.net/p/emma/discussion/373865/thread/4530dd98/#d2b4 The Jacoco team need to be pointed at this post (and indeed at all the other fixes mentioned in the same thread) and reqested to read, learn and apply :-). was (Author: adinn): Ok, I googled this problem and found that it is one I already fixed some years ago (!) but only in our fork of Emma. Full details are included here http://sourceforge.net/p/emma/discussion/373865/thread/4530dd98/#d2b4 The Jacoco team need to be pointed at this post and told to read, learn and apply :-). > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 04:56:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 04:56:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134134#comment-13134134 ] Michael Musgrove commented on JBTM-2564: ---------------------------------------- Our tests just run on a single host so even if AMS2 does not have IPv6 networking enabled we can still run jobs in IPv6 mode. What we cannot test is running with IPv4 disabled. So we do have a dual stack job running narayana-quickstarts-ipv6 on AMS2 so this JIRA can now be marked as resolved - if I don't hear any complaints then I will resolve it later on today. I will also move the narayana IPv6 job from the NCL cluster. > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 04:58:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 04:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2567) QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2567: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > QA suite failure: CrashRecovery02_2_Test??? (hqstore/JDKORB) > ------------------------------------------------------------ > > Key: JBTM-2567 > URL: https://issues.jboss.org/browse/JBTM-2567 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/135/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 05:00:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 26 Nov 2015 05:00:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134137#comment-13134137 ] Tom Jenkinson commented on JBTM-2564: ------------------------------------- Did you need any fixes to Narayana to make it work on IPv6 because I think [~hhovsepy] is reporting they don't work for him? I think the reason they would work on IPv6+IPv4 is arq will be fine to run with its IPv4 args. I therefore don't think we can mark it as resolved because the QS are running on IPv6 with IPv4 too so that is difference to the summary+description of this issue. > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 05:17:00 2015 From: issues at jboss.org (Hayk Hovsepyan (JIRA)) Date: Thu, 26 Nov 2015 05:17:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134152#comment-13134152 ] Hayk Hovsepyan commented on JBTM-2564: -------------------------------------- As I understood, this task was created to add new maven profile into several quickstarts to pass IPv6 parameters (mentioned in earlier comments), right? Is it already done? > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 05:40:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 05:40:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134171#comment-13134171 ] Michael Musgrove commented on JBTM-2564: ---------------------------------------- We can re-purpose this JIRA to do that. I will update the JIRA description to include both tasks. > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 05:42:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 05:42:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2564: ----------------------------------- Issue Type: Bug (was: Task) > Run quickstarts on IPv6 > ----------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 05:42:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 05:42:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Quickstart failures with IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2564: ----------------------------------- Summary: Quickstart failures with IPv6 (was: Run quickstarts on IPv6) > Quickstart failures with IPv6 > ----------------------------- > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 05:44:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 05:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Quickstart tests failed on pure-ipv6 linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2564: ----------------------------------- Summary: Quickstart tests failed on pure-ipv6 linux (was: Quickstart failures with IPv6) > Quickstart tests failed on pure-ipv6 linux > ------------------------------------------ > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 08:36:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 08:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2566) ObjectStoreIterator can silently fail if there is an ObjectStoreException in the CTOR In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reassigned JBTM-2566: -------------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > ObjectStoreIterator can silently fail if there is an ObjectStoreException in the CTOR > ------------------------------------------------------------------------------------- > > Key: JBTM-2566 > URL: https://issues.jboss.org/browse/JBTM-2566 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling, Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Detected during https://issues.jboss.org/browse/JBTM-2565 and worked around in CMR but it should be reviewed for the tooling use cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 08:36:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 08:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2566) ObjectStoreIterator can silently fail if there is an ObjectStoreException in the CTOR In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2566: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ObjectStoreIterator can silently fail if there is an ObjectStoreException in the CTOR > ------------------------------------------------------------------------------------- > > Key: JBTM-2566 > URL: https://issues.jboss.org/browse/JBTM-2566 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling, Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Detected during https://issues.jboss.org/browse/JBTM-2565 and worked around in CMR but it should be reviewed for the tooling use cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 08:40:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 08:40:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Quickstart tests failed on pure-ipv6 linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2564: ----------------------------------- Fix Version/s: 5.later (was: 5.next) > Quickstart tests failed on pure-ipv6 linux > ------------------------------------------ > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 08:43:15 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 08:43:15 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2305) Incomplete tooling documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2305: ----------------------------------- Fix Version/s: 5.next (was: 5.later) > Incomplete tooling documentation > -------------------------------- > > Key: JBTM-2305 > URL: https://issues.jboss.org/browse/JBTM-2305 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Documentation > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > For tooling the docs defer to the wildfly/EAP cli for "5.1.1. Browse and Manage Transactions Using an Application Server". We had some text in the README explaining how to view the tooling MBeans but the equivalent needs to be added to the development_guide too for use with standalone narayana. > In addition the docs need to explain how to extend the tooling for new abstract records (basically the user needs to create a JMX MBean for the new type and register it with the ObjStoreBrowser). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 08:43:17 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 08:43:17 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2517) Update the Narayana Release Process doc to include performance figures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2517: ----------------------------------- Fix Version/s: 5.next (was: 5.later) > Update the Narayana Release Process doc to include performance figures > ---------------------------------------------------------------------- > > Key: JBTM-2517 > URL: https://issues.jboss.org/browse/JBTM-2517 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Include a description in the NRP document of how to blog about performance figures when releasing a new version of Narayana -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 08:44:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 08:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2518) Product comparison benchmark CI job fails with OutOfMemoryError In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2518: ----------------------------------- Fix Version/s: 5.next (was: 5.later) > Product comparison benchmark CI job fails with OutOfMemoryError > --------------------------------------------------------------- > > Key: JBTM-2518 > URL: https://issues.jboss.org/browse/JBTM-2518 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmarks/39 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 08:44:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 08:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2542) Migrate performance tests to the performance repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2542: ----------------------------------- Priority: Minor (was: Major) > 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) From issues at jboss.org Thu Nov 26 08:49:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 26 Nov 2015 08:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2518) Product comparison benchmark CI job fails with OutOfMemoryError In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-2518. ---------------------------------- Resolution: Out of Date > Product comparison benchmark CI job fails with OutOfMemoryError > --------------------------------------------------------------- > > Key: JBTM-2518 > URL: https://issues.jboss.org/browse/JBTM-2518 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmarks/39 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 10:23:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 26 Nov 2015 10:23:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2569) If the JDBC store is unavailable it is possible for XAResources to be identified as orphans and rolled back In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2569: ----------------------------------- Summary: If the JDBC store is unavailable it is possible for XAResources to be identified as orphans and rolled back Key: JBTM-2569 URL: https://issues.jboss.org/browse/JBTM-2569 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Blocker Fix For: 5.next During investigation of https://issues.jboss.org/browse/JBEAP-1750 it was discovered that there exists an issue in XARecoveryModule where if the object store transaction log check throws an exception during orphan detection then the record is treated as if it does not have a log. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 10:29:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 26 Nov 2015 10:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2569) If the JDBC store is unavailable it is possible for XAResources to be identified as orphans and rolled back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2569: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/951 > If the JDBC store is unavailable it is possible for XAResources to be identified as orphans and rolled back > ----------------------------------------------------------------------------------------------------------- > > Key: JBTM-2569 > URL: https://issues.jboss.org/browse/JBTM-2569 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > During investigation of https://issues.jboss.org/browse/JBEAP-1750 it was discovered that there exists an issue in XARecoveryModule where if the object store transaction log check throws an exception during orphan detection then the record is treated as if it does not have a log. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 10:42:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 26 Nov 2015 10:42:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Quickstart tests failed on pure-ipv6 linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2564: ----------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > Quickstart tests failed on pure-ipv6 linux > ------------------------------------------ > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.later > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 10:43:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 26 Nov 2015 10:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Quickstart tests failed on pure-ipv6 linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2564: -------------------------------- Fix Version/s: (was: 5.later) > Quickstart tests failed on pure-ipv6 linux > ------------------------------------------ > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 10:43:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 26 Nov 2015 10:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Quickstart tests failed on pure-ipv6 linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2564: -------------------------------- Fix Version/s: 5.next > Quickstart tests failed on pure-ipv6 linux > ------------------------------------------ > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 11:02:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 26 Nov 2015 11:02:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2564) Quickstart tests failed on pure-ipv6 linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2564: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/156 > Quickstart tests failed on pure-ipv6 linux > ------------------------------------------ > > Key: JBTM-2564 > URL: https://issues.jboss.org/browse/JBTM-2564 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Environment: Pure IPv6 configured RHEL6 > Reporter: Hayk Hovsepyan > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine. > The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue. > On dual-stack-IPv6 machines they pass. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 11:11:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 26 Nov 2015 11:11:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134418#comment-13134418 ] Amos Feng commented on JBTM-2553: --------------------------------- Thanks adinn to look into it. I think we use the Jacoco 0.7.4.201502262128. I'm trying update to the 0.7.5.201505241946 but it still fails. > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Nov 26 11:27:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 26 Nov 2015 11:27:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2569) If the JDBC store is unavailable it is possible for XAResources to be identified as orphans and rolled back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2569: -------------------------------- Component/s: Transaction Core > If the JDBC store is unavailable it is possible for XAResources to be identified as orphans and rolled back > ----------------------------------------------------------------------------------------------------------- > > Key: JBTM-2569 > URL: https://issues.jboss.org/browse/JBTM-2569 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > During investigation of https://issues.jboss.org/browse/JBEAP-1750 it was discovered that there exists an issue in XARecoveryModule where if the object store transaction log check throws an exception during orphan detection then the record is treated as if it does not have a log. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 06:28:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Nov 2015 06:28:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2561) XTS code coverage failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2561: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/952 > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 06:29:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Nov 2015 06:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2561) XTS code coverage failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134648#comment-13134648 ] Gytis Trikleris commented on JBTM-2561: --------------------------------------- [~tomjenkinson], sorry didn't see your comment few days back. But I already had a job for this: http://albany.eng.hst.ams2.redhat.com/job/gytis-codeCoverage/ > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 06:39:00 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 27 Nov 2015 06:39:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2121) Add a jdbc object store implementation for later revisions of MySQL driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134654#comment-13134654 ] RH Bugzilla Integration commented on JBTM-2121: ----------------------------------------------- Enrique Gonzalez Martinez changed the Status of [bug 1097166|https://bugzilla.redhat.com/show_bug.cgi?id=1097166] from NEW to CLOSED > Add a jdbc object store implementation for later revisions of MySQL driver > -------------------------------------------------------------------------- > > Key: JBTM-2121 > URL: https://issues.jboss.org/browse/JBTM-2121 > Project: JBoss Transaction Manager > Issue Type: Task > Affects Versions: 4.17.17, 5.0.1 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.20, 5.0.2 > > > commit 44553931 updated the MySQl driver to 5.1.28. > In this revision of the driver, it is reporting as mysql, not mysql_ab. It should be possible to duplicate our mysql_ab_driver to mysql_driver in order to catch both cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 08:52:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Nov 2015 08:52:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2570) Remove unused private methods and fields in XTS In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2570: ------------------------------------- Summary: Remove unused private methods and fields in XTS Key: JBTM-2570 URL: https://issues.jboss.org/browse/JBTM-2570 Project: JBoss Transaction Manager Issue Type: Sub-task Components: XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 09:00:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Nov 2015 09:00:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2115) Not all classes are under code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2115: ---------------------------------- Description: The following poms contain skipped classes for code coverage: ArjunaCore/arjuna/pom.xml ArjunaJTA/jdbc/pom.xml ArjunaJTA/jta/pom.xml ArjunaJTA/spi/pom.xml XTS/localjunit/pom.xml We should aim to test everything was: The following poms contain skipped classes for code coverage: ArjunaCore/arjuna/pom.xml ArjunaJTA/jdbc/pom.xml ArjunaJTA/jta/pom.xml ArjunaJTA/spi/pom.xml XTS/localjunit/pom.xml compensations/pom.xml txframework/pom.xml We should aim to test everything > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 09:04:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Nov 2015 09:04:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2571) Enable code coverage for XTS crash recovery tests In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2571: ------------------------------------- Summary: Enable code coverage for XTS crash recovery tests Key: JBTM-2571 URL: https://issues.jboss.org/browse/JBTM-2571 Project: JBoss Transaction Manager Issue Type: Sub-task Components: XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Code coverage data is not collected during the XTS crash recovery tests execution. Currently this seems to be blocked by [1], [2], and [3]. [1] https://community.jboss.org/message/817252 [2] https://issues.jboss.org/browse/ARQ-1014 [3] https://issues.jboss.org/browse/ARQ-918 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 09:04:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Nov 2015 09:04:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2571) Enable code coverage for XTS crash recovery tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2571: ---------------------------------- Fix Version/s: (was: 5.next) > Enable code coverage for XTS crash recovery tests > ------------------------------------------------- > > Key: JBTM-2571 > URL: https://issues.jboss.org/browse/JBTM-2571 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > > Code coverage data is not collected during the XTS crash recovery tests execution. Currently this seems to be blocked by [1], [2], and [3]. > [1] https://community.jboss.org/message/817252 > [2] https://issues.jboss.org/browse/ARQ-1014 > [3] https://issues.jboss.org/browse/ARQ-918 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 09:08:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Nov 2015 09:08:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134764#comment-13134764 ] Gytis Trikleris commented on JBTM-741: -------------------------------------- [~tomjenkinson], what would you think about postponing this issue until JBTM-2571 is resolved? I think it'd be too dangerous to remove public classes or methods without having code coverage from all available tests. What do you think? > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Fix For: 5.next > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 09:12:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 27 Nov 2015 09:12:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134767#comment-13134767 ] Tom Jenkinson commented on JBTM-741: ------------------------------------ We don't want to remove any public classes or methods - those just need tests adding. But I do agree that sequencing this after JBTM-2571 makes a lot of sense. > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Fix For: 5.next > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 09:13:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 27 Nov 2015 09:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134769#comment-13134769 ] Tom Jenkinson commented on JBTM-741: ------------------------------------ Also, this and https://issues.jboss.org/browse/JBTM-2571 could be made subtasks of https://issues.jboss.org/browse/JBTM-2115 > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Fix For: 5.next > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 09:27:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Nov 2015 09:27:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2570) Remove unused private methods and fields in XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2570: ---------------------------------- Parent: (was: JBTM-741) Issue Type: Task (was: Sub-task) > Remove unused private methods and fields in XTS > ----------------------------------------------- > > Key: JBTM-2570 > URL: https://issues.jboss.org/browse/JBTM-2570 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 09:27:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Nov 2015 09:27:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-741: --------------------------------- Parent: JBTM-2115 Issue Type: Sub-task (was: Task) > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Fix For: 5.next > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Nov 27 10:14:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Nov 2015 10:14:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2570) Remove unused private methods and fields in XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2570: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/953 > Remove unused private methods and fields in XTS > ----------------------------------------------- > > Key: JBTM-2570 > URL: https://issues.jboss.org/browse/JBTM-2570 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Nov 30 11:18:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 30 Nov 2015 11:18:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-741: --------------------------------- Fix Version/s: (was: 5.next) > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)