From issues at jboss.org Thu Oct 1 06:31:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 1 Oct 2015 06:31:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2529) Create WildFly update issue as part of the JIRA update In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2529: ------------------------------------- Summary: Create WildFly update issue as part of the JIRA update Key: JBTM-2529 URL: https://issues.jboss.org/browse/JBTM-2529 Project: JBoss Transaction Manager Issue Type: Sub-task Components: Release Process 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 Oct 1 09:30:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 1 Oct 2015 09:30:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2530: -------------------------------------- Summary: jacoco failures Key: JBTM-2530 URL: https://issues.jboss.org/browse/JBTM-2530 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.2.1 http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:12:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 1 Oct 2015 11:12:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2505) Java heap space issue on Brandon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114244#comment-13114244 ] Tom Jenkinson commented on JBTM-2505: ------------------------------------- I have temporarily prevented building of BlackTie on various older operating systems. I have reduced it down to 32el5 and 64el7. I would have used 32el6 instead of 32el5 but we don't have such a slave > Java heap space issue on Brandon > -------------------------------- > > Key: JBTM-2505 > URL: https://issues.jboss.org/browse/JBTM-2505 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.2.5.Final > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Attachments: consoleText.txt > > > narayana-AS800 build fails whenever it runs on Brandon due to not enough java heap space. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:14:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 1 Oct 2015 11:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2505) Java heap space issue on Brandon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114244#comment-13114244 ] Tom Jenkinson edited comment on JBTM-2505 at 10/1/15 11:13 AM: --------------------------------------------------------------- I have temporarily prevented building of BlackTie on various older operating systems. I have reduced it down to 32el5 and 64el7. I would have used 32el6 instead of 32el5 but we don't have such a slave Jobs updated: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/ http://albany.eng.hst.ams2.redhat.com/view/Narayana-pulls/job/btny-pulls-narayana-jdk8/ was (Author: tomjenkinson): I have temporarily prevented building of BlackTie on various older operating systems. I have reduced it down to 32el5 and 64el7. I would have used 32el6 instead of 32el5 but we don't have such a slave > Java heap space issue on Brandon > -------------------------------- > > Key: JBTM-2505 > URL: https://issues.jboss.org/browse/JBTM-2505 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.2.5.Final > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Attachments: consoleText.txt > > > narayana-AS800 build fails whenever it runs on Brandon due to not enough java heap space. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 1 11:47:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 1 Oct 2015 11:47:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114260#comment-13114260 ] Michael Musgrove commented on JBTM-2530: ---------------------------------------- The issue is discussed here: https://github.com/jacoco/jacoco/issues/74 > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.1 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 04:58:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 04:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114444#comment-13114444 ] Tom Jenkinson commented on JBTM-2530: ------------------------------------- Whatever was merged has caused the none-jacoco build to fail consistently now for all QA builds: http://albany.eng.hst.ams2.redhat.com/job/narayana/948/ http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.1 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 05:01:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 05:01:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2531: ----------------------------------- Summary: XTS build regularly fails Key: JBTM-2531 URL: https://issues.jboss.org/browse/JBTM-2531 Project: JBoss Transaction Manager Issue Type: Bug Components: XTS Reporter: Tom Jenkinson Assignee: Gytis Trikleris Priority: Critical Fix For: 5.next http://albany.eng.hst.ams2.redhat.com/job/narayana/946/PROFILE=XTS,jdk=jdk8.latest,label=linux/console http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 05:02:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 05:02:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2531: -------------------------------- Description: http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ was: http://albany.eng.hst.ams2.redhat.com/job/narayana/946/PROFILE=XTS,jdk=jdk8.latest,label=linux/console http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 05:03:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 05:03:00 -0400 (EDT) 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 ] Tom Jenkinson updated JBTM-2511: -------------------------------- Priority: Critical (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: Critical > 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 Fri Oct 2 05:03:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 05:03:00 -0400 (EDT) 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=13114448#comment-13114448 ] Tom Jenkinson commented on JBTM-2511: ------------------------------------- Escallated to critical because job has had to be disabled > 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: Critical > 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 Fri Oct 2 05:04:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 05:04:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2530: -------------------------------- Priority: Critical (was: Major) > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.2.1 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 05:04:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 05:04:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114450#comment-13114450 ] Tom Jenkinson commented on JBTM-2530: ------------------------------------- Escallated to critical until main build is working again > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.2.1 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 05:22:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 2 Oct 2015 05:22:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114462#comment-13114462 ] Michael Musgrove commented on JBTM-2530: ---------------------------------------- I did push a fix (8bd7ae6) to upgrade the jacoco ant jar to org.jacoco.ant-0.7.5.201505241946.jar but this jar seems to be no longer self contained (it needs org/jacoco/report/IReportGroupVisitor) > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.2.1 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 05:29:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 05:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2530: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 05:29:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 05:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2530: -------------------------------- Component/s: Build System > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 05:29:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 05:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2512) Include BlackTie javadoc on Narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2512: -------------------------------- Priority: Minor (was: Major) > Include BlackTie javadoc on Narayana.io > --------------------------------------- > > Key: JBTM-2512 > URL: https://issues.jboss.org/browse/JBTM-2512 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 05:43:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 2 Oct 2015 05:43:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114462#comment-13114462 ] Michael Musgrove edited comment on JBTM-2530 at 10/2/15 5:42 AM: ----------------------------------------------------------------- I did push a fix (8bd7ae6) to upgrade the jacoco ant jar to org.jacoco.ant-0.7.5.201505241946.jar but push the wrong jar. Commit 75859d0 includes the correct one. was (Author: mmusgrov): I did push a fix (8bd7ae6) to upgrade the jacoco ant jar to org.jacoco.ant-0.7.5.201505241946.jar but this jar seems to be no longer self contained (it needs org/jacoco/report/IReportGroupVisitor) > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 05:45:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 2 Oct 2015 05:45:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114473#comment-13114473 ] Gytis Trikleris commented on JBTM-2531: --------------------------------------- Was it hanging or does it just look like the test was killed? {code} Running com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:742) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy51.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:956) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1706) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Caused by: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:805) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:954) at hudson.remoting.Channel$2.handle(Channel.java:474) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: hudson.remoting.Channel$OrderlyShutdown ... 3 more Caused by: Command close created at at hudson.remoting.Command.(Command.java:56) at hudson.remoting.Channel$CloseCommand.(Channel.java:948) at hudson.remoting.Channel$CloseCommand.(Channel.java:946) at hudson.remoting.Channel.close(Channel.java:1029) at hudson.remoting.Channel.close(Channel.java:1012) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:953) ... 2 more {code} > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 06:20:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 06:20:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114492#comment-13114492 ] Tom Jenkinson commented on JBTM-2530: ------------------------------------- Great - thanks for checking into it. > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 06:24:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 06:24:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114494#comment-13114494 ] Tom Jenkinson commented on JBTM-2531: ------------------------------------- It wasn't hanging that I know of - maybe the job has a timeout? > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 06:27:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 2 Oct 2015 06:27:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114497#comment-13114497 ] Gytis Trikleris commented on JBTM-2531: --------------------------------------- Not sure, but I'll investigate. > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 09:43:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 2 Oct 2015 09:43:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114602#comment-13114602 ] Gytis Trikleris commented on JBTM-2531: --------------------------------------- Mike did the following: "Manage Jenkins > Manage Nodes > Configure, and uncheck the "Response time" box". Lets see what happens through the weekend. That's Mike's comment on this based on stack exchange: "This monitors the round trip network response time from the master to the slave, and if it goes above a threshold repeatedly, it marks the slave offline." > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:46:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 11:46:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2409) XARecoveryModuleHelpersUnitTest hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114710#comment-13114710 ] Tom Jenkinson commented on JBTM-2409: ------------------------------------- I think what has happened here is that the notifyAll: https://github.com/jbosstm/narayana/blob/5.2.5.Final/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L994 released the locks: https://github.com/jbosstm/narayana/blob/5.2.5.Final/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L976 but not before: https://github.com/jbosstm/narayana/blob/5.2.5.Final/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L201 acquires the lock to set scan state to second pass which prevents these waiting threads from waking up. I think it can do this as there is only a 100 mill wait and its possible that the main thread fires before the two waiting threads wake from the notify to reacquire the lock: https://github.com/jbosstm/narayana/blob/5.2.5.Final/ArjunaJTA/jta/tests/classes/com/hp/mwtests/ts/jta/recovery/XARecoveryModuleHelpersUnitTest.java#L128 As in normal circumstances the delay between scans is much longer, plus this test has only failed once I will close it. If it reoccurs we could increase the delay in the test. > XARecoveryModuleHelpersUnitTest hang > ------------------------------------ > > Key: JBTM-2409 > URL: https://issues.jboss.org/browse/JBTM-2409 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Attachments: 32287.jstack > > > The test checks that recovery helpers can be removed at the correct stages during recovery scans. The CI job http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/196 shows the hang. > The junit test thread: > - starts 2 threads that will remove a recovery helper > - triggers xaRecoveryModule.periodicWorkFirstPass() > - triggers xaRecoveryModule.periodicWorkSecondPass() > - joins with remover threads > The jstack output shows: > - the two threads in the process of removing a recovery helper and are waiting for the first pass to finish; > - the junit test thread is waiting to join with these two threads; > Since both recovery passes must have completed it looks like the remover threads weren't notified when the first pass completed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 11:46:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 11:46:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2409) XARecoveryModuleHelpersUnitTest hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2409. ------------------------------- Fix Version/s: (was: 5.next) Resolution: Cannot Reproduce Bug > XARecoveryModuleHelpersUnitTest hang > ------------------------------------ > > Key: JBTM-2409 > URL: https://issues.jboss.org/browse/JBTM-2409 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Attachments: 32287.jstack > > > The test checks that recovery helpers can be removed at the correct stages during recovery scans. The CI job http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/196 shows the hang. > The junit test thread: > - starts 2 threads that will remove a recovery helper > - triggers xaRecoveryModule.periodicWorkFirstPass() > - triggers xaRecoveryModule.periodicWorkSecondPass() > - joins with remover threads > The jstack output shows: > - the two threads in the process of removing a recovery helper and are waiting for the first pass to finish; > - the junit test thread is waiting to join with these two threads; > Since both recovery passes must have completed it looks like the remover threads weren't notified when the first pass completed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 12:19:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 12:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2120) Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2120: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/922 > Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-2120 > URL: https://issues.jboss.org/browse/JBTM-2120 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Pull https://github.com/jbosstm/narayana/pull/598 added deferred throwables in case the XAR::end fails during commit. It doesn't handle the case of the HEURISTIC_ROLLBACK of a first resource where Narayana rolls back the remaining participants and then clears the failed/heuristic lists (and marks the txn as rolled back). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 2 12:20:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 Oct 2015 12:20:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2476) When a transaction times out, print the stack traces of the threads involved In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2476: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/921 > When a transaction times out, print the stack traces of the threads involved > ---------------------------------------------------------------------------- > > Key: JBTM-2476 > URL: https://issues.jboss.org/browse/JBTM-2476 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Would be useful to help understand what the code was doing when the transaction times out. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 02:55:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 5 Oct 2015 02:55:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2530: -------------------------------- Priority: Blocker (was: Critical) > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 08:54:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 5 Oct 2015 08:54:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2526) Create pre-release checking script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2526: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/923 > Create pre-release checking script > ---------------------------------- > > Key: JBTM-2526 > URL: https://issues.jboss.org/browse/JBTM-2526 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Build System, Release Process > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Write script to do tests, deprecation, and blockers checking before executing the release. > There are example bash scripts for deprecation and tests checking already, but they should be merged into one and be configurable. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 10:12:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 5 Oct 2015 10:12:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2510) Provide some example jbossts-properties.xml on the narayana.io site In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2510. ------------------------------- Fix Version/s: (was: 5.next) Resolution: Rejected These are in our repo: https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/narayana-jta/src/main/resources/jbossts-properties.xml https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/narayana-jts-jacorb/src/main/resources/jbossts-properties.xml https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/narayana-jts-idlj/src/main/resources/jbossts-idlj-properties.xml https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/narayana-jts-ibmorb/src/main/resources/jbossts-ibmorb-properties.xml > Provide some example jbossts-properties.xml on the narayana.io site > ------------------------------------------------------------------- > > Key: JBTM-2510 > URL: https://issues.jboss.org/browse/JBTM-2510 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > > This will mean we don't need to download the zip to use them (for say maven users). > We should provide: > local JTA > jacorb JTS > JDKORB JTS > IBMORB JTS -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 10:26:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 5 Oct 2015 10:26:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2512) Include BlackTie javadoc on Narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2512: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/924 > Include BlackTie javadoc on Narayana.io > --------------------------------------- > > Key: JBTM-2512 > URL: https://issues.jboss.org/browse/JBTM-2512 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 10:28:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 5 Oct 2015 10:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2492) Build and deploy Blacktie as part of BRP.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2492: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/924 > Build and deploy Blacktie as part of BRP.xml > -------------------------------------------- > > Key: JBTM-2492 > URL: https://issues.jboss.org/browse/JBTM-2492 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > We only update the Blacktie java artifacts so these should be able to be done from any machine: > {code} > call "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" > build.bat -f blacktie\wildfly-blacktie\pom.xml install -DskipTests > build.bat -f blacktie\pom.xml install -DskipTests > build.bat -f blacktie\pom.xml deploy -DskipTests > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 10:30:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 5 Oct 2015 10:30:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2512) Include BlackTie javadoc on Narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2512: -------------------------------- Status: Open (was: Pull Request Sent) Git Pull Request: (was: https://github.com/jbosstm/narayana/pull/924) > Include BlackTie javadoc on Narayana.io > --------------------------------------- > > Key: JBTM-2512 > URL: https://issues.jboss.org/browse/JBTM-2512 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 10:37:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 5 Oct 2015 10:37:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2512) Include BlackTie javadoc on Narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2512: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/925 > Include BlackTie javadoc on Narayana.io > --------------------------------------- > > Key: JBTM-2512 > URL: https://issues.jboss.org/browse/JBTM-2512 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 10:52:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 5 Oct 2015 10:52:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2512) Include BlackTie javadoc on Narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2512: -------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/925, https://github.com/jbosstm/narayana.io/pull/5 (was: https://github.com/jbosstm/narayana/pull/925) > Include BlackTie javadoc on Narayana.io > --------------------------------------- > > Key: JBTM-2512 > URL: https://issues.jboss.org/browse/JBTM-2512 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 10:56:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 5 Oct 2015 10:56:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2180: -------------------------------- Fix Version/s: 5.later (was: 5.next) > Determine whether or not we should use a specific collections framework > ----------------------------------------------------------------------- > > Key: JBTM-2180 > URL: https://issues.jboss.org/browse/JBTM-2180 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA, JTS, Performance Testing, REST, Transaction Core > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.later > > > We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections > There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 10:57:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 5 Oct 2015 10:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2491) JTS and JacORB NS Docker images quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2491: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JTS and JacORB NS Docker images quickstart > ------------------------------------------ > > Key: JBTM-2491 > URL: https://issues.jboss.org/browse/JBTM-2491 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Create a quickstart for JTS and JacORB Name Server Docker images. > Additionally, add Kubernetes pod configuration for that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 11:42:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 5 Oct 2015 11:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2120) Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2120: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-2120 > URL: https://issues.jboss.org/browse/JBTM-2120 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Pull https://github.com/jbosstm/narayana/pull/598 added deferred throwables in case the XAR::end fails during commit. It doesn't handle the case of the HEURISTIC_ROLLBACK of a first resource where Narayana rolls back the remaining participants and then clears the failed/heuristic lists (and marks the txn as rolled back). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 11:42:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 5 Oct 2015 11:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2492) Build and deploy Blacktie as part of BRP.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2492: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Build and deploy Blacktie as part of BRP.xml > -------------------------------------------- > > Key: JBTM-2492 > URL: https://issues.jboss.org/browse/JBTM-2492 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > We only update the Blacktie java artifacts so these should be able to be done from any machine: > {code} > call "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" > build.bat -f blacktie\wildfly-blacktie\pom.xml install -DskipTests > build.bat -f blacktie\pom.xml install -DskipTests > build.bat -f blacktie\pom.xml deploy -DskipTests > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 11:42:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 5 Oct 2015 11:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2512) Include BlackTie javadoc on Narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2512: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Include BlackTie javadoc on Narayana.io > --------------------------------------- > > Key: JBTM-2512 > URL: https://issues.jboss.org/browse/JBTM-2512 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 5 11:49:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 5 Oct 2015 11:49:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2476) When a transaction times out, print the stack traces of the threads involved In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2476: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > When a transaction times out, print the stack traces of the threads involved > ---------------------------------------------------------------------------- > > Key: JBTM-2476 > URL: https://issues.jboss.org/browse/JBTM-2476 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Would be useful to help understand what the code was doing when the transaction times out. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 04:45:00 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 6 Oct 2015 04:45:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2476) When a transaction times out, print the stack traces of the threads involved In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115291#comment-13115291 ] Mark Little commented on JBTM-2476: ----------------------------------- Debug option only I hope, since this could become quite tedious to view in the logs. > When a transaction times out, print the stack traces of the threads involved > ---------------------------------------------------------------------------- > > Key: JBTM-2476 > URL: https://issues.jboss.org/browse/JBTM-2476 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Would be useful to help understand what the code was doing when the transaction times out. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 04:55:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 6 Oct 2015 04:55:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2526) Create pre-release checking script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2526: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create pre-release checking script > ---------------------------------- > > Key: JBTM-2526 > URL: https://issues.jboss.org/browse/JBTM-2526 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Build System, Release Process > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Write script to do tests, deprecation, and blockers checking before executing the release. > There are example bash scripts for deprecation and tests checking already, but they should be merged into one and be configurable. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 05:14:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 05:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2476) When a transaction times out, print the stack traces of the threads involved In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115302#comment-13115302 ] Tom Jenkinson commented on JBTM-2476: ------------------------------------- It was added as a warn during rollback. I can certainly make it a debug option but the request came in from [~stephen.fikes] at the Narayana F2F that it would be useful in timeout situations. If we go for debug only then it will lose some of its power because the user would need to recreate the timeout which might be difficult. I could add an option on https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/common/CoordinatorEnvironmentBean.java so they user can choose to disable the enhancement (or maybe allow them to select a log level for the message)? > When a transaction times out, print the stack traces of the threads involved > ---------------------------------------------------------------------------- > > Key: JBTM-2476 > URL: https://issues.jboss.org/browse/JBTM-2476 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Would be useful to help understand what the code was doing when the transaction times out. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 06:10:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 06:10:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1854) Journal failures in CI test suite on JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115331#comment-13115331 ] Tom Jenkinson commented on JBTM-1854: ------------------------------------- Re-enabled over here: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk7.latest,label=linux/ > Journal failures in CI test suite on JDKORB > ------------------------------------------- > > Key: JBTM-1854 > URL: https://issues.jboss.org/browse/JBTM-1854 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz > > > The first CI job link includes: > CurrentTests01_Test036 > jtsremote JTSRemote_ImplicitPropagationTest > crashrecovery02_2 CrashRecovery02_2 - all of them > crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10 > crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them) > The second CI job link includes: > JTSRemote_ImplicitPropagationTest failure > CrashRecovery02_2_Test46 hang -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:09:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 09:09:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2530: -------------------------------- Priority: Critical (was: Blocker) > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:13:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 09:13:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2531: -------------------------------- Fix Version/s: (was: 5.next) > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:14:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 09:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2531. --------------------------------- Assignee: Michael Musgrove (was: Gytis Trikleris) Resolution: Done Looks like the change worked as we had two sequential passes > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Critical > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:14:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 09:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails due to jenkins config issue In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2531: -------------------------------- Summary: XTS build regularly fails due to jenkins config issue (was: XTS build regularly fails) > XTS build regularly fails due to jenkins config issue > ----------------------------------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Critical > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:14:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 09:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails due to jenkins config issue In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2531. ------------------------------- > XTS build regularly fails due to jenkins config issue > ----------------------------------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Critical > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:23:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 09:23:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails due to jenkins config issue In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2531: --------------------------------- > XTS build regularly fails due to jenkins config issue > ----------------------------------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Critical > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:23:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 09:23:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails due to jenkins config issue In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2531: -------------------------------- Fix Version/s: 5.next > XTS build regularly fails due to jenkins config issue > ----------------------------------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:23:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 09:23:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails due to jenkins config issue In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2531: ----------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > XTS build regularly fails due to jenkins config issue > ----------------------------------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:32:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 09:32:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2110) Investigate support for IBM ORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2110: -------------------------------- Fix Version/s: 5.later (was: 5.next) > Investigate support for IBM ORB > ------------------------------- > > Key: JBTM-2110 > URL: https://issues.jboss.org/browse/JBTM-2110 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:37:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 09:37:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2531: -------------------------------- Summary: XTS build regularly fails (was: XTS build regularly fails due to jenkins config issue) > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:56:14 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 09:56:14 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2531: -------------------------------- Comment: was deleted (was: Looks like the change worked as we had two sequential passes) > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 09:56:32 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 Oct 2015 09:56:32 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115475#comment-13115475 ] Tom Jenkinson commented on JBTM-2531: ------------------------------------- This seems related: https://issues.jenkins-ci.org/browse/JENKINS-24761 > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 6 10:36:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 6 Oct 2015 10:36:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2532) Enable code coverage for XTS In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2532: ------------------------------------- Summary: 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: 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 Tue Oct 6 10:37:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 6 Oct 2015 10:37:00 -0400 (EDT) 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: ---------------------------------- Component/s: Testing > 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 Wed Oct 7 05:44:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 7 Oct 2015 05:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115826#comment-13115826 ] Gytis Trikleris commented on JBTM-2531: --------------------------------------- This time it passed XTS tests, but failed on TXBridge: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/952/PROFILE=XTS,jdk=jdk8.latest,label=linux/console > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:01:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 7 Oct 2015 10:01:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115995#comment-13115995 ] Gytis Trikleris commented on JBTM-2531: --------------------------------------- The separate job I've create keeps failing, but in a bit different manner. However, it seem to run out of memory at some which might be the common issue. {code} [0m04:16:05,938 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") Oct 07, 2015 4:16:06 AM org.jboss.remoting3.remote.RemoteConnection handleException ERROR: JBREM000200: Remote connection failed: java.io.IOException: Fatal connection error Oct 07, 2015 4:16:06 AM org.xnio.ChannelListeners invokeChannelListener ERROR: XNIO001007: A channel event listener threw an exception java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:713) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1357) at org.xnio.XnioWorker.execute(XnioWorker.java:741) at org.jboss.remoting3.remote.RemoteReadListener$1.handleEvent(RemoteReadListener.java:54) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.channels.TranslatingSuspendableChannel.close(TranslatingSuspendableChannel.java:906) at org.xnio.IoUtils.safeClose(IoUtils.java:134) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:114) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:102) at org.jboss.remoting3.remote.RemoteConnectionChannel.handleMessageData(RemoteConnectionChannel.java:468) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:288) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:199) at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:113) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88) at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) 04:16:06,076 ERROR [org.xnio.listener] (XNIO-1 I/O-2) XNIO001007: A channel event listener threw an exception: java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:713) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1357) at org.xnio.XnioWorker.execute(XnioWorker.java:741) at org.jboss.remoting3.EndpointImpl$TrackingExecutor.execute(EndpointImpl.java:702) at org.jboss.remoting3.remote.RemoteReadListener$1.handleEvent(RemoteReadListener.java:55) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.channels.TranslatingSuspendableChannel.close(TranslatingSuspendableChannel.java:906) at org.xnio.IoUtils.safeClose(IoUtils.java:134) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:113) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:101) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:454) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:46) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:199) at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:113) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88) at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) {code} {code} Running com.arjuna.qa.junit.TestATCrashDuringCommit Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 390.664 sec Running com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 81.069 sec Running com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 384.289 sec Running com.arjuna.qa.junit.TestATParticipantCrashAndRecover Tests run: 3, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 0.031 sec Running com.arjuna.qa.junit.TestATSubordinateCrashDuringCommit Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 161.61 sec Running com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 83.059 sec Running com.arjuna.qa.junit.TestBACrashDuringCommit Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,478.401 sec Running com.arjuna.qa.junit.TestBACrashDuringOnePhaseCommit Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 166.913 sec Running com.arjuna.qa.junit.TestBASubordinateCrashDuringCommit Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 188.478 sec <<< FAILURE! subordinateMultiParticipantParticipantCompletionParticipantCloseTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringCommit) Time elapsed: 26.527 sec <<< ERROR! java.io.IOException: Cannot run program "/bin/sh": error=11, Resource temporarily unavailable at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:187) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1023) at com.arjuna.qa.extension.JBossAS7ServerKillProcessor.runShellCommandExitCode(JBossAS7ServerKillProcessor.java:49) at com.arjuna.qa.extension.JBossAS7ServerKillProcessor.jbossIsAlive(JBossAS7ServerKillProcessor.java:21) at com.arjuna.qa.extension.BaseServerKillProcessor.kill(BaseServerKillProcessor.java:46) at org.jboss.arquillian.container.impl.ContainerImpl.kill(ContainerImpl.java:235) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$10.perform(ContainerLifecycleController.java:193) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$10.perform(ContainerLifecycleController.java:187) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.killContainer(ContainerLifecycleController.java:186) at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.kill(ClientContainerController.java:230) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:209) at com.arjuna.qa.junit.TestBASubordinateCrashDuringCommit.subordinateMultiParticipantParticipantCompletionParticipantCloseTest(TestBASubordinateCrashDuringCommit.java:24) Running com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.087 sec <<< FAILURE! subordinateMultiParticipantParticipantCompletionParticipantCloseAndExitTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit) Time elapsed: 0.031 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:150) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:199) at com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit.subordinateMultiParticipantParticipantCompletionParticipantCloseAndExitTest(TestBASubordinateCrashDuringCommitAfterSubordinateExit.java:25) subordinateMultiParticipantCoordinatorCompletionParticipantCloseAndExitTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit) Time elapsed: 0.044 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:150) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:199) at com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit.subordinateMultiParticipantCoordinatorCompletionParticipantCloseAndExitTest(TestBASubordinateCrashDuringCommitAfterSubordinateExit.java:18) Running com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.108 sec <<< FAILURE! subordinateMultiParticipantCoordinatorCompletionParticipantCloseTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete) Time elapsed: 0.03 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:150) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:199) at com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete.subordinateMultiParticipantCoordinatorCompletionParticipantCloseTest(TestBASubordinateCrashDuringComplete.java:17) subordinateMultiParticipantParticipantCompletionParticipantCloseTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete) Time elapsed: 0.053 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:150) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:199) at com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete.subordinateMultiParticipantParticipantCompletionParticipantCloseTest(TestBASubordinateCrashDuringComplete.java:24) {code} > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:01:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 7 Oct 2015 10:01:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115995#comment-13115995 ] Gytis Trikleris edited comment on JBTM-2531 at 10/7/15 10:00 AM: ----------------------------------------------------------------- The separate job I've create keeps failing, but in a bit different manner. However, it seem to run out of memory at some which might be the common issue. http://albany.eng.hst.ams2.redhat.com/job/gytis-JBTM-2531/3/ {code} [0m04:16:05,938 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") Oct 07, 2015 4:16:06 AM org.jboss.remoting3.remote.RemoteConnection handleException ERROR: JBREM000200: Remote connection failed: java.io.IOException: Fatal connection error Oct 07, 2015 4:16:06 AM org.xnio.ChannelListeners invokeChannelListener ERROR: XNIO001007: A channel event listener threw an exception java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:713) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1357) at org.xnio.XnioWorker.execute(XnioWorker.java:741) at org.jboss.remoting3.remote.RemoteReadListener$1.handleEvent(RemoteReadListener.java:54) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.channels.TranslatingSuspendableChannel.close(TranslatingSuspendableChannel.java:906) at org.xnio.IoUtils.safeClose(IoUtils.java:134) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:114) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:102) at org.jboss.remoting3.remote.RemoteConnectionChannel.handleMessageData(RemoteConnectionChannel.java:468) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:288) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:199) at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:113) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88) at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) 04:16:06,076 ERROR [org.xnio.listener] (XNIO-1 I/O-2) XNIO001007: A channel event listener threw an exception: java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:713) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1357) at org.xnio.XnioWorker.execute(XnioWorker.java:741) at org.jboss.remoting3.EndpointImpl$TrackingExecutor.execute(EndpointImpl.java:702) at org.jboss.remoting3.remote.RemoteReadListener$1.handleEvent(RemoteReadListener.java:55) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.channels.TranslatingSuspendableChannel.close(TranslatingSuspendableChannel.java:906) at org.xnio.IoUtils.safeClose(IoUtils.java:134) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:113) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:101) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:454) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:46) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:199) at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:113) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88) at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) {code} {code} Running com.arjuna.qa.junit.TestATCrashDuringCommit Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 390.664 sec Running com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 81.069 sec Running com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 384.289 sec Running com.arjuna.qa.junit.TestATParticipantCrashAndRecover Tests run: 3, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 0.031 sec Running com.arjuna.qa.junit.TestATSubordinateCrashDuringCommit Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 161.61 sec Running com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 83.059 sec Running com.arjuna.qa.junit.TestBACrashDuringCommit Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,478.401 sec Running com.arjuna.qa.junit.TestBACrashDuringOnePhaseCommit Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 166.913 sec Running com.arjuna.qa.junit.TestBASubordinateCrashDuringCommit Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 188.478 sec <<< FAILURE! subordinateMultiParticipantParticipantCompletionParticipantCloseTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringCommit) Time elapsed: 26.527 sec <<< ERROR! java.io.IOException: Cannot run program "/bin/sh": error=11, Resource temporarily unavailable at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:187) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1023) at com.arjuna.qa.extension.JBossAS7ServerKillProcessor.runShellCommandExitCode(JBossAS7ServerKillProcessor.java:49) at com.arjuna.qa.extension.JBossAS7ServerKillProcessor.jbossIsAlive(JBossAS7ServerKillProcessor.java:21) at com.arjuna.qa.extension.BaseServerKillProcessor.kill(BaseServerKillProcessor.java:46) at org.jboss.arquillian.container.impl.ContainerImpl.kill(ContainerImpl.java:235) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$10.perform(ContainerLifecycleController.java:193) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$10.perform(ContainerLifecycleController.java:187) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.killContainer(ContainerLifecycleController.java:186) at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.kill(ClientContainerController.java:230) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:209) at com.arjuna.qa.junit.TestBASubordinateCrashDuringCommit.subordinateMultiParticipantParticipantCompletionParticipantCloseTest(TestBASubordinateCrashDuringCommit.java:24) Running com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.087 sec <<< FAILURE! subordinateMultiParticipantParticipantCompletionParticipantCloseAndExitTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit) Time elapsed: 0.031 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:150) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:199) at com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit.subordinateMultiParticipantParticipantCompletionParticipantCloseAndExitTest(TestBASubordinateCrashDuringCommitAfterSubordinateExit.java:25) subordinateMultiParticipantCoordinatorCompletionParticipantCloseAndExitTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit) Time elapsed: 0.044 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:150) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:199) at com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit.subordinateMultiParticipantCoordinatorCompletionParticipantCloseAndExitTest(TestBASubordinateCrashDuringCommitAfterSubordinateExit.java:18) Running com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.108 sec <<< FAILURE! subordinateMultiParticipantCoordinatorCompletionParticipantCloseTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete) Time elapsed: 0.03 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:150) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:199) at com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete.subordinateMultiParticipantCoordinatorCompletionParticipantCloseTest(TestBASubordinateCrashDuringComplete.java:17) subordinateMultiParticipantParticipantCompletionParticipantCloseTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete) Time elapsed: 0.053 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:150) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:199) at com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete.subordinateMultiParticipantParticipantCompletionParticipantCloseTest(TestBASubordinateCrashDuringComplete.java:24) {code} was (Author: gytis): The separate job I've create keeps failing, but in a bit different manner. However, it seem to run out of memory at some which might be the common issue. {code} [0m04:16:05,938 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") Oct 07, 2015 4:16:06 AM org.jboss.remoting3.remote.RemoteConnection handleException ERROR: JBREM000200: Remote connection failed: java.io.IOException: Fatal connection error Oct 07, 2015 4:16:06 AM org.xnio.ChannelListeners invokeChannelListener ERROR: XNIO001007: A channel event listener threw an exception java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:713) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1357) at org.xnio.XnioWorker.execute(XnioWorker.java:741) at org.jboss.remoting3.remote.RemoteReadListener$1.handleEvent(RemoteReadListener.java:54) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.channels.TranslatingSuspendableChannel.close(TranslatingSuspendableChannel.java:906) at org.xnio.IoUtils.safeClose(IoUtils.java:134) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:114) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:102) at org.jboss.remoting3.remote.RemoteConnectionChannel.handleMessageData(RemoteConnectionChannel.java:468) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:288) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:199) at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:113) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88) at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) 04:16:06,076 ERROR [org.xnio.listener] (XNIO-1 I/O-2) XNIO001007: A channel event listener threw an exception: java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:713) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1357) at org.xnio.XnioWorker.execute(XnioWorker.java:741) at org.jboss.remoting3.EndpointImpl$TrackingExecutor.execute(EndpointImpl.java:702) at org.jboss.remoting3.remote.RemoteReadListener$1.handleEvent(RemoteReadListener.java:55) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.channels.TranslatingSuspendableChannel.close(TranslatingSuspendableChannel.java:906) at org.xnio.IoUtils.safeClose(IoUtils.java:134) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:113) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:101) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:454) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:46) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:199) at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:113) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88) at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) {code} {code} Running com.arjuna.qa.junit.TestATCrashDuringCommit Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 390.664 sec Running com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 81.069 sec Running com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 384.289 sec Running com.arjuna.qa.junit.TestATParticipantCrashAndRecover Tests run: 3, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 0.031 sec Running com.arjuna.qa.junit.TestATSubordinateCrashDuringCommit Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 161.61 sec Running com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 83.059 sec Running com.arjuna.qa.junit.TestBACrashDuringCommit Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,478.401 sec Running com.arjuna.qa.junit.TestBACrashDuringOnePhaseCommit Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 166.913 sec Running com.arjuna.qa.junit.TestBASubordinateCrashDuringCommit Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 188.478 sec <<< FAILURE! subordinateMultiParticipantParticipantCompletionParticipantCloseTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringCommit) Time elapsed: 26.527 sec <<< ERROR! java.io.IOException: Cannot run program "/bin/sh": error=11, Resource temporarily unavailable at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:187) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1023) at com.arjuna.qa.extension.JBossAS7ServerKillProcessor.runShellCommandExitCode(JBossAS7ServerKillProcessor.java:49) at com.arjuna.qa.extension.JBossAS7ServerKillProcessor.jbossIsAlive(JBossAS7ServerKillProcessor.java:21) at com.arjuna.qa.extension.BaseServerKillProcessor.kill(BaseServerKillProcessor.java:46) at org.jboss.arquillian.container.impl.ContainerImpl.kill(ContainerImpl.java:235) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$10.perform(ContainerLifecycleController.java:193) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$10.perform(ContainerLifecycleController.java:187) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.killContainer(ContainerLifecycleController.java:186) at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.kill(ClientContainerController.java:230) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:209) at com.arjuna.qa.junit.TestBASubordinateCrashDuringCommit.subordinateMultiParticipantParticipantCompletionParticipantCloseTest(TestBASubordinateCrashDuringCommit.java:24) Running com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.087 sec <<< FAILURE! subordinateMultiParticipantParticipantCompletionParticipantCloseAndExitTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit) Time elapsed: 0.031 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:150) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:199) at com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit.subordinateMultiParticipantParticipantCompletionParticipantCloseAndExitTest(TestBASubordinateCrashDuringCommitAfterSubordinateExit.java:25) subordinateMultiParticipantCoordinatorCompletionParticipantCloseAndExitTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit) Time elapsed: 0.044 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:150) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:199) at com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit.subordinateMultiParticipantCoordinatorCompletionParticipantCloseAndExitTest(TestBASubordinateCrashDuringCommitAfterSubordinateExit.java:18) Running com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.108 sec <<< FAILURE! subordinateMultiParticipantCoordinatorCompletionParticipantCloseTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete) Time elapsed: 0.03 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:150) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:199) at com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete.subordinateMultiParticipantCoordinatorCompletionParticipantCloseTest(TestBASubordinateCrashDuringComplete.java:17) subordinateMultiParticipantParticipantCompletionParticipantCloseTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete) Time elapsed: 0.053 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80) at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:150) at com.arjuna.qa.junit.BaseCrashTest.runTest(BaseCrashTest.java:199) at com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete.subordinateMultiParticipantParticipantCompletionParticipantCloseTest(TestBASubordinateCrashDuringComplete.java:24) {code} > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:14:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 7 Oct 2015 10:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116008#comment-13116008 ] Gytis Trikleris commented on JBTM-2531: --------------------------------------- So at lest for out of memory and hopefully for the core problem [~mmusgrov] solution of increasing ulimit should work. > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:56:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 7 Oct 2015 10:56:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1340) BeanPopulator overhead needs looking into In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-1340. --------------------------------- Resolution: Out of Date I am closing this as out of date. I can't replicate the performance issue with the current version of Narayana. I built a simple harness using JProfiler and will attach the test I am using and output - enabled() does not appear in the list of hotspots. If you can replicate, please can you attach a test class and instructions on how to observe and I will look again. > BeanPopulator overhead needs looking into > ----------------------------------------- > > Key: JBTM-1340 > URL: https://issues.jboss.org/browse/JBTM-1340 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 4.17.2 > Environment: Mac OS 10.7 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.next > > > During profiling, BeanPopulator can represent a 7% overhead. It may not seem like a lot, but for something as relatively simple as what BeanPopulator should be doing, it seems to be quite a bit. > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.coordinator.TxStats.enabled > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.common.arjPropertyManager.getCoordinatorEnvironmentBean > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance > 2.5% - 1,587 ms - 10,000 inv. java.lang.StringBuilder. > 2.3% - 1,507 ms - 10,000 inv. java.lang.StringBuilder.toString > 0.0% - 320 ?s - 10,000 inv. java.util.concurrent.ConcurrentMap.containsKey > 0.0% - 61 ?s - 10,000 inv. java.lang.Class.getName > 0.0% - 25 ?s - 10,000 inv. java.util.concurrent.ConcurrentMap.get -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 7 10:57:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 7 Oct 2015 10:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1340) BeanPopulator overhead needs looking into In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1340: -------------------------------- Attachment: SpeedTest.java Hot_Spots.html Call_Tree.html > BeanPopulator overhead needs looking into > ----------------------------------------- > > Key: JBTM-1340 > URL: https://issues.jboss.org/browse/JBTM-1340 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 4.17.2 > Environment: Mac OS 10.7 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.next > > Attachments: Call_Tree.html, Hot_Spots.html, SpeedTest.java > > > During profiling, BeanPopulator can represent a 7% overhead. It may not seem like a lot, but for something as relatively simple as what BeanPopulator should be doing, it seems to be quite a bit. > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.coordinator.TxStats.enabled > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.common.arjPropertyManager.getCoordinatorEnvironmentBean > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance > 2.5% - 1,587 ms - 10,000 inv. java.lang.StringBuilder. > 2.3% - 1,507 ms - 10,000 inv. java.lang.StringBuilder.toString > 0.0% - 320 ?s - 10,000 inv. java.util.concurrent.ConcurrentMap.containsKey > 0.0% - 61 ?s - 10,000 inv. java.lang.Class.getName > 0.0% - 25 ?s - 10,000 inv. java.util.concurrent.ConcurrentMap.get -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 08:21:00 2015 From: issues at jboss.org (Hayk Hovsepyan (JIRA)) Date: Thu, 8 Oct 2015 08:21:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2533) Possibility to run "scripts/hudson/narayana.sh" on different platforms. In-Reply-To: References: Message-ID: Hayk Hovsepyan created JBTM-2533: ------------------------------------ Summary: Possibility to run "scripts/hudson/narayana.sh" on different platforms. Key: JBTM-2533 URL: https://issues.jboss.org/browse/JBTM-2533 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Testing Affects Versions: 5.2.5.Final Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan Priority: Blocker Fix For: 5.next Currently "scripts/hudson/narayana.sh" uses "sed" command with "-i" option, so it looks like: "sed -i file -e expression". "-i" option is not supported on some platforms (HP-UX). We need to apply workaround here and modify "sed" commands to be in this format: "sed -e expression file > file.tmp && mv file.tmp file" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 08:35:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 8 Oct 2015 08:35:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2533) Possibility to run "scripts/hudson/narayana.sh" on different platforms. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116391#comment-13116391 ] Tom Jenkinson commented on JBTM-2533: ------------------------------------- Hi Hayk, There isn't an "SLA" (read versioned API) on the script but if you are happy with that caveat, I am happy to review any PR for this. Thanks, Tom > Possibility to run "scripts/hudson/narayana.sh" on different platforms. > ----------------------------------------------------------------------- > > Key: JBTM-2533 > URL: https://issues.jboss.org/browse/JBTM-2533 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Affects Versions: 5.2.5.Final > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Fix For: 5.next > > > Currently "scripts/hudson/narayana.sh" uses "sed" command with "-i" option, so it looks like: > "sed -i file -e expression". > "-i" option is not supported on some platforms (HP-UX). > We need to apply workaround here and modify "sed" commands to be in this format: > "sed -e expression file > file.tmp && mv file.tmp file" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 10:47:00 2015 From: issues at jboss.org (Hayk Hovsepyan (JIRA)) Date: Thu, 8 Oct 2015 10:47:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2533) Possibility to run "scripts/hudson/narayana.sh" on different platforms. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2533 started by Hayk Hovsepyan. -------------------------------------------- > Possibility to run "scripts/hudson/narayana.sh" on different platforms. > ----------------------------------------------------------------------- > > Key: JBTM-2533 > URL: https://issues.jboss.org/browse/JBTM-2533 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Affects Versions: 5.2.5.Final > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Fix For: 5.next > > > Currently "scripts/hudson/narayana.sh" uses "sed" command with "-i" option, so it looks like: > "sed -i file -e expression". > "-i" option is not supported on some platforms (HP-UX). > We need to apply workaround here and modify "sed" commands to be in this format: > "sed -e expression file > file.tmp && mv file.tmp file" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 8 10:54:00 2015 From: issues at jboss.org (Hayk Hovsepyan (JIRA)) Date: Thu, 8 Oct 2015 10:54:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2533) Possibility to run "scripts/hudson/narayana.sh" on different platforms. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hayk Hovsepyan updated JBTM-2533: --------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jbosstm/narayana/pull/926 > Possibility to run "scripts/hudson/narayana.sh" on different platforms. > ----------------------------------------------------------------------- > > Key: JBTM-2533 > URL: https://issues.jboss.org/browse/JBTM-2533 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Affects Versions: 5.2.5.Final > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Fix For: 5.next > > > Currently "scripts/hudson/narayana.sh" uses "sed" command with "-i" option, so it looks like: > "sed -i file -e expression". > "-i" option is not supported on some platforms (HP-UX). > We need to apply workaround here and modify "sed" commands to be in this format: > "sed -e expression file > file.tmp && mv file.tmp file" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 02:55:00 2015 From: issues at jboss.org (Alexander Morozov (JIRA)) Date: Fri, 9 Oct 2015 02:55:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2434) @Transactional annotation on stereotype leads to error "ARJUNA016107: Expected an @Transactional annotation at class and/or method level" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116726#comment-13116726 ] Alexander Morozov commented on JBTM-2434: ----------------------------------------- Several days ago I've faced with the same issue, but on Wildfly 9.0.2 :( > @Transactional annotation on stereotype leads to error "ARJUNA016107: Expected an @Transactional annotation at class and/or method level" > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2434 > URL: https://issues.jboss.org/browse/JBTM-2434 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Environment: JDK 1.7u72 x64, Windows 8.1 Professional > Reporter: Alexander Morozov > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.2.0 > > Attachments: wildfly-jta-cdi.zip > > > It is seems that CDI Transactional extesion doesn't support well @Transactional annotation on CDI stereotypes. JTA transaction is created by library interceptor, but in case of exception on component's side, _com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.getTransactional(...)_ method failed to locate @Transactional annotation on target component. It leads to exception like that > {code} > java.lang.RuntimeException: ARJUNA016107: Expected an @Transactional annotation at class and/or method level > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.getTransactional(TransactionalInterceptorBase.java:83) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.handleException(TransactionalInterceptorBase.java:118) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInCallerTx(TransactionalInterceptorBase.java:106) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory.intercept(TransactionalInterceptorMandatory.java:58) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) > at com.mycompany.wildfly.jta.cdi.UserEventDispatcher$Proxy$_$$_WeldSubclass.dispatch(Unknown Source) > at com.mycompany.wildfly.jta.cdi.UserEventDispatcher$Proxy$_$$_WeldClientProxy.dispatch(Unknown Source) > at com.mycompany.wildfly.jta.cdi.UserApplicationService.addUser(UserApplicationService.java:18) > at com.mycompany.wildfly.jta.cdi.UserApplicationService$Proxy$_$$_WeldSubclass.addUser$$super(Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) > at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInOurTx(TransactionalInterceptorBase.java:92) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired.intercept(TransactionalInterceptorRequired.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) > at com.mycompany.wildfly.jta.cdi.UserApplicationService$Proxy$_$$_WeldSubclass.addUser(Unknown Source) > at com.mycompany.wildfly.jta.cdi.UserApplicationService$Proxy$_$$_WeldClientProxy.addUser(Unknown Source) > at com.mycompany.wildfly.jta.cdi.BootstrapExtension.start(BootstrapExtension.java:20) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > ......... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 03:56:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 9 Oct 2015 03:56:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2434) @Transactional annotation on stereotype leads to error "ARJUNA016107: Expected an @Transactional annotation at class and/or method level" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116750#comment-13116750 ] Tom Jenkinson commented on JBTM-2434: ------------------------------------- You could try doing your own custom build of WildFly with version 5.2.0 of Narayana in it or upgrade to WFLY 10? > @Transactional annotation on stereotype leads to error "ARJUNA016107: Expected an @Transactional annotation at class and/or method level" > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2434 > URL: https://issues.jboss.org/browse/JBTM-2434 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Environment: JDK 1.7u72 x64, Windows 8.1 Professional > Reporter: Alexander Morozov > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.2.0 > > Attachments: wildfly-jta-cdi.zip > > > It is seems that CDI Transactional extesion doesn't support well @Transactional annotation on CDI stereotypes. JTA transaction is created by library interceptor, but in case of exception on component's side, _com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.getTransactional(...)_ method failed to locate @Transactional annotation on target component. It leads to exception like that > {code} > java.lang.RuntimeException: ARJUNA016107: Expected an @Transactional annotation at class and/or method level > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.getTransactional(TransactionalInterceptorBase.java:83) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.handleException(TransactionalInterceptorBase.java:118) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInCallerTx(TransactionalInterceptorBase.java:106) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory.intercept(TransactionalInterceptorMandatory.java:58) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) > at com.mycompany.wildfly.jta.cdi.UserEventDispatcher$Proxy$_$$_WeldSubclass.dispatch(Unknown Source) > at com.mycompany.wildfly.jta.cdi.UserEventDispatcher$Proxy$_$$_WeldClientProxy.dispatch(Unknown Source) > at com.mycompany.wildfly.jta.cdi.UserApplicationService.addUser(UserApplicationService.java:18) > at com.mycompany.wildfly.jta.cdi.UserApplicationService$Proxy$_$$_WeldSubclass.addUser$$super(Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) > at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInOurTx(TransactionalInterceptorBase.java:92) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired.intercept(TransactionalInterceptorRequired.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) > at com.mycompany.wildfly.jta.cdi.UserApplicationService$Proxy$_$$_WeldSubclass.addUser(Unknown Source) > at com.mycompany.wildfly.jta.cdi.UserApplicationService$Proxy$_$$_WeldClientProxy.addUser(Unknown Source) > at com.mycompany.wildfly.jta.cdi.BootstrapExtension.start(BootstrapExtension.java:20) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > ......... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 06:42:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 9 Oct 2015 06:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2529) Create WildFly update issue as part of the JIRA update In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2529: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/927 > Create WildFly update issue as part of the JIRA update > ------------------------------------------------------ > > Key: JBTM-2529 > URL: https://issues.jboss.org/browse/JBTM-2529 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Release Process > 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 Oct 9 07:48:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 9 Oct 2015 07:48:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2533) Possibility to run "scripts/hudson/narayana.sh" on different platforms. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2533: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Possibility to run "scripts/hudson/narayana.sh" on different platforms. > ----------------------------------------------------------------------- > > Key: JBTM-2533 > URL: https://issues.jboss.org/browse/JBTM-2533 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Affects Versions: 5.2.5.Final > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Fix For: 5.next > > > Currently "scripts/hudson/narayana.sh" uses "sed" command with "-i" option, so it looks like: > "sed -i file -e expression". > "-i" option is not supported on some platforms (HP-UX). > We need to apply workaround here and modify "sed" commands to be in this format: > "sed -e expression file > file.tmp && mv file.tmp file" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 07:52:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 9 Oct 2015 07:52:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2534) HQStore handing on QA_JTS_JDKORB In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2534: ----------------------------------- Summary: HQStore handing 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: Gytis Trikleris Fix For: 5.next http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/127/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 07:59:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 9 Oct 2015 07:59:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2534) HQStore hanging 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 updated JBTM-2534: -------------------------------- Summary: HQStore hanging on QA_JTS_JDKORB (was: HQStore handing on QA_JTS_JDKORB) > HQStore hanging 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: Gytis Trikleris > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/127/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 10:07:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 9 Oct 2015 10:07:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2535) Add support for Maria DB as JDBC ObjectStore driver In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2535: ----------------------------------- Summary: Add support for Maria DB as JDBC ObjectStore driver Key: JBTM-2535 URL: https://issues.jboss.org/browse/JBTM-2535 Project: JBoss Transaction Manager Issue Type: Enhancement Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 10:08:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 9 Oct 2015 10:08:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2535) Add support for Maria DB as JDBC ObjectStore driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2535: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/928 > Add support for Maria DB as JDBC ObjectStore driver > --------------------------------------------------- > > Key: JBTM-2535 > URL: https://issues.jboss.org/browse/JBTM-2535 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 9 10:10:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 9 Oct 2015 10:10:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2535) Add initial support for Maria DB as JDBC ObjectStore driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2535: -------------------------------- Summary: Add initial support for Maria DB as JDBC ObjectStore driver (was: Add support for Maria DB as JDBC ObjectStore driver) > Add initial support for Maria DB as JDBC ObjectStore driver > ----------------------------------------------------------- > > Key: JBTM-2535 > URL: https://issues.jboss.org/browse/JBTM-2535 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 05:40:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 12 Oct 2015 05:40:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-223) Check WL-to-JBossTS interoperability (via JTS). In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reassigned JBTM-223: ------------------------------------- Assignee: Michael Musgrove > Check WL-to-JBossTS interoperability (via JTS). > ----------------------------------------------- > > Key: JBTM-223 > URL: https://issues.jboss.org/browse/JBTM-223 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Mark Little > Assignee: Michael Musgrove > Fix For: 6.later > > > Extensible header structure corba call > key value slot ids > slot for transaction context is not in the well known slot > tx context was not defined so we used the market leader at the time -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 06:33:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 12 Oct 2015 06:33:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2536) Hornetq QA crashrec failures In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2536: -------------------------------------- Summary: Hornetq QA crashrec failures Key: JBTM-2536 URL: https://issues.jboss.org/browse/JBTM-2536 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Affects Versions: 5.2.5.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next Quite a few of the crash recovery tests are failing when running with the journal store: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/128/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 07:11:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 12 Oct 2015 07:11:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2530 started by Michael Musgrove. ---------------------------------------------- > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 10:34:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 12 Oct 2015 10:34:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117433#comment-13117433 ] Gytis Trikleris edited comment on JBTM-2531 at 10/12/15 10:33 AM: ------------------------------------------------------------------ It has just failed on WildFly 9.0.1.Final and Narayana 5.0.6.Final. So it seems that this is an environment issue rather than something introduced by the code change. http://albany.eng.hst.ams2.redhat.com/job/gytis-JBTM-2531/19/ was (Author: gytis): It has just failed on WildFly 9.0.1.Final and Narayana 5.0.6.Final. So it seems that this is an environment issue rather than something introduced by the code change. > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 10:34:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 12 Oct 2015 10:34:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117433#comment-13117433 ] Gytis Trikleris commented on JBTM-2531: --------------------------------------- It has just failed on WildFly 9.0.1.Final and Narayana 5.0.6.Final. So it seems that this is an environment issue rather than something introduced by the code change. > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 12 11:18:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Oct 2015 11:18:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2535) Add initial support for Maria DB as JDBC ObjectStore driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117481#comment-13117481 ] Tom Jenkinson commented on JBTM-2535: ------------------------------------- MariaDB does not allow select for update - this is a problem. > Add initial support for Maria DB as JDBC ObjectStore driver > ----------------------------------------------------------- > > Key: JBTM-2535 > URL: https://issues.jboss.org/browse/JBTM-2535 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 05:57:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 13 Oct 2015 05:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2519) Add privileged actions to XTS to make it work with security manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2519: ---------------------------------- Summary: Add privileged actions to XTS to make it work with security manager (was: Investigate if XTS and RTS work with enabled security manager) > Add privileged actions to XTS to make it work with security manager > ------------------------------------------------------------------- > > Key: JBTM-2519 > URL: https://issues.jboss.org/browse/JBTM-2519 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST, 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 Tue Oct 13 05:57:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 13 Oct 2015 05:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2519) Add privileged actions to XTS to make it work with security manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2519: ---------------------------------- Component/s: (was: REST) > Add privileged actions to XTS to make it work with security manager > ------------------------------------------------------------------- > > Key: JBTM-2519 > URL: https://issues.jboss.org/browse/JBTM-2519 > 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 Tue Oct 13 06:45:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 13 Oct 2015 06:45:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2529) Create WildFly update issue as part of the JIRA update In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2529: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create WildFly update issue as part of the JIRA update > ------------------------------------------------------ > > Key: JBTM-2529 > URL: https://issues.jboss.org/browse/JBTM-2529 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Release Process > 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 Tue Oct 13 06:59:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 13 Oct 2015 06:59:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2536) Hornetq QA crashrec failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-2536. ---------------------------------- Resolution: Duplicate Issue Duplicate of JBTM-2534 - note that the build is using JDK 7 so I have kicked off another run with jdk8.latest to see if the issue is related to the JDK version. > Hornetq QA crashrec failures > ---------------------------- > > Key: JBTM-2536 > URL: https://issues.jboss.org/browse/JBTM-2536 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Quite a few of the crash recovery tests are failing when running with the journal store: > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/128/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 07:38:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 13 Oct 2015 07:38:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2535) Add initial support for Maria DB as JDBC ObjectStore driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2535: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add initial support for Maria DB as JDBC ObjectStore driver > ----------------------------------------------------------- > > Key: JBTM-2535 > URL: https://issues.jboss.org/browse/JBTM-2535 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 13 07:44:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 13 Oct 2015 07:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2535) Add initial support for Maria DB as JDBC ObjectStore driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117709#comment-13117709 ] Tom Jenkinson commented on JBTM-2535: ------------------------------------- Changed to use the select, and then update separate (in a local transaction) > Add initial support for Maria DB as JDBC ObjectStore driver > ----------------------------------------------------------- > > Key: JBTM-2535 > URL: https://issues.jboss.org/browse/JBTM-2535 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 14 08:29:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 14 Oct 2015 08:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118191#comment-13118191 ] Gytis Trikleris commented on JBTM-2531: --------------------------------------- Separate job doesn't fail any more after the JDK update. I'll close the issue, if Narayana job passes. > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 03:56:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 03:56:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118491#comment-13118491 ] Tom Jenkinson commented on JBTM-2530: ------------------------------------- Initial failures is because build can't find "mvn" {code} QA Test Suite orb=idlj site -PcodeCoverage -Pfindbugs Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/build.xml get.maven.libs: BUILD FAILED /home/hudson/workspace/narayana-codeCoverage/qa/build.xml:65: Execute failed: java.io.IOException: Cannot run program "mvn" (in directory "/home/hudson/workspace/narayana-codeCoverage/qa"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1042) at java.lang.Runtime.exec(Runtime.java:620) at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Execute.java:862) at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:481) at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:495) at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:631) at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:672) at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:498) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.Target.performTasks(Target.java:411) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) at org.apache.tools.ant.Project.executeTarget(Project.java:1368) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.Main.runBuild(Main.java:809) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:187) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1023) ... 24 more {code} > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 04:02:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 04:02:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2530: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jbosstm/narayana/pull/929 > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 04:48:01 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 15 Oct 2015 04:48:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118517#comment-13118517 ] Michael Musgrove commented on JBTM-2530: ---------------------------------------- Good catch. I still think it is to do with the JDK version. I have upgrded the jdk on the linux slaves and pinned the job to the linux64 label. > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 04:53:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 04:53:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118520#comment-13118520 ] Tom Jenkinson commented on JBTM-2530: ------------------------------------- Thanks Mike, I just wondered if it was borked due to not managing to build something and so falls back to trying to instrument JDK classes as that was all it had. nps > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:21:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 05:21:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2534) HQStore hanging 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 updated JBTM-2534: -------------------------------- Priority: Critical (was: Major) > HQStore hanging 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: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/127/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:22:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 05:22:00 -0400 (EDT) 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: -------------------------------- Priority: Major (was: Minor) > 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 Thu Oct 15 05:23:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 05:23:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2505) Java heap space issue on Brandon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2505: ----------------------------------- Assignee: (was: Tom Jenkinson) > Java heap space issue on Brandon > -------------------------------- > > Key: JBTM-2505 > URL: https://issues.jboss.org/browse/JBTM-2505 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.2.5.Final > Reporter: Gytis Trikleris > Attachments: consoleText.txt > > > narayana-AS800 build fails whenever it runs on Brandon due to not enough java heap space. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:24:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 05:24:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2463) QA suite failure: TestGroup_rawresources01_3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2463: ----------------------------------- Assignee: (was: Tom Jenkinson) > QA suite failure: TestGroup_rawresources01_3 > -------------------------------------------- > > Key: JBTM-2463 > URL: https://issues.jboss.org/browse/JBTM-2463 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-jdbcobjectstore/152/DB_TYPE=db2,jdk=jdk7.latest,slave=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:25:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 05:25:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2329) Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2329: ----------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2329 > URL: https://issues.jboss.org/browse/JBTM-2329 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > If an AbstractRecord type has resulted in a heuristic state, it would be useful to provide some form of management API to clear the state on the resource manager. > After discussion on the forum, it seems likely the API would be something like: > Update AbstractRecord to change the return type of value() to the HeuristicManagement interface (rather than Object). Although value() is maybe not the most accurate term and it does appear that this is used internally by XAResourceRecord in an unintended manner (i.e. not dealing with HeuristicInformation. > Add a new interface of modify the existing HeuristicInformation (the current version of which is to be deprecated in: JBTM-2328) > {code} > public interface HeuristicManagement > { > public void resolve() throws CouldNotResolveException; > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:25:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 05:25:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2329) Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2329: ----------------------------------- Assignee: (was: Michael Musgrove) > Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2329 > URL: https://issues.jboss.org/browse/JBTM-2329 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Michael Musgrove > Fix For: 5.later > > > If an AbstractRecord type has resulted in a heuristic state, it would be useful to provide some form of management API to clear the state on the resource manager. > After discussion on the forum, it seems likely the API would be something like: > Update AbstractRecord to change the return type of value() to the HeuristicManagement interface (rather than Object). Although value() is maybe not the most accurate term and it does appear that this is used internally by XAResourceRecord in an unintended manner (i.e. not dealing with HeuristicInformation. > Add a new interface of modify the existing HeuristicInformation (the current version of which is to be deprecated in: JBTM-2328) > {code} > public interface HeuristicManagement > { > public void resolve() throws CouldNotResolveException; > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:25:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 05:25:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2326: ----------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2326 > URL: https://issues.jboss.org/browse/JBTM-2326 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Tooling > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.later > > > Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L1017 so it might be useful to others. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:25:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 05:25:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2326: ----------------------------------- Assignee: (was: Michael Musgrove) > Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2326 > URL: https://issues.jboss.org/browse/JBTM-2326 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Tooling > Reporter: Tom Jenkinson > Fix For: 5.later > > > Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L1017 so it might be useful to others. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:26:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 15 Oct 2015 05:26:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2505) Java heap space issue on Brandon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118533#comment-13118533 ] Michael Musgrove commented on JBTM-2505: ---------------------------------------- I had a similar issue on sansa last night on the code coverage job. I updated the job config to give it more heap. > Java heap space issue on Brandon > -------------------------------- > > Key: JBTM-2505 > URL: https://issues.jboss.org/browse/JBTM-2505 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.2.5.Final > Reporter: Gytis Trikleris > Attachments: consoleText.txt > > > narayana-AS800 build fails whenever it runs on Brandon due to not enough java heap space. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:26:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 05:26:00 -0400 (EDT) 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: -------------------------------- Fix Version/s: 5.next (was: 5.later) > 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 Thu Oct 15 05:27:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 05:27:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2411) Investigate jgroups-raft and whether this can help with cloud object store In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2411: ----------------------------------- Assignee: (was: Tom Jenkinson) > Investigate jgroups-raft and whether this can help with cloud object store > -------------------------------------------------------------------------- > > Key: JBTM-2411 > URL: https://issues.jboss.org/browse/JBTM-2411 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Recovery, Transaction Core > Reporter: Tom Jenkinson > Fix For: 5.later > > > http://belaban.blogspot.ch/2015/05/release-of-jgroups-raft-02.html -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:28:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 05:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1860) Please document TransactionStatusManager scanner. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1860: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Please document TransactionStatusManager scanner. > ------------------------------------------------- > > Key: JBTM-1860 > URL: https://issues.jboss.org/browse/JBTM-1860 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Environment: JBoss EAP 5.x and 6.x > Reporter: Tom Ross > Assignee: Tom Jenkinson > Fix For: 5.next > > > JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them. > Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 05:29:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 05:29:00 -0400 (EDT) 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 ] Tom Jenkinson updated JBTM-2511: -------------------------------- Fix Version/s: 5.next (was: 5.later) > 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: Critical > 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 Oct 15 06:55:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 15 Oct 2015 06:55:00 -0400 (EDT) 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=13118563#comment-13118563 ] Michael Musgrove commented on JBTM-2511: ---------------------------------------- The issue only happens with jenkins and only under the control of the JMH harness (making it hard to debug). I don't think not having RTS performance testing is critical so I therefore propose to disable the RTS specific performance tests and downgrade 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 > Priority: Critical > 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 Oct 15 06:57:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 15 Oct 2015 06:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118564#comment-13118564 ] Michael Musgrove commented on JBTM-2530: ---------------------------------------- Lets wait for CI build narayana-codeCoverage/254/ before evaluating the priority of this JIRA > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 07:02:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 15 Oct 2015 07:02:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2519) Add privileged actions to XTS to make it work with security manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2519: ---------------------------------- Priority: Critical (was: Major) > Add privileged actions to XTS to make it work with security manager > ------------------------------------------------------------------- > > Key: JBTM-2519 > URL: https://issues.jboss.org/browse/JBTM-2519 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 15 07:15:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 15 Oct 2015 07:15:00 -0400 (EDT) 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: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/performance/pull/24 > 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: Critical > 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 Oct 15 07:29:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 15 Oct 2015 07:29:00 -0400 (EDT) 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: Major (was: Critical) > 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 Oct 15 07:33:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 Oct 2015 07:33:00 -0400 (EDT) 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=13118579#comment-13118579 ] Tom Jenkinson commented on JBTM-2511: ------------------------------------- Did you re-enable the job yet though? At that point (and assuming it is working) I agree its not critical. > 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 Oct 15 07:35:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 15 Oct 2015 07:35:00 -0400 (EDT) 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: Critical (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: Critical > 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 Oct 15 07:36:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 15 Oct 2015 07:36:00 -0400 (EDT) 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=13118581#comment-13118581 ] Michael Musgrove commented on JBTM-2511: ---------------------------------------- I've moved it back to critical and will await the outcome of the CI job before updating it again > 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: Critical > 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 Oct 15 14:34:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 15 Oct 2015 14:34:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2530: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done CI job passed. We should update the job sometime to check if it still fails with the 32 bit JDK > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 04:58:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 19 Oct 2015 04:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2519) Add privileged actions to XTS to make it work with security manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2519: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add privileged actions to XTS to make it work with security manager > ------------------------------------------------------------------- > > Key: JBTM-2519 > URL: https://issues.jboss.org/browse/JBTM-2519 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 06:43:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 06:43:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Can't build WFLY on a machine that has only built for IBM Orb In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2537: ----------------------------------- Summary: Can't build WFLY on a machine that has only built for IBM Orb Key: JBTM-2537 URL: https://issues.jboss.org/browse/JBTM-2537 Project: JBoss Transaction Manager Issue Type: Bug Components: JTS Reporter: Tom Jenkinson Fix For: 5.later 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 Mon Oct 19 06:44:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 06:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Can't build WFLY on a machine that has only built for IBM Orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119364#comment-13119364 ] Tom Jenkinson commented on JBTM-2537: ------------------------------------- I have disabled the job and added an .m2 rm so we don't miss it in future > Can't build WFLY on a machine that has only built for IBM Orb > ------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Fix For: 5.later > > > 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 Mon Oct 19 06:46:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 06:46:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2534) HQStore hanging on QA_JTS_JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119365#comment-13119365 ] Tom Jenkinson commented on JBTM-2534: ------------------------------------- I have disabled the job > HQStore hanging 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: Gytis Trikleris > Priority: Critical > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/127/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 06:47:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 06:47:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2534) HQStore hanging 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 updated JBTM-2534: -------------------------------- Description: 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} was:http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/127/ > HQStore hanging 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: Gytis Trikleris > 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 Mon Oct 19 06:47:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 06:47:00 -0400 (EDT) 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 updated JBTM-2534: -------------------------------- Summary: HQStore crashrec failures on QA_JTS_JDKORB (was: HQStore hanging on QA_JTS_JDKORB) > 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: Gytis Trikleris > 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 Mon Oct 19 06:47:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 19 Oct 2015 06:47:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2531: ---------------------------------- Priority: Major (was: Critical) > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 06:48:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 19 Oct 2015 06:48:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118191#comment-13118191 ] Gytis Trikleris edited comment on JBTM-2531 at 10/19/15 6:47 AM: ----------------------------------------------------------------- Separate job doesn't fail any more after the JDK update. I'll close the issue, if Narayana job passes on Janei. For now decreasing severity to Major. was (Author: gytis): Separate job doesn't fail any more after the JDK update. I'll close the issue, if Narayana job passes. > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 06:49:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 06:49:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2538) Benchmarking failure In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2538: ----------------------------------- Summary: 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 Mon Oct 19 06:50:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 06:50:00 -0400 (EDT) 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=13119366#comment-13119366 ] Tom Jenkinson commented on JBTM-2538: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmarks/41/ http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmarks/42/ > 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 Mon Oct 19 06:51:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 06:51:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Can't build WFLY on a machine that has only built for IBM Orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119367#comment-13119367 ] Tom Jenkinson commented on JBTM-2537: ------------------------------------- Haven't marked as critical as its not a regression that I can see even though its pretty important > Can't build WFLY on a machine that has only built for IBM Orb > ------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > 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 Mon Oct 19 06:51:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 06:51:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Can't build WFLY on a machine that has only built for IBM Orb 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: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Can't build WFLY on a machine that has only built for IBM Orb > ------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > 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 Mon Oct 19 06:53:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 06:53:00 -0400 (EDT) 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=13119368#comment-13119368 ] Tom Jenkinson commented on JBTM-2538: ------------------------------------- Haven't disabled job yet as different product failures (same place though) in both runs so may not be fatal. Different nodes though so it might be... > 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 Mon Oct 19 06:55:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 06:55:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2539) QA suite failure: jdbcresources01_pgsql_jndi (JDBC store) In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2539: ----------------------------------- Summary: QA suite failure: jdbcresources01_pgsql_jndi (JDBC store) Key: JBTM-2539 URL: https://issues.jboss.org/browse/JBTM-2539 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Tom Jenkinson Priority: Minor Fix For: 5.next http://albany.eng.hst.ams2.redhat.com/job/narayana-jdbcobjectstore/DB_TYPE=db2,jdk=jdk7.latest,slave=linux/164/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 08:45:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 08:45:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2539) QA suite failure: jdbcresources01_pgsql_jndi (JDBC store) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2539: -------------------------------- Fix Version/s: 5.later (was: 5.next) > QA suite failure: jdbcresources01_pgsql_jndi (JDBC store) > --------------------------------------------------------- > > Key: JBTM-2539 > URL: https://issues.jboss.org/browse/JBTM-2539 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-jdbcobjectstore/DB_TYPE=db2,jdk=jdk7.latest,slave=linux/164/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 19 09:03:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Oct 2015 09:03:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2533) Possibility to run "scripts/hudson/narayana.sh" on different platforms. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2533: -------------------------------- Issue Type: Task (was: Feature Request) > Possibility to run "scripts/hudson/narayana.sh" on different platforms. > ----------------------------------------------------------------------- > > Key: JBTM-2533 > URL: https://issues.jboss.org/browse/JBTM-2533 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.2.5.Final > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Fix For: 5.next > > > Currently "scripts/hudson/narayana.sh" uses "sed" command with "-i" option, so it looks like: > "sed -i file -e expression". > "-i" option is not supported on some platforms (HP-UX). > We need to apply workaround here and modify "sed" commands to be in this format: > "sed -e expression file > file.tmp && mv file.tmp file" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 02:43:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 20 Oct 2015 02:43:00 -0400 (EDT) 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:comment-tabpanel&focusedCommentId=13119694#comment-13119694 ] Amos Feng commented on JBTM-2115: --------------------------------- ArjunaCore/arjuna/pom.xml - ObjStoreBrowserTest it looks good and I will remove it from the excluded tests - LogStressTest2.java it looks like not a unit test and needs to run for 4 hours. So I think it should be excluded ArjunaJTA/jdbc/pom.xml - There is no excluded test ArjunaJTA/jta/pom.xml - */io/narayana/perf/product/* I think all of them should be the performance tests - */commitmarkable/* - */recovery/* it looks like that the tests do not work with byteman and jacoco and I will investigate it. ArjunaJTA/spi/pom.xml - There is no excluded test XTS/localjunit/pom.xml - it should be in the subtask > 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 Tue Oct 20 09:09:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 20 Oct 2015 09:09:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2531: -------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/performance/pull/25 > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 09:10:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 20 Oct 2015 09:10:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2531: -------------------------------- Status: Open (was: Pull Request Sent) Git Pull Request: (was: https://github.com/jbosstm/performance/pull/25) > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 09:14:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 20 Oct 2015 09:14:00 -0400 (EDT) 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:comment-tabpanel&focusedCommentId=13119942#comment-13119942 ] Michael Musgrove commented on JBTM-2534: ---------------------------------------- export WORKSPACE=`pwd` export SUN_ORB=1 JAC_ORB=0 IBM_ORB=0 OPENJDK_ORB=0 export PROFILE=NONE NARAYANA_BUILD=0 NARAYANA_TESTS=0 AS_BUILD=0 BLACKTIE=0 OSGI_TESTS=0 JTA_CDI_TESTS=0 XTS_AS_TESTS=0 RTS_AS_TESTS=0 JTA_AS_TESTS=0 TXF_TESTS=0 XTS_TESTS=0 txbridge=0 RTS_TESTS=0 QA_TESTS=0 PERF_TESTS=0 #QA_TESTGROUP=jtsremote QA_TESTMETHODS=JTSRemote_ImplicitPropagationTest export QA_TESTGROUP=currenttests01 QA_TESTMETHODS= export QA_TESTS=1 QA_TRACE=0 QA_TESTGROUP=crashrecovery05_1 QA_TESTMETHODS=CrashRecovery05_1_Test01 NARAYANA_VERSION=5.2.6.Final-SNAPSHOT export QA_PROFILE="-Dprofile=hornetq" export QA_TESTS=1 NARAYANA_BUILD=1 ./scripts/hudson/narayana.sh > 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: Gytis Trikleris > 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 Oct 20 09:14:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 20 Oct 2015 09:14:00 -0400 (EDT) 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: Major (was: Critical) > 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 Oct 20 09:15:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 20 Oct 2015 09:15:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Can't build WFLY on a machine that has only built for IBM Orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2537: ----------------------------------- Assignee: Tom Jenkinson > Can't build WFLY on a machine that has only built for IBM Orb > ------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > 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 Tue Oct 20 09:15:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 20 Oct 2015 09:15:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Can't build WFLY on a machine that has only built for IBM Orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2537: ----------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > Can't build WFLY on a machine that has only built for IBM Orb > ------------------------------------------------------------- > > 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 Tue Oct 20 09:16:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 20 Oct 2015 09:16:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2531) XTS build regularly fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2531. --------------------------------- Fix Version/s: (was: 5.next) Resolution: Out of Date > XTS build regularly fails > ------------------------- > > Key: JBTM-2531 > URL: https://issues.jboss.org/browse/JBTM-2531 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > > http://albany.eng.hst.ams2.redhat.com/job/narayana/946/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/947/ > http://albany.eng.hst.ams2.redhat.com/job/narayana/949/ > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/241/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 20 09:16:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 20 Oct 2015 09:16:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Can't build WFLY on a machine that has only built for IBM Orb 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: Minor (was: Major) > Can't build WFLY on a machine that has only built for IBM Orb > ------------------------------------------------------------- > > 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 Tue Oct 20 10:12:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 20 Oct 2015 10:12:00 -0400 (EDT) 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: Pull Request Sent (was: Open) Git Pull Request: 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 Wed Oct 21 08:19:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2535) Add initial support for Maria DB as JDBC ObjectStore driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2535. ------------------------------- > Add initial support for Maria DB as JDBC ObjectStore driver > ----------------------------------------------------------- > > Key: JBTM-2535 > URL: https://issues.jboss.org/browse/JBTM-2535 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.6.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:19:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2533) Possibility to run "scripts/hudson/narayana.sh" on different platforms. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2533. ------------------------------- > Possibility to run "scripts/hudson/narayana.sh" on different platforms. > ----------------------------------------------------------------------- > > Key: JBTM-2533 > URL: https://issues.jboss.org/browse/JBTM-2533 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.2.5.Final > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Fix For: 5.2.6.Final > > > Currently "scripts/hudson/narayana.sh" uses "sed" command with "-i" option, so it looks like: > "sed -i file -e expression". > "-i" option is not supported on some platforms (HP-UX). > We need to apply workaround here and modify "sed" commands to be in this format: > "sed -e expression file > file.tmp && mv file.tmp file" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:19:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2530) jacoco failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2530. ------------------------------- > jacoco failures > --------------- > > Key: JBTM-2530 > URL: https://issues.jboss.org/browse/JBTM-2530 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.2.6.Final > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/240/console > The qa build is attempting to instrument java classes. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:19:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2529) Create WildFly update issue as part of the JIRA update In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2529. ------------------------------- > Create WildFly update issue as part of the JIRA update > ------------------------------------------------------ > > Key: JBTM-2529 > URL: https://issues.jboss.org/browse/JBTM-2529 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Release Process > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.2.6.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:19:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2526) Create pre-release checking script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2526. ------------------------------- > Create pre-release checking script > ---------------------------------- > > Key: JBTM-2526 > URL: https://issues.jboss.org/browse/JBTM-2526 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Build System, Release Process > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.2.6.Final > > > Write script to do tests, deprecation, and blockers checking before executing the release. > There are example bash scripts for deprecation and tests checking already, but they should be merged into one and be configurable. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:19:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2519) Add privileged actions to XTS to make it work with security manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2519. ------------------------------- > Add privileged actions to XTS to make it work with security manager > ------------------------------------------------------------------- > > Key: JBTM-2519 > URL: https://issues.jboss.org/browse/JBTM-2519 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.2.6.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:20:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2512) Include BlackTie javadoc on Narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2512. ------------------------------- > Include BlackTie javadoc on Narayana.io > --------------------------------------- > > Key: JBTM-2512 > URL: https://issues.jboss.org/browse/JBTM-2512 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.2.6.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:20:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2492) Build and deploy Blacktie as part of BRP.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2492. ------------------------------- > Build and deploy Blacktie as part of BRP.xml > -------------------------------------------- > > Key: JBTM-2492 > URL: https://issues.jboss.org/browse/JBTM-2492 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.2.6.Final > > > We only update the Blacktie java artifacts so these should be able to be done from any machine: > {code} > call "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" > build.bat -f blacktie\wildfly-blacktie\pom.xml install -DskipTests > build.bat -f blacktie\pom.xml install -DskipTests > build.bat -f blacktie\pom.xml deploy -DskipTests > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:20:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2491) JTS and JacORB NS Docker images quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2491. ------------------------------- > JTS and JacORB NS Docker images quickstart > ------------------------------------------ > > Key: JBTM-2491 > URL: https://issues.jboss.org/browse/JBTM-2491 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.2.6.Final > > > Create a quickstart for JTS and JacORB Name Server Docker images. > Additionally, add Kubernetes pod configuration for that. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:20:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2476) When a transaction times out, print the stack traces of the threads involved In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2476. ------------------------------- > When a transaction times out, print the stack traces of the threads involved > ---------------------------------------------------------------------------- > > Key: JBTM-2476 > URL: https://issues.jboss.org/browse/JBTM-2476 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.6.Final > > > Would be useful to help understand what the code was doing when the transaction times out. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:20:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1854) Journal failures in CI test suite on JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1854. ------------------------------- > Journal failures in CI test suite on JDKORB > ------------------------------------------- > > Key: JBTM-1854 > URL: https://issues.jboss.org/browse/JBTM-1854 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.6.Final > > Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz > > > The first CI job link includes: > CurrentTests01_Test036 > jtsremote JTSRemote_ImplicitPropagationTest > crashrecovery02_2 CrashRecovery02_2 - all of them > crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10 > crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them) > The second CI job link includes: > JTSRemote_ImplicitPropagationTest failure > CrashRecovery02_2_Test46 hang -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:20:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:01 -0400 (EDT) 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 updated JBTM-2538: -------------------------------- Fix Version/s: 5.next (was: 5.2.6.Final) > 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 Wed Oct 21 08:20:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1340) BeanPopulator overhead needs looking into In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1340. ------------------------------- > BeanPopulator overhead needs looking into > ----------------------------------------- > > Key: JBTM-1340 > URL: https://issues.jboss.org/browse/JBTM-1340 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 4.17.2 > Environment: Mac OS 10.7 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.2.6.Final > > Attachments: Call_Tree.html, Hot_Spots.html, SpeedTest.java > > > During profiling, BeanPopulator can represent a 7% overhead. It may not seem like a lot, but for something as relatively simple as what BeanPopulator should be doing, it seems to be quite a bit. > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.coordinator.TxStats.enabled > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.common.arjPropertyManager.getCoordinatorEnvironmentBean > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance > 2.5% - 1,587 ms - 10,000 inv. java.lang.StringBuilder. > 2.3% - 1,507 ms - 10,000 inv. java.lang.StringBuilder.toString > 0.0% - 320 ?s - 10,000 inv. java.util.concurrent.ConcurrentMap.containsKey > 0.0% - 61 ?s - 10,000 inv. java.lang.Class.getName > 0.0% - 25 ?s - 10,000 inv. java.util.concurrent.ConcurrentMap.get -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:20:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2120) Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2120. ------------------------------- > Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-2120 > URL: https://issues.jboss.org/browse/JBTM-2120 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.6.Final > > > Pull https://github.com/jbosstm/narayana/pull/598 added deferred throwables in case the XAR::end fails during commit. It doesn't handle the case of the HEURISTIC_ROLLBACK of a first resource where Narayana rolls back the remaining participants and then clears the failed/heuristic lists (and marks the txn as rolled back). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:20:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Can't build WFLY on a machine that has only built for IBM Orb 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: -------------------------------- Fix Version/s: 5.next (was: 5.2.6.Final) > Can't build WFLY on a machine that has only built for IBM Orb > ------------------------------------------------------------- > > 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 Wed Oct 21 08:20:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:01 -0400 (EDT) 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 updated JBTM-2532: -------------------------------- Fix Version/s: 5.next (was: 5.2.6.Final) > 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 Wed Oct 21 08:20:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:01 -0400 (EDT) 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.6.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 Wed Oct 21 08:20:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:01 -0400 (EDT) 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 ] Tom Jenkinson updated JBTM-2511: -------------------------------- Fix Version/s: 5.next (was: 5.2.6.Final) > 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 Wed Oct 21 08:20:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:01 -0400 (EDT) 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.6.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 > 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 Wed Oct 21 08:20:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:20:01 -0400 (EDT) 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 updated JBTM-2534: -------------------------------- Fix Version/s: 5.next (was: 5.2.6.Final) > 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: Gytis Trikleris > 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 Wed Oct 21 08:21:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:00 -0400 (EDT) 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.6.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 > 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 Wed Oct 21 08:21:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:00 -0400 (EDT) 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.6.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 Wed Oct 21 08:21:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:00 -0400 (EDT) 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.6.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 > 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 Wed Oct 21 08:21:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:00 -0400 (EDT) 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.6.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 Wed Oct 21 08:21:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:01 -0400 (EDT) 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.6.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 Wed Oct 21 08:21:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:01 -0400 (EDT) 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: -------------------------------- Fix Version/s: 5.next (was: 5.2.6.Final) > 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 Wed Oct 21 08:21:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:01 -0400 (EDT) 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.6.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 Wed Oct 21 08:21:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:01 -0400 (EDT) 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.6.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: Optional > 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 Wed Oct 21 08:21:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:01 -0400 (EDT) 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.6.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 Wed Oct 21 08:21:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:01 -0400 (EDT) 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.6.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 Wed Oct 21 08:21:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:01 -0400 (EDT) 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.6.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 > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:21:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1860) Please document TransactionStatusManager scanner. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1860: -------------------------------- Fix Version/s: 5.next (was: 5.2.6.Final) > Please document TransactionStatusManager scanner. > ------------------------------------------------- > > Key: JBTM-1860 > URL: https://issues.jboss.org/browse/JBTM-1860 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Environment: JBoss EAP 5.x and 6.x > Reporter: Tom Ross > Assignee: Tom Jenkinson > Fix For: 5.next > > > JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them. > Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 08:21:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:01 -0400 (EDT) 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.6.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: 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 Wed Oct 21 08:21:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:01 -0400 (EDT) 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.6.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 > 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 Wed Oct 21 08:21:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 08:21:01 -0400 (EDT) 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.6.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 Wed Oct 21 11:40:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 21 Oct 2015 11:40:00 -0400 (EDT) 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:comment-tabpanel&focusedCommentId=13120610#comment-13120610 ] Gytis Trikleris commented on JBTM-2532: --------------------------------------- I'm able to enable code coverage for test in unit package. However, crash-recovery-tests package does not generate any results. It seems that we're hitting the issue described in [1], [2], [3]. I'll have to look into a possibility of repackaging crash recovery tests, otherwise we might not be able to test code coverage. [1] https://community.jboss.org/message/817252 [2] https://issues.jboss.org/browse/ARQ-1014 [3] https://issues.jboss.org/browse/ARQ-918 > 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 Wed Oct 21 11:44:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 11:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2540) Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2540: ----------------------------------- Summary: Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT Key: JBTM-2540 URL: https://issues.jboss.org/browse/JBTM-2540 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie, Build System Affects Versions: 5.2.6.Final Reporter: Tom Jenkinson Assignee: Amos Feng Priority: Blocker Fix For: 5.next {code} [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] WildFly: Blacktie Subsystem Parent ................ SUCCESS [0.932s] [INFO] WildFly: Blacktie Subsystem ....................... SUCCESS [3.568s] [INFO] WildFly: Blacktie Feature Pack .................... SUCCESS [0.725s] [INFO] WildFly: Blacktie Subsystem Build ................. FAILURE [4.928s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 10.345s [INFO] Finished at: Wed Oct 21 16:40:05 BST 2015 [INFO] Final Memory: 51M/234M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR1:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-pro visioning-maven-plugin:1.1.0.CR1:build failed: java.lang.RuntimeException: java.lang.NullPointerException -> [Help 1] {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 21 11:49:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Oct 2015 11:49:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2540) Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120617#comment-13120617 ] Tom Jenkinson commented on JBTM-2540: ------------------------------------- I pushed a commit to align with current build tools and wildfly core but this hasn't helped: https://github.com/jbosstm/narayana/commit/ada5603d9f2e758b402a3f351a32e95d3bd23c3b I pushed it anyway because it needs to be done during the upgrade and it didn't make it worse... {code} [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR2:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR2:build failed: java.lang.RuntimeException: java.lang.NullPointerException {code} > Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT > ------------------------------------------------------------------- > > Key: JBTM-2540 > URL: https://issues.jboss.org/browse/JBTM-2540 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Build System > Affects Versions: 5.2.6.Final > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] WildFly: Blacktie Subsystem Parent ................ SUCCESS [0.932s] > [INFO] WildFly: Blacktie Subsystem ....................... SUCCESS [3.568s] > [INFO] WildFly: Blacktie Feature Pack .................... SUCCESS [0.725s] > [INFO] WildFly: Blacktie Subsystem Build ................. FAILURE [4.928s] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 10.345s > [INFO] Finished at: Wed Oct 21 16:40:05 BST 2015 > [INFO] Final Memory: 51M/234M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR1:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-pro > visioning-maven-plugin:1.1.0.CR1:build failed: java.lang.RuntimeException: java.lang.NullPointerException -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 01:33:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 22 Oct 2015 01:33:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2540) Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120771#comment-13120771 ] Amos Feng commented on JBTM-2540: --------------------------------- Thanks Tom for looking into it and I think it would be some configuration changes. > Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT > ------------------------------------------------------------------- > > Key: JBTM-2540 > URL: https://issues.jboss.org/browse/JBTM-2540 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Build System > Affects Versions: 5.2.6.Final > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] WildFly: Blacktie Subsystem Parent ................ SUCCESS [0.932s] > [INFO] WildFly: Blacktie Subsystem ....................... SUCCESS [3.568s] > [INFO] WildFly: Blacktie Feature Pack .................... SUCCESS [0.725s] > [INFO] WildFly: Blacktie Subsystem Build ................. FAILURE [4.928s] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 10.345s > [INFO] Finished at: Wed Oct 21 16:40:05 BST 2015 > [INFO] Final Memory: 51M/234M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR1:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-pro > visioning-maven-plugin:1.1.0.CR1:build failed: java.lang.RuntimeException: java.lang.NullPointerException -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 02:42:00 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 22 Oct 2015 02:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2540) Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2540: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/930 > Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT > ------------------------------------------------------------------- > > Key: JBTM-2540 > URL: https://issues.jboss.org/browse/JBTM-2540 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Build System > Affects Versions: 5.2.6.Final > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] WildFly: Blacktie Subsystem Parent ................ SUCCESS [0.932s] > [INFO] WildFly: Blacktie Subsystem ....................... SUCCESS [3.568s] > [INFO] WildFly: Blacktie Feature Pack .................... SUCCESS [0.725s] > [INFO] WildFly: Blacktie Subsystem Build ................. FAILURE [4.928s] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 10.345s > [INFO] Finished at: Wed Oct 21 16:40:05 BST 2015 > [INFO] Final Memory: 51M/234M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR1:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-pro > visioning-maven-plugin:1.1.0.CR1:build failed: java.lang.RuntimeException: java.lang.NullPointerException -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 22 11:11:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 22 Oct 2015 11:11:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2540) Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2540: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT > ------------------------------------------------------------------- > > Key: JBTM-2540 > URL: https://issues.jboss.org/browse/JBTM-2540 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Build System > Affects Versions: 5.2.6.Final > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] WildFly: Blacktie Subsystem Parent ................ SUCCESS [0.932s] > [INFO] WildFly: Blacktie Subsystem ....................... SUCCESS [3.568s] > [INFO] WildFly: Blacktie Feature Pack .................... SUCCESS [0.725s] > [INFO] WildFly: Blacktie Subsystem Build ................. FAILURE [4.928s] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 10.345s > [INFO] Finished at: Wed Oct 21 16:40:05 BST 2015 > [INFO] Final Memory: 51M/234M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR1:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-pro > visioning-maven-plugin:1.1.0.CR1:build failed: java.lang.RuntimeException: java.lang.NullPointerException -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 06:32:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ond=C5=99ej_Chaloupka_=28JIRA=29?=) Date: Fri, 23 Oct 2015 06:32:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2541) Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store In-Reply-To: References: Message-ID: Ond?ej Chaloupka created JBTM-2541: -------------------------------------- Summary: Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store Key: JBTM-2541 URL: https://issues.jboss.org/browse/JBTM-2541 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 5.2.5.Final Reporter: Ond?ej Chaloupka Priority: Minor Currently the Narayna could use journal store which is implemented by ActiveMQ journaling. But after activation the narayana trace log contains messages like {{2015-10-23 12:24:40,735 TRACE [com.arjuna.ats.arjuna] HornetqObjectStore.start()}}. If HornetQ object store is not really used the log messages should be changed to correspond to current state. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 06:32:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ond=C5=99ej_Chaloupka_=28JIRA=29?=) Date: Fri, 23 Oct 2015 06:32:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2541) Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ond?ej Chaloupka updated JBTM-2541: ----------------------------------- Description: Currently the Narayna could use journal store which is implemented by ActiveMQ journaling. But after activation the narayana trace log contains messages like {{2015-10-23 12:24:40,735 TRACE [com.arjuna.ats.arjuna] HornetqObjectStore.start()}}. If HornetQ object store is not really used the log messages should be changed to correspond to the state. was: Currently the Narayna could use journal store which is implemented by ActiveMQ journaling. But after activation the narayana trace log contains messages like {{2015-10-23 12:24:40,735 TRACE [com.arjuna.ats.arjuna] HornetqObjectStore.start()}}. If HornetQ object store is not really used the log messages should be changed to correspond to current state. > Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store > -------------------------------------------------------------------------------------------- > > Key: JBTM-2541 > URL: https://issues.jboss.org/browse/JBTM-2541 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.5.Final > Reporter: Ond?ej Chaloupka > Priority: Minor > > Currently the Narayna could use journal store which is implemented by ActiveMQ journaling. But after activation the narayana trace log contains messages like > {{2015-10-23 12:24:40,735 TRACE [com.arjuna.ats.arjuna] HornetqObjectStore.start()}}. > If HornetQ object store is not really used the log messages should be changed to correspond to the state. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 06:33:00 2015 From: issues at jboss.org (=?UTF-8?Q?Ond=C5=99ej_Chaloupka_=28JIRA=29?=) Date: Fri, 23 Oct 2015 06:33:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2541) Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ond?ej Chaloupka reassigned JBTM-2541: -------------------------------------- Assignee: Amos Feng > Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store > -------------------------------------------------------------------------------------------- > > Key: JBTM-2541 > URL: https://issues.jboss.org/browse/JBTM-2541 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.5.Final > Reporter: Ond?ej Chaloupka > Assignee: Amos Feng > Priority: Minor > > Currently the Narayna could use journal store which is implemented by ActiveMQ journaling. But after activation the narayana trace log contains messages like > {{2015-10-23 12:24:40,735 TRACE [com.arjuna.ats.arjuna] HornetqObjectStore.start()}}. > If HornetQ object store is not really used the log messages should be changed to correspond to the state. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 23 06:42:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 23 Oct 2015 06:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2542) Migrate performance tests to the performance repo In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2542: -------------------------------------- Summary: 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 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 Fri Oct 23 17:39:00 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Fri, 23 Oct 2015 17:39:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2543) Figure 2.3 in Recovery Guide too large In-Reply-To: References: Message-ID: Mark Little created JBTM-2543: --------------------------------- Summary: Figure 2.3 in Recovery Guide too large Key: JBTM-2543 URL: https://issues.jboss.org/browse/JBTM-2543 Project: JBoss Transaction Manager Issue Type: Bug Components: Documentation Affects Versions: 5.2.6.Final Reporter: Mark Little Take a look at the guide Tom references ... https://developer.jboss.org/message/944517?et=watches.email.thread Figure 2.3 is huge :) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 06:15:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 26 Oct 2015 06:15:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2543) Figure 2.3 in Recovery Guide too large In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2543. --------------------------------- Fix Version/s: 5.next Resolution: Done Wow - it was big! Fixed here: https://github.com/jbosstm/documentation/commit/6fe01e226eaf35ed2910fef54be775a9c6263a9c > Figure 2.3 in Recovery Guide too large > -------------------------------------- > > Key: JBTM-2543 > URL: https://issues.jboss.org/browse/JBTM-2543 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Affects Versions: 5.2.6.Final > Reporter: Mark Little > Fix For: 5.next > > > Take a look at the guide Tom references ... > https://developer.jboss.org/message/944517?et=watches.email.thread > Figure 2.3 is huge :) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 06:53:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 26 Oct 2015 06:53:00 -0400 (EDT) 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 ] Gytis Trikleris reassigned JBTM-2534: ------------------------------------- Assignee: Michael Musgrove (was: Gytis Trikleris) > 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 Mon Oct 26 08:18:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 26 Oct 2015 08:18:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1860) Please document TransactionStatusManager scanner. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121905#comment-13121905 ] Tom Jenkinson commented on JBTM-1860: ------------------------------------- AtomicActionExpiryScanner is described here: http://narayana.io/docs/product/index.html#d0e1211 Please consider filing an issue on the product docs if the documentation is missing from there. > Please document TransactionStatusManager scanner. > ------------------------------------------------- > > Key: JBTM-1860 > URL: https://issues.jboss.org/browse/JBTM-1860 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Environment: JBoss EAP 5.x and 6.x > Reporter: Tom Ross > Assignee: Tom Jenkinson > > JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them. > Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 08:18:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 26 Oct 2015 08:18:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1860) Please document TransactionStatusManager scanner. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1860. ------------------------------- Fix Version/s: (was: 5.next) Resolution: Rejected > Please document TransactionStatusManager scanner. > ------------------------------------------------- > > Key: JBTM-1860 > URL: https://issues.jboss.org/browse/JBTM-1860 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Environment: JBoss EAP 5.x and 6.x > Reporter: Tom Ross > Assignee: Tom Jenkinson > > JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them. > Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 26 11:15:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 26 Oct 2015 11:15:01 -0400 (EDT) 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: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/932 The pull request is to demote some of the log messages. To actually change the format of the logger users can configure the JDK logger however they would normally do so. For example I found this useful: -Djava.util.logging.SimpleFormatter.format="%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS %4$s %5$s%6$s%n" Alternatively they could replace the entire default JAVA_HOME/lib/logging.properties file with java.util.logging.config.file. I am reluctant to make our scripts do the former as it would seem to override their system defaults. > 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 Tue Oct 27 06:22:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 27 Oct 2015 06:22:00 -0400 (EDT) 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:comment-tabpanel&focusedCommentId=13121997#comment-13121997 ] Tom Jenkinson edited comment on JBTM-2318 at 10/27/15 6:21 AM: --------------------------------------------------------------- The pull request is to demote some of the log messages. To actually change the format of the logger users can configure the JDK logger however they would normally do so. For example I found this useful: {code} -Djava.util.logging.SimpleFormatter.format="%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS %4$s %5$s%6$s%n" {code} Alternatively they could replace the entire default JAVA_HOME/lib/logging.properties file with java.util.logging.config.file. I am reluctant to make our scripts do the former as it would seem to override their system defaults. was (Author: tomjenkinson): The pull request is to demote some of the log messages. To actually change the format of the logger users can configure the JDK logger however they would normally do so. For example I found this useful: -Djava.util.logging.SimpleFormatter.format="%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS %4$s %5$s%6$s%n" Alternatively they could replace the entire default JAVA_HOME/lib/logging.properties file with java.util.logging.config.file. I am reluctant to make our scripts do the former as it would seem to override their system defaults. > 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 Tue Oct 27 06:41:00 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 27 Oct 2015 06:41:00 -0400 (EDT) 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:comment-tabpanel&focusedCommentId=13122330#comment-13122330 ] Michael Musgrove commented on JBTM-2534: ---------------------------------------- I debugged CrashRecovery05_1_Test01 but all the failures seem to be similar. Client starts a txn, calls a server which enlists 2 resources one of which crashes during 2PC. During recovery the resource is recovered. BasicAciont#phase2Commit calls BasicAction#doForget after successfully committing the resource. When running with JacORB the resource CORBA object is destroyed after commit so the forget call is not processed (BasicAction#doForget processing receives org.omg.CORBA.OBJECT_NOT_EXIST). When running with JdkORB the resource CORBA object is not destroyed after commit so the forget call is processed. The actual test maintains a trace of the last call the resource processed which should be commit. But since the forget call reaches the resource in the JdkORB case the trace is unexpected. My interpretation of the problem is that the resource trace in ResourceImpl02#forget, for example, in the default case should not be updating the resource trace - ie the resource test code is wrong. JacORB only works because the remote resource corba object never received the forget() call. > 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 Oct 27 06:49:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 27 Oct 2015 06:49:00 -0400 (EDT) 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:comment-tabpanel&focusedCommentId=13122334#comment-13122334 ] Tom Jenkinson commented on JBTM-2534: ------------------------------------- I agree - my understanding is Resource should be free to cleanup after commit unless it was a heuristic. > 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 Oct 27 08:44:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 27 Oct 2015 08:44:00 -0400 (EDT) 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:comment-tabpanel&focusedCommentId=13122404#comment-13122404 ] Tom Jenkinson commented on JBTM-2532: ------------------------------------- Did you put back a commit for the unit tests for now? > 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 Tue Oct 27 09:02:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 27 Oct 2015 09:02:00 -0400 (EDT) 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:comment-tabpanel&focusedCommentId=13122422#comment-13122422 ] Gytis Trikleris commented on JBTM-2532: --------------------------------------- I have not, I wanted to put them all together. But I'll put it in since you've asked. > 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 Tue Oct 27 12:33:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 27 Oct 2015 12:33:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2544) RTS inbound bridge recovery does not work with JTS In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2544: ------------------------------------- Summary: 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 Oct 27 12:36:00 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 27 Oct 2015 12:36:00 -0400 (EDT) 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 ] Gytis Trikleris updated JBTM-2544: ---------------------------------- Steps to Reproduce: 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 Thu Oct 29 05:43:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 29 Oct 2015 05:43:00 -0400 (EDT) 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: Tom Jenkinson created JBTM-2545: ----------------------------------- Summary: 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 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 05:45:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 29 Oct 2015 05:45:00 -0400 (EDT) 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 updated JBTM-2545: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/933 > 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 > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 05:47:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 29 Oct 2015 05:47:00 -0400 (EDT) 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 updated JBTM-2545: -------------------------------- Description: 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. was: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. > 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 > 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 Oct 29 07:48:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 29 Oct 2015 07:48:00 -0400 (EDT) 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 reassigned JBTM-2545: ----------------------------------- Assignee: Tom Jenkinson > 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 Oct 29 10:00:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 29 Oct 2015 10:00:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2546) Change support of MariaDB JBDC object store to 1.2.3 In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2546: ----------------------------------- Summary: Change support of MariaDB JBDC object store to 1.2.3 Key: JBTM-2546 URL: https://issues.jboss.org/browse/JBTM-2546 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Transaction Core Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next 1.2.2: https://github.com/MariaDB/mariadb-connector-j/blob/1.2.2/src/main/java/org/mariadb/jdbc/MySQLDatabaseMetaData.java#L491 1.2.3: https://github.com/MariaDB/mariadb-connector-j/blob/1.2.3/src/main/java/org/mariadb/jdbc/MySQLDatabaseMetaData.java#L64 The algorithm we use changes "-" to "_", trims after the space and lower cases: https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCStore.java#L234 The change was part of https://mariadb.atlassian.net/browse/CONJ-192 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 10:07:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 29 Oct 2015 10:07:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2546) Change support of MariaDB JBDC object store to 1.2.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2546: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/934 > Change support of MariaDB JBDC object store to 1.2.3 > ---------------------------------------------------- > > Key: JBTM-2546 > URL: https://issues.jboss.org/browse/JBTM-2546 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > 1.2.2: https://github.com/MariaDB/mariadb-connector-j/blob/1.2.2/src/main/java/org/mariadb/jdbc/MySQLDatabaseMetaData.java#L491 > 1.2.3: https://github.com/MariaDB/mariadb-connector-j/blob/1.2.3/src/main/java/org/mariadb/jdbc/MySQLDatabaseMetaData.java#L64 > The algorithm we use changes "-" to "_", trims after the space and lower cases: > https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCStore.java#L234 > The change was part of https://mariadb.atlassian.net/browse/CONJ-192 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 29 10:07:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 29 Oct 2015 10:07:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2546) Change support of MariaDB JBDC object store to 1.2.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2546: -------------------------------- Priority: Blocker (was: Major) > Change support of MariaDB JBDC object store to 1.2.3 > ---------------------------------------------------- > > Key: JBTM-2546 > URL: https://issues.jboss.org/browse/JBTM-2546 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > 1.2.2: https://github.com/MariaDB/mariadb-connector-j/blob/1.2.2/src/main/java/org/mariadb/jdbc/MySQLDatabaseMetaData.java#L491 > 1.2.3: https://github.com/MariaDB/mariadb-connector-j/blob/1.2.3/src/main/java/org/mariadb/jdbc/MySQLDatabaseMetaData.java#L64 > The algorithm we use changes "-" to "_", trims after the space and lower cases: > https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCStore.java#L234 > The change was part of https://mariadb.atlassian.net/browse/CONJ-192 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 07:10:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:10:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2546) Change support of MariaDB JBDC object store to 1.2.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2546. ------------------------------- Resolution: Done > Change support of MariaDB JBDC object store to 1.2.3 > ---------------------------------------------------- > > Key: JBTM-2546 > URL: https://issues.jboss.org/browse/JBTM-2546 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > 1.2.2: https://github.com/MariaDB/mariadb-connector-j/blob/1.2.2/src/main/java/org/mariadb/jdbc/MySQLDatabaseMetaData.java#L491 > 1.2.3: https://github.com/MariaDB/mariadb-connector-j/blob/1.2.3/src/main/java/org/mariadb/jdbc/MySQLDatabaseMetaData.java#L64 > The algorithm we use changes "-" to "_", trims after the space and lower cases: > https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCStore.java#L234 > The change was part of https://mariadb.atlassian.net/browse/CONJ-192 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 07:12:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:12:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2540) Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2540. ------------------------------- > Can't build BlackTie subsystem since update to WFLY 10 CR4-SNAPSHOT > ------------------------------------------------------------------- > > Key: JBTM-2540 > URL: https://issues.jboss.org/browse/JBTM-2540 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Build System > Affects Versions: 5.2.6.Final > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.2.7.Final > > > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] WildFly: Blacktie Subsystem Parent ................ SUCCESS [0.932s] > [INFO] WildFly: Blacktie Subsystem ....................... SUCCESS [3.568s] > [INFO] WildFly: Blacktie Feature Pack .................... SUCCESS [0.725s] > [INFO] WildFly: Blacktie Subsystem Build ................. FAILURE [4.928s] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 10.345s > [INFO] Finished at: Wed Oct 21 16:40:05 BST 2015 > [INFO] Final Memory: 51M/234M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.CR1:build (server-provisioning) on project wildfly-blacktie-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-pro > visioning-maven-plugin:1.1.0.CR1:build failed: java.lang.RuntimeException: java.lang.NullPointerException -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 07:12:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:12:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2543) Figure 2.3 in Recovery Guide too large In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2543. ------------------------------- > Figure 2.3 in Recovery Guide too large > -------------------------------------- > > Key: JBTM-2543 > URL: https://issues.jboss.org/browse/JBTM-2543 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Affects Versions: 5.2.6.Final > Reporter: Mark Little > Fix For: 5.2.7.Final > > > Take a look at the guide Tom references ... > https://developer.jboss.org/message/944517?et=watches.email.thread > Figure 2.3 is huge :) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 07:12:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:12:00 -0400 (EDT) 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 updated JBTM-2545: -------------------------------- Fix Version/s: 5.next (was: 5.2.7.Final) > 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 Fri Oct 30 07:12:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:12:00 -0400 (EDT) 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.7.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 Oct 30 07:12:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:12:01 -0400 (EDT) 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 updated JBTM-2538: -------------------------------- Fix Version/s: 5.next (was: 5.2.7.Final) > 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 Oct 30 07:13:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2537) Can't build WFLY on a machine that has only built for IBM Orb 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: -------------------------------- Fix Version/s: 5.next (was: 5.2.7.Final) > Can't build WFLY on a machine that has only built for IBM Orb > ------------------------------------------------------------- > > 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 Oct 30 07:13:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:00 -0400 (EDT) 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 updated JBTM-2534: -------------------------------- Fix Version/s: 5.next (was: 5.2.7.Final) > 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 Oct 30 07:13:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:00 -0400 (EDT) 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 updated JBTM-2532: -------------------------------- Fix Version/s: 5.next (was: 5.2.7.Final) > 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 Oct 30 07:13:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:00 -0400 (EDT) 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.7.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 Oct 30 07:13:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:00 -0400 (EDT) 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 ] Tom Jenkinson updated JBTM-2511: -------------------------------- Fix Version/s: 5.next (was: 5.2.7.Final) > 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 Fri Oct 30 07:13:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:01 -0400 (EDT) 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.7.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 > 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 Oct 30 07:13:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:01 -0400 (EDT) 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.7.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 > 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 Oct 30 07:13:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:01 -0400 (EDT) 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.7.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 Oct 30 07:13:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:01 -0400 (EDT) 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.7.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 > 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 Oct 30 07:13:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:01 -0400 (EDT) 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.7.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 Oct 30 07:13:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:01 -0400 (EDT) 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.7.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 Oct 30 07:13:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:01 -0400 (EDT) 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: -------------------------------- Fix Version/s: 5.next (was: 5.2.7.Final) > 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 Oct 30 07:13:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:01 -0400 (EDT) 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.7.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: Optional > 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 Oct 30 07:13:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:01 -0400 (EDT) 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.7.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 Oct 30 07:13:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:01 -0400 (EDT) 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.7.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 Oct 30 07:13:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:01 -0400 (EDT) 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.7.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 Oct 30 07:13:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:01 -0400 (EDT) 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.7.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 > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 30 07:13:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:13:02 -0400 (EDT) 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.7.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: 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 Oct 30 07:14:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:14:00 -0400 (EDT) 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.7.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 > 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 Oct 30 07:14:00 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 Oct 2015 07:14:00 -0400 (EDT) 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.7.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)