From issues at jboss.org Mon May 2 05:08:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 May 2016 05:08:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2647) Extend compensations BAControler to allow enlistment of handlers by instance In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2647: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Extend compensations BAControler to allow enlistment of handlers by instance > ---------------------------------------------------------------------------- > > Key: JBTM-2647 > URL: https://issues.jboss.org/browse/JBTM-2647 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently BAControler allows enlistment of handler only by class. It later creates instances using those classes when finishing the compensating transaction. Because of that it should be easy to allow enlisting of instances. This would allow using labdas when implementing handlers. Also instance could carry some extra information needed to compensate the transaction. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 2 05:08:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 May 2016 05:08:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2641) Add localisation to JMS module warnings In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2641: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add localisation to JMS module warnings > --------------------------------------- > > Key: JBTM-2641 > URL: https://issues.jboss.org/browse/JBTM-2641 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Warning messages in JMS modules should be localised same as other modules in ArjunaJTA. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 2 05:39:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 May 2016 05:39:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2587) DistributedTestRemote compensations test hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2587. --------------------------------- Resolution: Incomplete Description > DistributedTestRemote compensations test hang > --------------------------------------------- > > Key: JBTM-2587 > URL: https://issues.jboss.org/browse/JBTM-2587 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.2.9.Final > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > > CI test hang (http://albany.eng.hst.ams2.redhat.com/job/narayana/PROFILE=XTS,jdk=jdk8.latest,label=linux/1007/): > testSimple(org.jboss.narayana.compensations.functional.distributed.DistributedTestRemote) Time elapsed: 0.806 sec <<< ERROR! > com.arjuna.wst.SystemException: ARJUNA045061: No termination context! > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.getTerminationCoordinator(UserBusinessActivityImple.java:390) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:153) > at org.jboss.narayana.compensations.impl.remote.RemoteBAControler.closeBusinessActivity(RemoteBAControler.java:38) > at org.jboss.narayana.compensations.impl.remote.RemoteBAControler.completeBusinessActivity(RemoteBAControler.java:59) > at org.jboss.narayana.compensations.impl.CompensationInterceptorBase.invokeInOurTx(CompensationInterceptorBase.java:62) > at org.jboss.narayana.compensations.impl.CompensationInterceptorRequired.intercept(CompensationInterceptorRequired.java:45) > 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:497) > 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 org.jboss.narayana.compensations.functional.distributed.TestServiceClient$Proxy$_$$_WeldSubclass.saveData(Unknown Source) > at org.jboss.narayana.compensations.functional.distributed.DistributedTestRemote.testSimple(DistributedTestRemote.java:101) > I was unable to obtain jstack data because of the following error: > java-jarslave.jar[hudson at sansa ~]$ jstack 18610 > 18610: Unable to open socket file: target process not responding or HotSpot VM not loaded > The -F option can be used when the target process is not responding > [hudson at sansa ~]$ > [hudson at sansa ~]$ > [hudson at sansa ~]$ jstack -F 18610 > Attaching to process ID 18610, please wait... > Exception in thread "main" java.lang.reflect.InvocationTargetException > 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 sun.tools.jstack.JStack.runJStackTool(JStack.java:140) > at sun.tools.jstack.JStack.main(JStack.java:106) > Caused by: java.lang.InternalError: void* type hasn't been seen when parsing int* > at sun.jvm.hotspot.HotSpotTypeDataBase.recursiveCreateBasicPointerType(HotSpotTypeDataBase.java:687) > at sun.jvm.hotspot.HotSpotTypeDataBase.lookupType(HotSpotTypeDataBase.java:131) > at sun.jvm.hotspot.HotSpotTypeDataBase.lookupOrCreateClass(HotSpotTypeDataBase.java:597) > at sun.jvm.hotspot.HotSpotTypeDataBase.createType(HotSpotTypeDataBase.java:717) > at sun.jvm.hotspot.HotSpotTypeDataBase.readVMTypes(HotSpotTypeDataBase.java:188) > at sun.jvm.hotspot.HotSpotTypeDataBase.(HotSpotTypeDataBase.java:86) > at sun.jvm.hotspot.HotSpotAgent.setupVM(HotSpotAgent.java:395) > at sun.jvm.hotspot.HotSpotAgent.go(HotSpotAgent.java:305) > at sun.jvm.hotspot.HotSpotAgent.attach(HotSpotAgent.java:140) > at sun.jvm.hotspot.tools.Tool.start(Tool.java:185) > at sun.jvm.hotspot.tools.Tool.execute(Tool.java:118) > at sun.jvm.hotspot.tools.JStack.main(JStack.java:92) > ... 6 more -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 2 05:42:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 May 2016 05:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2585) Configure CMR test programatically In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris reassigned JBTM-2585: ------------------------------------- Assignee: (was: Gytis Trikleris) > Configure CMR test programatically > ---------------------------------- > > Key: JBTM-2585 > URL: https://issues.jboss.org/browse/JBTM-2585 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA, Testing > Reporter: Gytis Trikleris > Priority: Minor > > I think we should add CMR configuration to standalon-full.xml programatically rather than copying standalone-cmr.xml manually in order to run CMRIntegrationTest. It needs to be kept up to date all the time. Also, it's a bit misleading when running the test for the first time. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 2 05:54:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 May 2016 05:54:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2650) Remove typo from BAControler interface and its implementations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #1005 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Remove typo from BAControler interface and its implementations > -------------------------------------------------------------- > > Key: JBTM-2650 > URL: https://issues.jboss.org/browse/JBTM-2650 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Fix typos in BAControler, LocalBAControler, and RemoteBAControler names. Also variables when those classes are used also have typos. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 2 05:58:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 May 2016 05:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2635) TXBridge OutboundBasicTests hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2635. --------------------------------- Resolution: Won't Fix Hanging on Arquillian shutdown, doesn't look like an issue with the product. > TXBridge OutboundBasicTests hanging > ----------------------------------- > > Key: JBTM-2635 > URL: https://issues.jboss.org/browse/JBTM-2635 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.3.1.Final > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > > Thread dump > {code} > Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode): > "Thread-16" #41 prio=5 os_prio=0 tid=0x0000000009fb6000 nid=0x6f30 runnable [0x00002b5477ed7000] > java.lang.Thread.State: RUNNABLE > at java.io.FileInputStream.readBytes(Native Method) > at java.io.FileInputStream.read(FileInputStream.java:255) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:284) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x00000000a46321e0> (a java.lang.UNIXProcess$ProcessPipeInputStream) > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) > - locked <0x00000000a4632238> (a java.io.InputStreamReader) > at java.io.InputStreamReader.read(InputStreamReader.java:184) > at java.io.BufferedReader.fill(BufferedReader.java:161) > at java.io.BufferedReader.readLine(BufferedReader.java:324) > - locked <0x00000000a4632238> (a java.io.InputStreamReader) > at java.io.BufferedReader.readLine(BufferedReader.java:389) > at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:66) > "Thread-15" #40 prio=5 os_prio=0 tid=0x0000000009f86000 nid=0x6f2d runnable [0x00002b5477dd6000] > java.lang.Thread.State: RUNNABLE > at java.io.FileInputStream.readBytes(Native Method) > at java.io.FileInputStream.read(FileInputStream.java:255) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:284) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x00000000a46782f8> (a java.lang.UNIXProcess$ProcessPipeInputStream) > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) > - locked <0x00000000a4827108> (a java.io.InputStreamReader) > at java.io.InputStreamReader.read(InputStreamReader.java:184) > at java.io.BufferedReader.fill(BufferedReader.java:161) > at java.io.BufferedReader.readLine(BufferedReader.java:324) > - locked <0x00000000a4827108> (a java.io.InputStreamReader) > at java.io.BufferedReader.readLine(BufferedReader.java:389) > at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:66) > "ThreadedStreamConsumer" #39 prio=5 os_prio=0 tid=0x000000000a028000 nid=0x6f2b waiting on condition [0x00002b5477cd5000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a4678188> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:68) > at java.lang.Thread.run(Thread.java:745) > "pool-1-thread-1" #22 prio=5 os_prio=0 tid=0x000000000b4a2000 nid=0x4ea3 in Object.wait() [0x00002b5477bd4000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000a46782b8> (a java.lang.UNIXProcess) > at java.lang.Object.wait(Object.java:502) > at java.lang.UNIXProcess.waitFor(UNIXProcess.java:396) > - locked <0x00000000a46782b8> (a java.lang.UNIXProcess) > at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.CommandLineUtils$1.call(CommandLineUtils.java:202) > at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:141) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:471) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:380) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$300(ForkStarter.java:88) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:315) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:306) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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) > "resolver-4" #21 daemon prio=5 os_prio=0 tid=0x000000000bc90000 nid=0x4ea2 waiting on condition [0x00002b5477a3e000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a856fb90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "resolver-3" #20 daemon prio=5 os_prio=0 tid=0x0000000009fab800 nid=0x4ea1 waiting on condition [0x00002b547793d000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a856fb90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "resolver-2" #19 daemon prio=5 os_prio=0 tid=0x0000000009f0a800 nid=0x4ea0 waiting on condition [0x00002b547711b000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a856fb90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "resolver-1" #18 daemon prio=5 os_prio=0 tid=0x000000000a40f000 nid=0x4e9f waiting on condition [0x00002b547701a000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a856fb90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "process reaper" #11 daemon prio=10 os_prio=0 tid=0x000000000a9c8000 nid=0x4e94 runnable [0x00002b5476f19000] > java.lang.Thread.State: RUNNABLE > at java.lang.UNIXProcess.waitForProcessExit(Native Method) > at java.lang.UNIXProcess.lambda$initStreams$273(UNIXProcess.java:290) > at java.lang.UNIXProcess$$Lambda$7/594570680.run(Unknown Source) > 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) > "Service Thread" #8 daemon prio=9 os_prio=0 tid=0x0000000009431800 nid=0x4e90 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C1 CompilerThread1" #7 daemon prio=9 os_prio=0 tid=0x000000000942a800 nid=0x4e8f waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread0" #6 daemon prio=9 os_prio=0 tid=0x00000000093dc000 nid=0x4e8e waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Signal Dispatcher" #5 daemon prio=9 os_prio=0 tid=0x00000000093d9800 nid=0x4e8d runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Surrogate Locker Thread (Concurrent GC)" #4 daemon prio=9 os_prio=0 tid=0x00000000093d8800 nid=0x4e8c waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Finalizer" #3 daemon prio=8 os_prio=0 tid=0x000000000939a000 nid=0x4e8b in Object.wait() [0x00002b547226a000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000a80443d0> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) > - locked <0x00000000a80443d0> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) > at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209) > "Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x0000000009398000 nid=0x4e8a in Object.wait() [0x00002b5472169000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000a803c3d0> (a java.lang.ref.Reference$Lock) > at java.lang.Object.wait(Object.java:502) > at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:157) > - locked <0x00000000a803c3d0> (a java.lang.ref.Reference$Lock) > "main" #1 prio=5 os_prio=0 tid=0x00000000092ea800 nid=0x4e86 waiting on condition [0x00002b545d802000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a9237408> (a java.util.concurrent.FutureTask) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:429) > at java.util.concurrent.FutureTask.get(FutureTask.java:191) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:327) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:178) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:990) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:824) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:722) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > 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:497) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > "VM Thread" os_prio=0 tid=0x0000000009393000 nid=0x4e89 runnable > "Gang worker#0 (Parallel GC Threads)" os_prio=0 tid=0x00000000092fb800 nid=0x4e87 runnable > "Concurrent Mark-Sweep GC Thread" os_prio=0 tid=0x000000000931e800 nid=0x4e88 runnable > "VM Periodic Task Thread" os_prio=0 tid=0x0000000009434800 nid=0x4e91 waiting on condition > 2016-03-07 10:39:06 > Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode): > "Remoting "endpoint" task-9" #187 daemon prio=5 os_prio=0 tid=0x00000000133d5800 nid=0x73ce waiting on condition [0x00002aeb308f7000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-8" #186 daemon prio=5 os_prio=0 tid=0x000000001372c800 nid=0x73cd waiting on condition [0x00002aeb2f2e3000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "management-client-thread 5-2" #184 prio=5 os_prio=0 tid=0x000000001366d000 nid=0x73a4 waiting on condition [0x00002aeb2eedf000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c207d548> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > "Remoting "endpoint" task-7" #181 daemon prio=5 os_prio=0 tid=0x0000000013329800 nid=0x73a2 waiting on condition [0x00002aeb2feef000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-6" #180 daemon prio=5 os_prio=0 tid=0x0000000013329000 nid=0x73a0 waiting on condition [0x00002aeb2e47f000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-5" #179 daemon prio=5 os_prio=0 tid=0x0000000013328000 nid=0x739f waiting on condition [0x00002aeb2fff0000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-4" #178 daemon prio=5 os_prio=0 tid=0x0000000013327800 nid=0x739e waiting on condition [0x00002aeb31602000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-3" #177 daemon prio=5 os_prio=0 tid=0x0000000013326800 nid=0x739d waiting on condition [0x00002aeb2e989000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-2" #176 daemon prio=5 os_prio=0 tid=0x000000001328b000 nid=0x739c waiting on condition [0x00002aeb307f6000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-1" #175 daemon prio=5 os_prio=0 tid=0x000000001328a000 nid=0x739b waiting on condition [0x00002aeb2f0e1000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" I/O-1" #174 daemon prio=5 os_prio=0 tid=0x000000001328d000 nid=0x739a runnable [0x00002aeb2f7e8000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86) > - locked <0x00000000c20c0428> (a sun.nio.ch.Util$2) > - locked <0x00000000c20c0418> (a java.util.Collections$UnmodifiableSet) > - locked <0x00000000c20c0300> (a sun.nio.ch.EPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:502) > "management-client-thread 5-1" #173 prio=5 os_prio=0 tid=0x000000001328c000 nid=0x7397 waiting on condition [0x00002aeb305f4000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c207d548> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > "Remoting "management-client" task-16" #172 prio=5 os_prio=0 tid=0x000000001339c000 nid=0x738d waiting on condition [0x00002aeb2f6e7000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-15" #171 prio=5 os_prio=0 tid=0x000000001339d800 nid=0x738c waiting on condition [0x00002aeb306f5000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-14" #170 prio=5 os_prio=0 tid=0x0000000013e3c800 nid=0x738a waiting on condition [0x00002aeb2f8e9000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-13" #169 prio=5 os_prio=0 tid=0x0000000013441000 nid=0x7389 waiting on condition [0x00002aeb2f3e4000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-12" #168 prio=5 os_prio=0 tid=0x0000000014229800 nid=0x7388 waiting on condition [0x00002aeb2f5e6000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-11" #167 prio=5 os_prio=0 tid=0x0000000013a53800 nid=0x7387 waiting on condition [0x00002aeb302f1000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-10" #166 prio=5 os_prio=0 tid=0x0000000013472800 nid=0x7386 waiting on condition [0x00002aeb2fdee000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-9" #165 prio=5 os_prio=0 tid=0x00000000134a9000 nid=0x7383 waiting on condition [0x00002aeb2fbec000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-8" #164 prio=5 os_prio=0 tid=0x00000000131dc000 nid=0x737f waiting on condition [0x00002aeb2f1e2000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-7" #163 prio=5 os_prio=0 tid=0x0000000013474800 nid=0x737a waiting on condition [0x00002aeb31703000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-6" #162 prio=5 os_prio=0 tid=0x0000000013b1b800 nid=0x7377 waiting on condition [0x00002aeb30af9000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-5" #161 prio=5 os_prio=0 tid=0x000000001339e800 nid=0x7370 waiting on condition [0x00002aeb2fced000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-4" #160 prio=5 os_prio=0 tid=0x0000000013e3a000 nid=0x736a waiting on condition [0x00002aeb2f9ea000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-3" #159 prio=5 os_prio=0 tid=0x0000000014228000 nid=0x735f waiting on condition [0x00002aeb2faeb000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-2" #158 prio=5 os_prio=0 tid=0x0000000013250000 nid=0x735c waiting on condition [0x00002aeb2efe0000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-1" #157 prio=5 os_prio=0 tid=0x0000000013516000 nid=0x735a waiting on condition [0x00002aeb309f8000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" I/O-1" #156 prio=5 os_prio=0 tid=0x0000000013344000 nid=0x72f5 runnable [0x00002aeb2f4e5000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86) > - locked <0x00000000c2082260> (a sun.nio.ch.Util$2) > - locked <0x00000000c2082250> (a java.util.Collections$UnmodifiableSet) > - locked <0x00000000c2082138> (a sun.nio.ch.EPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:502) > "RMI Scheduler(0)" #46 daemon prio=5 os_prio=0 tid=0x0000000012e95000 nid=0x7003 waiting on condition [0x00002aeb30ffe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c1e599c0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1081) > at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "GC Daemon" #44 daemon prio=2 os_prio=0 tid=0x000000001311c000 nid=0x6ff2 in Object.wait() [0x00002aeb30dfc000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at sun.misc.GC$Daemon.run(GC.java:117) > - locked <0x00000000c1f87830> (a sun.misc.GC$LatencyLock) > "RMI Reaper" #43 prio=5 os_prio=0 tid=0x0000000013119800 nid=0x6ff1 in Object.wait() [0x00002aeb30cfb000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000c1e3f620> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) > - locked <0x00000000c1e3f620> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) > at sun.rmi.transport.ObjectTable$Reaper.run(ObjectTable.java:351) > at java.lang.Thread.run(Thread.java:745) > "RMI TCP Accept-0" #42 daemon prio=5 os_prio=0 tid=0x0000000013117800 nid=0x6ff0 runnable [0x00002aeb30bfa000] > java.lang.Thread.State: RUNNABLE > at java.net.PlainSocketImpl.socketAccept(Native Method) > at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) > at java.net.ServerSocket.implAccept(ServerSocket.java:545) > at java.net.ServerSocket.accept(ServerSocket.java:513) > at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:400) > at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:372) > at java.lang.Thread.run(Thread.java:745) > "process reaper" #10 daemon prio=10 os_prio=0 tid=0x0000000013502800 nid=0x6f3c runnable [0x00002aeb2e37e000] > java.lang.Thread.State: RUNNABLE > at java.lang.UNIXProcess.waitForProcessExit(Native Method) > at java.lang.UNIXProcess.lambda$initStreams$273(UNIXProcess.java:290) > at java.lang.UNIXProcess$$Lambda$7/1233990028.run(Unknown Source) > 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) > "RMI TCP Accept-1199" #9 daemon prio=5 os_prio=0 tid=0x000000001413c800 nid=0x6f39 runnable [0x00002aeb2e10e000] > java.lang.Thread.State: RUNNABLE > at java.net.PlainSocketImpl.socketAccept(Native Method) > at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) > at java.net.ServerSocket.implAccept(ServerSocket.java:545) > at java.net.ServerSocket.accept(ServerSocket.java:513) > at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:400) > at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:372) > at java.lang.Thread.run(Thread.java:745) > "Service Thread" #7 daemon prio=9 os_prio=0 tid=0x0000000012b02000 nid=0x6f37 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C1 CompilerThread1" #6 daemon prio=9 os_prio=0 tid=0x0000000012afb000 nid=0x6f36 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread0" #5 daemon prio=9 os_prio=0 tid=0x0000000012aac800 nid=0x6f35 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Signal Dispatcher" #4 daemon prio=9 os_prio=0 tid=0x0000000012aab000 nid=0x6f34 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Finalizer" #3 daemon prio=8 os_prio=0 tid=0x0000000012a6c800 nid=0x6f33 in Object.wait() [0x00002aeb29f40000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) > - locked <0x00000000c1c25980> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) > at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209) > "Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x0000000012a6a800 nid=0x6f32 in Object.wait() [0x00002aeb29e3f000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.Object.wait(Object.java:502) > at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:157) > - locked <0x00000000c1c25b38> (a java.lang.ref.Reference$Lock) > "main" #1 prio=5 os_prio=0 tid=0x00000000129da000 nid=0x6f2f in Object.wait() [0x00002aeb19032000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.Object.wait(Object.java:502) > at java.lang.UNIXProcess.waitFor(UNIXProcess.java:396) > - locked <0x00000000c207f620> (a java.lang.UNIXProcess) > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.stopInternal(ManagedDeployableContainer.java:275) > at org.jboss.as.arquillian.container.CommonDeployableContainer.stop(CommonDeployableContainer.java:122) > at org.jboss.arquillian.container.impl.ContainerImpl.stop(ContainerImpl.java:217) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$9.perform(ContainerLifecycleController.java:178) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$9.perform(ContainerLifecycleController.java:172) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.stopContainer(ContainerLifecycleController.java:171) > 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:497) > 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.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.stop(ClientContainerController.java:204) > at org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests.tearDown(OutboundBasicTests.java:86) > 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:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) > at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:459) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:80) > 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:497) > 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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > 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:497) > 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.junit.extension.UpdateTestResultBeforeAfter.update(UpdateTestResultBeforeAfter.java:54) > 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:497) > 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.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:122) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:264) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:315) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:72) > 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:497) > 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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > 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:497) > 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.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:311) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > "VM Thread" os_prio=0 tid=0x0000000012a65800 nid=0x6f31 runnable > "VM Periodic Task Thread" os_prio=0 tid=0x0000000012b05800 nid=0x6f38 waiting on condition > JNI global references: 255 > Heap > par new generation total 28864K, used 12323K [0x00000000a2a00000, 0x00000000a4950000, 0x00000000a7d30000) > eden space 25664K, 35% used [0x00000000a2a00000, 0x00000000a32e8dc0, 0x00000000a4310000) > from space 3200K, 100% used [0x00000000a4630000, 0x00000000a4950000, 0x00000000a4950000) > to space 3200K, 0% used [0x00000000a4310000, 0x00000000a4310000, 0x00000000a4630000) > concurrent mark-sweep generation total 64192K, used 30441K [0x00000000a7d30000, 0x00000000abbe0000, 0x0000000100000000) > Metaspace used 26517K, capacity 27428K, committed 27612K, reserved 1073152K > class space used 3152K, capacity 3467K, committed 3556K, reserved 1048576K > JNI global references: 339 > Heap > SUREFIRE-859: def new generation total 29056K, used 109K [0x00000000a2a00000, 0x00000000a4980000, 0x00000000c1c00000) > SUREFIRE-859: eden space 25856K, 0% used [0x00000000a2a00000, 0x00000000a2a1b518, 0x00000000a4340000) > SUREFIRE-859: from space 3200K, 0% used [0x00000000a4340000, 0x00000000a4340000, 0x00000000a4660000) > SUREFIRE-859: to space 3200K, 0% used [0x00000000a4660000, 0x00000000a4660000, 0x00000000a4980000) > SUREFIRE-859: tenured generation total 64192K, used 5286K [0x00000000c1c00000, 0x00000000c5ab0000, 0x0000000100000000) > SUREFIRE-859: the space 64192K, 8% used [0x00000000c1c00000, 0x00000000c2129ab8, 0x00000000c2129c00, 0x00000000c5ab0000) > SUREFIRE-859: Metaspace used 19536K, capacity 19712K, committed 20096K, reserved 1067008K > SUREFIRE-859: class space used 2501K, capacity 2576K, committed 2688K, reserved 1048576K > FATAL: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 31362D30 > hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 31362D30 > 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.$Proxy45.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: java.io.StreamCorruptedException: invalid stream header: 31362D30 > at hudson.remoting.Request.abort(Request.java:299) > at hudson.remoting.Channel.terminate(Channel.java:805) > at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) > Caused by: java.io.StreamCorruptedException: invalid stream header: 31362D30 > at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:806) > at java.io.ObjectInputStream.(ObjectInputStream.java:299) > at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) > at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) > at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 2 22:28:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 2 May 2016 22:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2619: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) > -------------------------------------------------------------------------- > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 2 22:29:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 2 May 2016 22:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2661) Unknown directive cardinality: in Require-Capability In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2661: ---------------------------- Priority: Minor (was: Major) > Unknown directive cardinality: in Require-Capability > ---------------------------------------------------- > > Key: JBTM-2661 > URL: https://issues.jboss.org/browse/JBTM-2661 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > [WARNING] Bundle org.jboss.narayana.osgi:narayana-osgi-jta:bundle:5.3.3.Final-SNAPSHOT : Unknown directive cardinality: in Require-Capability, allowed directives are effective:,resolution:,filter:, and 'x-*'. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 2 22:29:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 2 May 2016 22:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2662) Export org.jboss.tm, has 1, private references [org.jboss.logging] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2662: ---------------------------- Priority: Minor (was: Major) > Export org.jboss.tm, has 1, private references [org.jboss.logging] > -------------------------------------------------------------------- > > Key: JBTM-2662 > URL: https://issues.jboss.org/browse/JBTM-2662 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 2 22:29:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 2 May 2016 22:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2659) narayana-osgi-jta build bundle warings In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2659: ---------------------------- Priority: Minor (was: Major) > narayana-osgi-jta build bundle warings > -------------------------------------- > > Key: JBTM-2659 > URL: https://issues.jboss.org/browse/JBTM-2659 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > There are three warning when building the bundle. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 2 22:29:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 2 May 2016 22:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2660) multiple jars provide the same package:javax/transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2660: ---------------------------- Priority: Minor (was: Major) > multiple jars provide the same package:javax/transaction > -------------------------------------------------------- > > Key: JBTM-2660 > URL: https://issues.jboss.org/browse/JBTM-2660 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > [WARNING] Bundle org.jboss.narayana.osgi:narayana-osgi-jta:bundle:5.3.3.Final-SNAPSHOT : Split package, multiple jars provide the same package:javax/transaction > Use Import/Export Package directive -split-package:=(merge-first|merge-last|error|first) to get rid of this warning > Package found in [Jar:jboss-transaction-api_1.2_spec, Jar:jboss-transaction-api_1.1_spec] > Class path [Jar:., Jar:org.osgi.core, Jar:org.osgi.compendium, Jar:jbosgi-metadata, Jar:jboss-transaction-api_1.2_spec, Jar:jta, Jar:common, Jar:arjuna, Jar:jconsole, Jar:jboss-transaction-spi, Jar:jboss-connector-api_1.5_spec, Jar:jboss-transaction-api_1.1_spec, Jar:narayana-jts-integration, Jar:jboss-logging, Jar:artemis-journal, Jar:artemis-commons, Jar:jboss-logmanager, Jar:netty-all, Jar:commons-beanutils, Jar:commons-collections, Jar:guava, Jar:artemis-native, Jar:spring-tx, Jar:aopalliance, Jar:spring-aop, Jar:spring-asm, Jar:spring-beans, Jar:spring-context, Jar:spring-expression, Jar:spring-core, Jar:commons-logging] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 2 22:32:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 2 May 2016 22:32:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2663) Upgrade to jboss-connector-api_1.7_spec 1.0.0.Final in jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2663: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade to jboss-connector-api_1.7_spec 1.0.0.Final in jboss-transaction-spi > ---------------------------------------------------------------------------- > > Key: JBTM-2663 > URL: https://issues.jboss.org/browse/JBTM-2663 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > It includes the JTA 1.2 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 2 22:42:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 2 May 2016 22:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2657) Missing narayana-osgi-jta artifact with the release profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2657: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Missing narayana-osgi-jta artifact with the release profile > ----------------------------------------------------------- > > Key: JBTM-2657 > URL: https://issues.jboss.org/browse/JBTM-2657 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Amos Feng > Labels: JTA, OSGI > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 3 04:14:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 3 May 2016 04:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2665) Upgrade jboss-transacton-spi dependency to 7.3.2.Final before the next release In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2665: -------------------------------------- Summary: Upgrade jboss-transacton-spi dependency to 7.3.2.Final before the next release Key: JBTM-2665 URL: https://issues.jboss.org/browse/JBTM-2665 Project: JBoss Transaction Manager Issue Type: Task Components: SPI Affects Versions: 5.3.2.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The OSGI build depends on an upgrade of the jboss-transacton-spi (JBTM-2663) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 3 05:06:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 3 May 2016 05:06:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2635) TXBridge OutboundBasicTests hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200080#comment-13200080 ] Tom Jenkinson commented on JBTM-2635: ------------------------------------- [~gytis] - it would be worth reporting upstream to Arq ITS? > TXBridge OutboundBasicTests hanging > ----------------------------------- > > Key: JBTM-2635 > URL: https://issues.jboss.org/browse/JBTM-2635 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.3.1.Final > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > > Thread dump > {code} > Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode): > "Thread-16" #41 prio=5 os_prio=0 tid=0x0000000009fb6000 nid=0x6f30 runnable [0x00002b5477ed7000] > java.lang.Thread.State: RUNNABLE > at java.io.FileInputStream.readBytes(Native Method) > at java.io.FileInputStream.read(FileInputStream.java:255) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:284) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x00000000a46321e0> (a java.lang.UNIXProcess$ProcessPipeInputStream) > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) > - locked <0x00000000a4632238> (a java.io.InputStreamReader) > at java.io.InputStreamReader.read(InputStreamReader.java:184) > at java.io.BufferedReader.fill(BufferedReader.java:161) > at java.io.BufferedReader.readLine(BufferedReader.java:324) > - locked <0x00000000a4632238> (a java.io.InputStreamReader) > at java.io.BufferedReader.readLine(BufferedReader.java:389) > at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:66) > "Thread-15" #40 prio=5 os_prio=0 tid=0x0000000009f86000 nid=0x6f2d runnable [0x00002b5477dd6000] > java.lang.Thread.State: RUNNABLE > at java.io.FileInputStream.readBytes(Native Method) > at java.io.FileInputStream.read(FileInputStream.java:255) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:284) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x00000000a46782f8> (a java.lang.UNIXProcess$ProcessPipeInputStream) > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) > - locked <0x00000000a4827108> (a java.io.InputStreamReader) > at java.io.InputStreamReader.read(InputStreamReader.java:184) > at java.io.BufferedReader.fill(BufferedReader.java:161) > at java.io.BufferedReader.readLine(BufferedReader.java:324) > - locked <0x00000000a4827108> (a java.io.InputStreamReader) > at java.io.BufferedReader.readLine(BufferedReader.java:389) > at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:66) > "ThreadedStreamConsumer" #39 prio=5 os_prio=0 tid=0x000000000a028000 nid=0x6f2b waiting on condition [0x00002b5477cd5000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a4678188> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:68) > at java.lang.Thread.run(Thread.java:745) > "pool-1-thread-1" #22 prio=5 os_prio=0 tid=0x000000000b4a2000 nid=0x4ea3 in Object.wait() [0x00002b5477bd4000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000a46782b8> (a java.lang.UNIXProcess) > at java.lang.Object.wait(Object.java:502) > at java.lang.UNIXProcess.waitFor(UNIXProcess.java:396) > - locked <0x00000000a46782b8> (a java.lang.UNIXProcess) > at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.CommandLineUtils$1.call(CommandLineUtils.java:202) > at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:141) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:471) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:380) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$300(ForkStarter.java:88) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:315) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:306) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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) > "resolver-4" #21 daemon prio=5 os_prio=0 tid=0x000000000bc90000 nid=0x4ea2 waiting on condition [0x00002b5477a3e000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a856fb90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "resolver-3" #20 daemon prio=5 os_prio=0 tid=0x0000000009fab800 nid=0x4ea1 waiting on condition [0x00002b547793d000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a856fb90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "resolver-2" #19 daemon prio=5 os_prio=0 tid=0x0000000009f0a800 nid=0x4ea0 waiting on condition [0x00002b547711b000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a856fb90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "resolver-1" #18 daemon prio=5 os_prio=0 tid=0x000000000a40f000 nid=0x4e9f waiting on condition [0x00002b547701a000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a856fb90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "process reaper" #11 daemon prio=10 os_prio=0 tid=0x000000000a9c8000 nid=0x4e94 runnable [0x00002b5476f19000] > java.lang.Thread.State: RUNNABLE > at java.lang.UNIXProcess.waitForProcessExit(Native Method) > at java.lang.UNIXProcess.lambda$initStreams$273(UNIXProcess.java:290) > at java.lang.UNIXProcess$$Lambda$7/594570680.run(Unknown Source) > 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) > "Service Thread" #8 daemon prio=9 os_prio=0 tid=0x0000000009431800 nid=0x4e90 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C1 CompilerThread1" #7 daemon prio=9 os_prio=0 tid=0x000000000942a800 nid=0x4e8f waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread0" #6 daemon prio=9 os_prio=0 tid=0x00000000093dc000 nid=0x4e8e waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Signal Dispatcher" #5 daemon prio=9 os_prio=0 tid=0x00000000093d9800 nid=0x4e8d runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Surrogate Locker Thread (Concurrent GC)" #4 daemon prio=9 os_prio=0 tid=0x00000000093d8800 nid=0x4e8c waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Finalizer" #3 daemon prio=8 os_prio=0 tid=0x000000000939a000 nid=0x4e8b in Object.wait() [0x00002b547226a000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000a80443d0> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) > - locked <0x00000000a80443d0> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) > at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209) > "Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x0000000009398000 nid=0x4e8a in Object.wait() [0x00002b5472169000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000a803c3d0> (a java.lang.ref.Reference$Lock) > at java.lang.Object.wait(Object.java:502) > at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:157) > - locked <0x00000000a803c3d0> (a java.lang.ref.Reference$Lock) > "main" #1 prio=5 os_prio=0 tid=0x00000000092ea800 nid=0x4e86 waiting on condition [0x00002b545d802000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a9237408> (a java.util.concurrent.FutureTask) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:429) > at java.util.concurrent.FutureTask.get(FutureTask.java:191) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:327) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:178) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:990) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:824) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:722) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > 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:497) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > "VM Thread" os_prio=0 tid=0x0000000009393000 nid=0x4e89 runnable > "Gang worker#0 (Parallel GC Threads)" os_prio=0 tid=0x00000000092fb800 nid=0x4e87 runnable > "Concurrent Mark-Sweep GC Thread" os_prio=0 tid=0x000000000931e800 nid=0x4e88 runnable > "VM Periodic Task Thread" os_prio=0 tid=0x0000000009434800 nid=0x4e91 waiting on condition > 2016-03-07 10:39:06 > Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode): > "Remoting "endpoint" task-9" #187 daemon prio=5 os_prio=0 tid=0x00000000133d5800 nid=0x73ce waiting on condition [0x00002aeb308f7000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-8" #186 daemon prio=5 os_prio=0 tid=0x000000001372c800 nid=0x73cd waiting on condition [0x00002aeb2f2e3000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "management-client-thread 5-2" #184 prio=5 os_prio=0 tid=0x000000001366d000 nid=0x73a4 waiting on condition [0x00002aeb2eedf000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c207d548> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > "Remoting "endpoint" task-7" #181 daemon prio=5 os_prio=0 tid=0x0000000013329800 nid=0x73a2 waiting on condition [0x00002aeb2feef000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-6" #180 daemon prio=5 os_prio=0 tid=0x0000000013329000 nid=0x73a0 waiting on condition [0x00002aeb2e47f000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-5" #179 daemon prio=5 os_prio=0 tid=0x0000000013328000 nid=0x739f waiting on condition [0x00002aeb2fff0000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-4" #178 daemon prio=5 os_prio=0 tid=0x0000000013327800 nid=0x739e waiting on condition [0x00002aeb31602000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-3" #177 daemon prio=5 os_prio=0 tid=0x0000000013326800 nid=0x739d waiting on condition [0x00002aeb2e989000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-2" #176 daemon prio=5 os_prio=0 tid=0x000000001328b000 nid=0x739c waiting on condition [0x00002aeb307f6000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-1" #175 daemon prio=5 os_prio=0 tid=0x000000001328a000 nid=0x739b waiting on condition [0x00002aeb2f0e1000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" I/O-1" #174 daemon prio=5 os_prio=0 tid=0x000000001328d000 nid=0x739a runnable [0x00002aeb2f7e8000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86) > - locked <0x00000000c20c0428> (a sun.nio.ch.Util$2) > - locked <0x00000000c20c0418> (a java.util.Collections$UnmodifiableSet) > - locked <0x00000000c20c0300> (a sun.nio.ch.EPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:502) > "management-client-thread 5-1" #173 prio=5 os_prio=0 tid=0x000000001328c000 nid=0x7397 waiting on condition [0x00002aeb305f4000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c207d548> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > "Remoting "management-client" task-16" #172 prio=5 os_prio=0 tid=0x000000001339c000 nid=0x738d waiting on condition [0x00002aeb2f6e7000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-15" #171 prio=5 os_prio=0 tid=0x000000001339d800 nid=0x738c waiting on condition [0x00002aeb306f5000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-14" #170 prio=5 os_prio=0 tid=0x0000000013e3c800 nid=0x738a waiting on condition [0x00002aeb2f8e9000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-13" #169 prio=5 os_prio=0 tid=0x0000000013441000 nid=0x7389 waiting on condition [0x00002aeb2f3e4000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-12" #168 prio=5 os_prio=0 tid=0x0000000014229800 nid=0x7388 waiting on condition [0x00002aeb2f5e6000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-11" #167 prio=5 os_prio=0 tid=0x0000000013a53800 nid=0x7387 waiting on condition [0x00002aeb302f1000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-10" #166 prio=5 os_prio=0 tid=0x0000000013472800 nid=0x7386 waiting on condition [0x00002aeb2fdee000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-9" #165 prio=5 os_prio=0 tid=0x00000000134a9000 nid=0x7383 waiting on condition [0x00002aeb2fbec000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-8" #164 prio=5 os_prio=0 tid=0x00000000131dc000 nid=0x737f waiting on condition [0x00002aeb2f1e2000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-7" #163 prio=5 os_prio=0 tid=0x0000000013474800 nid=0x737a waiting on condition [0x00002aeb31703000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-6" #162 prio=5 os_prio=0 tid=0x0000000013b1b800 nid=0x7377 waiting on condition [0x00002aeb30af9000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-5" #161 prio=5 os_prio=0 tid=0x000000001339e800 nid=0x7370 waiting on condition [0x00002aeb2fced000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-4" #160 prio=5 os_prio=0 tid=0x0000000013e3a000 nid=0x736a waiting on condition [0x00002aeb2f9ea000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-3" #159 prio=5 os_prio=0 tid=0x0000000014228000 nid=0x735f waiting on condition [0x00002aeb2faeb000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-2" #158 prio=5 os_prio=0 tid=0x0000000013250000 nid=0x735c waiting on condition [0x00002aeb2efe0000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-1" #157 prio=5 os_prio=0 tid=0x0000000013516000 nid=0x735a waiting on condition [0x00002aeb309f8000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" I/O-1" #156 prio=5 os_prio=0 tid=0x0000000013344000 nid=0x72f5 runnable [0x00002aeb2f4e5000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86) > - locked <0x00000000c2082260> (a sun.nio.ch.Util$2) > - locked <0x00000000c2082250> (a java.util.Collections$UnmodifiableSet) > - locked <0x00000000c2082138> (a sun.nio.ch.EPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:502) > "RMI Scheduler(0)" #46 daemon prio=5 os_prio=0 tid=0x0000000012e95000 nid=0x7003 waiting on condition [0x00002aeb30ffe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c1e599c0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1081) > at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "GC Daemon" #44 daemon prio=2 os_prio=0 tid=0x000000001311c000 nid=0x6ff2 in Object.wait() [0x00002aeb30dfc000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at sun.misc.GC$Daemon.run(GC.java:117) > - locked <0x00000000c1f87830> (a sun.misc.GC$LatencyLock) > "RMI Reaper" #43 prio=5 os_prio=0 tid=0x0000000013119800 nid=0x6ff1 in Object.wait() [0x00002aeb30cfb000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000c1e3f620> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) > - locked <0x00000000c1e3f620> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) > at sun.rmi.transport.ObjectTable$Reaper.run(ObjectTable.java:351) > at java.lang.Thread.run(Thread.java:745) > "RMI TCP Accept-0" #42 daemon prio=5 os_prio=0 tid=0x0000000013117800 nid=0x6ff0 runnable [0x00002aeb30bfa000] > java.lang.Thread.State: RUNNABLE > at java.net.PlainSocketImpl.socketAccept(Native Method) > at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) > at java.net.ServerSocket.implAccept(ServerSocket.java:545) > at java.net.ServerSocket.accept(ServerSocket.java:513) > at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:400) > at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:372) > at java.lang.Thread.run(Thread.java:745) > "process reaper" #10 daemon prio=10 os_prio=0 tid=0x0000000013502800 nid=0x6f3c runnable [0x00002aeb2e37e000] > java.lang.Thread.State: RUNNABLE > at java.lang.UNIXProcess.waitForProcessExit(Native Method) > at java.lang.UNIXProcess.lambda$initStreams$273(UNIXProcess.java:290) > at java.lang.UNIXProcess$$Lambda$7/1233990028.run(Unknown Source) > 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) > "RMI TCP Accept-1199" #9 daemon prio=5 os_prio=0 tid=0x000000001413c800 nid=0x6f39 runnable [0x00002aeb2e10e000] > java.lang.Thread.State: RUNNABLE > at java.net.PlainSocketImpl.socketAccept(Native Method) > at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) > at java.net.ServerSocket.implAccept(ServerSocket.java:545) > at java.net.ServerSocket.accept(ServerSocket.java:513) > at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:400) > at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:372) > at java.lang.Thread.run(Thread.java:745) > "Service Thread" #7 daemon prio=9 os_prio=0 tid=0x0000000012b02000 nid=0x6f37 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C1 CompilerThread1" #6 daemon prio=9 os_prio=0 tid=0x0000000012afb000 nid=0x6f36 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread0" #5 daemon prio=9 os_prio=0 tid=0x0000000012aac800 nid=0x6f35 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Signal Dispatcher" #4 daemon prio=9 os_prio=0 tid=0x0000000012aab000 nid=0x6f34 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Finalizer" #3 daemon prio=8 os_prio=0 tid=0x0000000012a6c800 nid=0x6f33 in Object.wait() [0x00002aeb29f40000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) > - locked <0x00000000c1c25980> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) > at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209) > "Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x0000000012a6a800 nid=0x6f32 in Object.wait() [0x00002aeb29e3f000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.Object.wait(Object.java:502) > at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:157) > - locked <0x00000000c1c25b38> (a java.lang.ref.Reference$Lock) > "main" #1 prio=5 os_prio=0 tid=0x00000000129da000 nid=0x6f2f in Object.wait() [0x00002aeb19032000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.Object.wait(Object.java:502) > at java.lang.UNIXProcess.waitFor(UNIXProcess.java:396) > - locked <0x00000000c207f620> (a java.lang.UNIXProcess) > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.stopInternal(ManagedDeployableContainer.java:275) > at org.jboss.as.arquillian.container.CommonDeployableContainer.stop(CommonDeployableContainer.java:122) > at org.jboss.arquillian.container.impl.ContainerImpl.stop(ContainerImpl.java:217) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$9.perform(ContainerLifecycleController.java:178) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$9.perform(ContainerLifecycleController.java:172) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.stopContainer(ContainerLifecycleController.java:171) > 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:497) > 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.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.stop(ClientContainerController.java:204) > at org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests.tearDown(OutboundBasicTests.java:86) > 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:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) > at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:459) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:80) > 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:497) > 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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > 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:497) > 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.junit.extension.UpdateTestResultBeforeAfter.update(UpdateTestResultBeforeAfter.java:54) > 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:497) > 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.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:122) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:264) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:315) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:72) > 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:497) > 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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > 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:497) > 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.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:311) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > "VM Thread" os_prio=0 tid=0x0000000012a65800 nid=0x6f31 runnable > "VM Periodic Task Thread" os_prio=0 tid=0x0000000012b05800 nid=0x6f38 waiting on condition > JNI global references: 255 > Heap > par new generation total 28864K, used 12323K [0x00000000a2a00000, 0x00000000a4950000, 0x00000000a7d30000) > eden space 25664K, 35% used [0x00000000a2a00000, 0x00000000a32e8dc0, 0x00000000a4310000) > from space 3200K, 100% used [0x00000000a4630000, 0x00000000a4950000, 0x00000000a4950000) > to space 3200K, 0% used [0x00000000a4310000, 0x00000000a4310000, 0x00000000a4630000) > concurrent mark-sweep generation total 64192K, used 30441K [0x00000000a7d30000, 0x00000000abbe0000, 0x0000000100000000) > Metaspace used 26517K, capacity 27428K, committed 27612K, reserved 1073152K > class space used 3152K, capacity 3467K, committed 3556K, reserved 1048576K > JNI global references: 339 > Heap > SUREFIRE-859: def new generation total 29056K, used 109K [0x00000000a2a00000, 0x00000000a4980000, 0x00000000c1c00000) > SUREFIRE-859: eden space 25856K, 0% used [0x00000000a2a00000, 0x00000000a2a1b518, 0x00000000a4340000) > SUREFIRE-859: from space 3200K, 0% used [0x00000000a4340000, 0x00000000a4340000, 0x00000000a4660000) > SUREFIRE-859: to space 3200K, 0% used [0x00000000a4660000, 0x00000000a4660000, 0x00000000a4980000) > SUREFIRE-859: tenured generation total 64192K, used 5286K [0x00000000c1c00000, 0x00000000c5ab0000, 0x0000000100000000) > SUREFIRE-859: the space 64192K, 8% used [0x00000000c1c00000, 0x00000000c2129ab8, 0x00000000c2129c00, 0x00000000c5ab0000) > SUREFIRE-859: Metaspace used 19536K, capacity 19712K, committed 20096K, reserved 1067008K > SUREFIRE-859: class space used 2501K, capacity 2576K, committed 2688K, reserved 1048576K > FATAL: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 31362D30 > hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 31362D30 > 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.$Proxy45.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: java.io.StreamCorruptedException: invalid stream header: 31362D30 > at hudson.remoting.Request.abort(Request.java:299) > at hudson.remoting.Channel.terminate(Channel.java:805) > at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) > Caused by: java.io.StreamCorruptedException: invalid stream header: 31362D30 > at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:806) > at java.io.ObjectInputStream.(ObjectInputStream.java:299) > at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) > at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) > at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 3 05:09:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 3 May 2016 05:09:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2648) Failing .Narayana qa testcase crashrecovery12 method CrashRecovery12_Test03 when journal object store is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2648 started by Gytis Trikleris. --------------------------------------------- > Failing .Narayana qa testcase crashrecovery12 method CrashRecovery12_Test03 when journal object store is used > ------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2648 > URL: https://issues.jboss.org/browse/JBTM-2648 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.14.Final > Reporter: Ond?ej Chaloupka > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: TEST-org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12.txt, testoutput.zip > > > When using journal object store (amq) then we experience failues of test {{crashrecovery12 CrashRecovery12_Test03}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 3 05:40:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 3 May 2016 05:40:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2635) TXBridge OutboundBasicTests hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200121#comment-13200121 ] Gytis Trikleris commented on JBTM-2635: --------------------------------------- Not sure, this seem to be one off thing. If it happens again, I'll raise it with them. > TXBridge OutboundBasicTests hanging > ----------------------------------- > > Key: JBTM-2635 > URL: https://issues.jboss.org/browse/JBTM-2635 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.3.1.Final > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > > Thread dump > {code} > Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode): > "Thread-16" #41 prio=5 os_prio=0 tid=0x0000000009fb6000 nid=0x6f30 runnable [0x00002b5477ed7000] > java.lang.Thread.State: RUNNABLE > at java.io.FileInputStream.readBytes(Native Method) > at java.io.FileInputStream.read(FileInputStream.java:255) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:284) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x00000000a46321e0> (a java.lang.UNIXProcess$ProcessPipeInputStream) > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) > - locked <0x00000000a4632238> (a java.io.InputStreamReader) > at java.io.InputStreamReader.read(InputStreamReader.java:184) > at java.io.BufferedReader.fill(BufferedReader.java:161) > at java.io.BufferedReader.readLine(BufferedReader.java:324) > - locked <0x00000000a4632238> (a java.io.InputStreamReader) > at java.io.BufferedReader.readLine(BufferedReader.java:389) > at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:66) > "Thread-15" #40 prio=5 os_prio=0 tid=0x0000000009f86000 nid=0x6f2d runnable [0x00002b5477dd6000] > java.lang.Thread.State: RUNNABLE > at java.io.FileInputStream.readBytes(Native Method) > at java.io.FileInputStream.read(FileInputStream.java:255) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:284) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x00000000a46782f8> (a java.lang.UNIXProcess$ProcessPipeInputStream) > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) > - locked <0x00000000a4827108> (a java.io.InputStreamReader) > at java.io.InputStreamReader.read(InputStreamReader.java:184) > at java.io.BufferedReader.fill(BufferedReader.java:161) > at java.io.BufferedReader.readLine(BufferedReader.java:324) > - locked <0x00000000a4827108> (a java.io.InputStreamReader) > at java.io.BufferedReader.readLine(BufferedReader.java:389) > at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:66) > "ThreadedStreamConsumer" #39 prio=5 os_prio=0 tid=0x000000000a028000 nid=0x6f2b waiting on condition [0x00002b5477cd5000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a4678188> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:68) > at java.lang.Thread.run(Thread.java:745) > "pool-1-thread-1" #22 prio=5 os_prio=0 tid=0x000000000b4a2000 nid=0x4ea3 in Object.wait() [0x00002b5477bd4000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000a46782b8> (a java.lang.UNIXProcess) > at java.lang.Object.wait(Object.java:502) > at java.lang.UNIXProcess.waitFor(UNIXProcess.java:396) > - locked <0x00000000a46782b8> (a java.lang.UNIXProcess) > at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.CommandLineUtils$1.call(CommandLineUtils.java:202) > at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:141) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:471) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:380) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$300(ForkStarter.java:88) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:315) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:306) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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) > "resolver-4" #21 daemon prio=5 os_prio=0 tid=0x000000000bc90000 nid=0x4ea2 waiting on condition [0x00002b5477a3e000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a856fb90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "resolver-3" #20 daemon prio=5 os_prio=0 tid=0x0000000009fab800 nid=0x4ea1 waiting on condition [0x00002b547793d000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a856fb90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "resolver-2" #19 daemon prio=5 os_prio=0 tid=0x0000000009f0a800 nid=0x4ea0 waiting on condition [0x00002b547711b000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a856fb90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "resolver-1" #18 daemon prio=5 os_prio=0 tid=0x000000000a40f000 nid=0x4e9f waiting on condition [0x00002b547701a000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a856fb90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "process reaper" #11 daemon prio=10 os_prio=0 tid=0x000000000a9c8000 nid=0x4e94 runnable [0x00002b5476f19000] > java.lang.Thread.State: RUNNABLE > at java.lang.UNIXProcess.waitForProcessExit(Native Method) > at java.lang.UNIXProcess.lambda$initStreams$273(UNIXProcess.java:290) > at java.lang.UNIXProcess$$Lambda$7/594570680.run(Unknown Source) > 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) > "Service Thread" #8 daemon prio=9 os_prio=0 tid=0x0000000009431800 nid=0x4e90 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C1 CompilerThread1" #7 daemon prio=9 os_prio=0 tid=0x000000000942a800 nid=0x4e8f waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread0" #6 daemon prio=9 os_prio=0 tid=0x00000000093dc000 nid=0x4e8e waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Signal Dispatcher" #5 daemon prio=9 os_prio=0 tid=0x00000000093d9800 nid=0x4e8d runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Surrogate Locker Thread (Concurrent GC)" #4 daemon prio=9 os_prio=0 tid=0x00000000093d8800 nid=0x4e8c waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Finalizer" #3 daemon prio=8 os_prio=0 tid=0x000000000939a000 nid=0x4e8b in Object.wait() [0x00002b547226a000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000a80443d0> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) > - locked <0x00000000a80443d0> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) > at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209) > "Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x0000000009398000 nid=0x4e8a in Object.wait() [0x00002b5472169000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000a803c3d0> (a java.lang.ref.Reference$Lock) > at java.lang.Object.wait(Object.java:502) > at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:157) > - locked <0x00000000a803c3d0> (a java.lang.ref.Reference$Lock) > "main" #1 prio=5 os_prio=0 tid=0x00000000092ea800 nid=0x4e86 waiting on condition [0x00002b545d802000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a9237408> (a java.util.concurrent.FutureTask) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:429) > at java.util.concurrent.FutureTask.get(FutureTask.java:191) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:327) > at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:178) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:990) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:824) > at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:722) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > 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:497) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > "VM Thread" os_prio=0 tid=0x0000000009393000 nid=0x4e89 runnable > "Gang worker#0 (Parallel GC Threads)" os_prio=0 tid=0x00000000092fb800 nid=0x4e87 runnable > "Concurrent Mark-Sweep GC Thread" os_prio=0 tid=0x000000000931e800 nid=0x4e88 runnable > "VM Periodic Task Thread" os_prio=0 tid=0x0000000009434800 nid=0x4e91 waiting on condition > 2016-03-07 10:39:06 > Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode): > "Remoting "endpoint" task-9" #187 daemon prio=5 os_prio=0 tid=0x00000000133d5800 nid=0x73ce waiting on condition [0x00002aeb308f7000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-8" #186 daemon prio=5 os_prio=0 tid=0x000000001372c800 nid=0x73cd waiting on condition [0x00002aeb2f2e3000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "management-client-thread 5-2" #184 prio=5 os_prio=0 tid=0x000000001366d000 nid=0x73a4 waiting on condition [0x00002aeb2eedf000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c207d548> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > "Remoting "endpoint" task-7" #181 daemon prio=5 os_prio=0 tid=0x0000000013329800 nid=0x73a2 waiting on condition [0x00002aeb2feef000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-6" #180 daemon prio=5 os_prio=0 tid=0x0000000013329000 nid=0x73a0 waiting on condition [0x00002aeb2e47f000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-5" #179 daemon prio=5 os_prio=0 tid=0x0000000013328000 nid=0x739f waiting on condition [0x00002aeb2fff0000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-4" #178 daemon prio=5 os_prio=0 tid=0x0000000013327800 nid=0x739e waiting on condition [0x00002aeb31602000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-3" #177 daemon prio=5 os_prio=0 tid=0x0000000013326800 nid=0x739d waiting on condition [0x00002aeb2e989000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-2" #176 daemon prio=5 os_prio=0 tid=0x000000001328b000 nid=0x739c waiting on condition [0x00002aeb307f6000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" task-1" #175 daemon prio=5 os_prio=0 tid=0x000000001328a000 nid=0x739b waiting on condition [0x00002aeb2f0e1000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c20bff98> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "endpoint" I/O-1" #174 daemon prio=5 os_prio=0 tid=0x000000001328d000 nid=0x739a runnable [0x00002aeb2f7e8000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86) > - locked <0x00000000c20c0428> (a sun.nio.ch.Util$2) > - locked <0x00000000c20c0418> (a java.util.Collections$UnmodifiableSet) > - locked <0x00000000c20c0300> (a sun.nio.ch.EPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:502) > "management-client-thread 5-1" #173 prio=5 os_prio=0 tid=0x000000001328c000 nid=0x7397 waiting on condition [0x00002aeb305f4000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c207d548> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > "Remoting "management-client" task-16" #172 prio=5 os_prio=0 tid=0x000000001339c000 nid=0x738d waiting on condition [0x00002aeb2f6e7000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-15" #171 prio=5 os_prio=0 tid=0x000000001339d800 nid=0x738c waiting on condition [0x00002aeb306f5000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-14" #170 prio=5 os_prio=0 tid=0x0000000013e3c800 nid=0x738a waiting on condition [0x00002aeb2f8e9000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-13" #169 prio=5 os_prio=0 tid=0x0000000013441000 nid=0x7389 waiting on condition [0x00002aeb2f3e4000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-12" #168 prio=5 os_prio=0 tid=0x0000000014229800 nid=0x7388 waiting on condition [0x00002aeb2f5e6000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-11" #167 prio=5 os_prio=0 tid=0x0000000013a53800 nid=0x7387 waiting on condition [0x00002aeb302f1000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-10" #166 prio=5 os_prio=0 tid=0x0000000013472800 nid=0x7386 waiting on condition [0x00002aeb2fdee000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-9" #165 prio=5 os_prio=0 tid=0x00000000134a9000 nid=0x7383 waiting on condition [0x00002aeb2fbec000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-8" #164 prio=5 os_prio=0 tid=0x00000000131dc000 nid=0x737f waiting on condition [0x00002aeb2f1e2000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-7" #163 prio=5 os_prio=0 tid=0x0000000013474800 nid=0x737a waiting on condition [0x00002aeb31703000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-6" #162 prio=5 os_prio=0 tid=0x0000000013b1b800 nid=0x7377 waiting on condition [0x00002aeb30af9000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-5" #161 prio=5 os_prio=0 tid=0x000000001339e800 nid=0x7370 waiting on condition [0x00002aeb2fced000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-4" #160 prio=5 os_prio=0 tid=0x0000000013e3a000 nid=0x736a waiting on condition [0x00002aeb2f9ea000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-3" #159 prio=5 os_prio=0 tid=0x0000000014228000 nid=0x735f waiting on condition [0x00002aeb2faeb000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-2" #158 prio=5 os_prio=0 tid=0x0000000013250000 nid=0x735c waiting on condition [0x00002aeb2efe0000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" task-1" #157 prio=5 os_prio=0 tid=0x0000000013516000 nid=0x735a waiting on condition [0x00002aeb309f8000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c2081de8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "Remoting "management-client" I/O-1" #156 prio=5 os_prio=0 tid=0x0000000013344000 nid=0x72f5 runnable [0x00002aeb2f4e5000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86) > - locked <0x00000000c2082260> (a sun.nio.ch.Util$2) > - locked <0x00000000c2082250> (a java.util.Collections$UnmodifiableSet) > - locked <0x00000000c2082138> (a sun.nio.ch.EPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:502) > "RMI Scheduler(0)" #46 daemon prio=5 os_prio=0 tid=0x0000000012e95000 nid=0x7003 waiting on condition [0x00002aeb30ffe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000c1e599c0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1081) > at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > "GC Daemon" #44 daemon prio=2 os_prio=0 tid=0x000000001311c000 nid=0x6ff2 in Object.wait() [0x00002aeb30dfc000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at sun.misc.GC$Daemon.run(GC.java:117) > - locked <0x00000000c1f87830> (a sun.misc.GC$LatencyLock) > "RMI Reaper" #43 prio=5 os_prio=0 tid=0x0000000013119800 nid=0x6ff1 in Object.wait() [0x00002aeb30cfb000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000c1e3f620> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) > - locked <0x00000000c1e3f620> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) > at sun.rmi.transport.ObjectTable$Reaper.run(ObjectTable.java:351) > at java.lang.Thread.run(Thread.java:745) > "RMI TCP Accept-0" #42 daemon prio=5 os_prio=0 tid=0x0000000013117800 nid=0x6ff0 runnable [0x00002aeb30bfa000] > java.lang.Thread.State: RUNNABLE > at java.net.PlainSocketImpl.socketAccept(Native Method) > at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) > at java.net.ServerSocket.implAccept(ServerSocket.java:545) > at java.net.ServerSocket.accept(ServerSocket.java:513) > at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:400) > at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:372) > at java.lang.Thread.run(Thread.java:745) > "process reaper" #10 daemon prio=10 os_prio=0 tid=0x0000000013502800 nid=0x6f3c runnable [0x00002aeb2e37e000] > java.lang.Thread.State: RUNNABLE > at java.lang.UNIXProcess.waitForProcessExit(Native Method) > at java.lang.UNIXProcess.lambda$initStreams$273(UNIXProcess.java:290) > at java.lang.UNIXProcess$$Lambda$7/1233990028.run(Unknown Source) > 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) > "RMI TCP Accept-1199" #9 daemon prio=5 os_prio=0 tid=0x000000001413c800 nid=0x6f39 runnable [0x00002aeb2e10e000] > java.lang.Thread.State: RUNNABLE > at java.net.PlainSocketImpl.socketAccept(Native Method) > at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) > at java.net.ServerSocket.implAccept(ServerSocket.java:545) > at java.net.ServerSocket.accept(ServerSocket.java:513) > at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:400) > at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:372) > at java.lang.Thread.run(Thread.java:745) > "Service Thread" #7 daemon prio=9 os_prio=0 tid=0x0000000012b02000 nid=0x6f37 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C1 CompilerThread1" #6 daemon prio=9 os_prio=0 tid=0x0000000012afb000 nid=0x6f36 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread0" #5 daemon prio=9 os_prio=0 tid=0x0000000012aac800 nid=0x6f35 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Signal Dispatcher" #4 daemon prio=9 os_prio=0 tid=0x0000000012aab000 nid=0x6f34 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Finalizer" #3 daemon prio=8 os_prio=0 tid=0x0000000012a6c800 nid=0x6f33 in Object.wait() [0x00002aeb29f40000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) > - locked <0x00000000c1c25980> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) > at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209) > "Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x0000000012a6a800 nid=0x6f32 in Object.wait() [0x00002aeb29e3f000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.Object.wait(Object.java:502) > at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:157) > - locked <0x00000000c1c25b38> (a java.lang.ref.Reference$Lock) > "main" #1 prio=5 os_prio=0 tid=0x00000000129da000 nid=0x6f2f in Object.wait() [0x00002aeb19032000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.Object.wait(Object.java:502) > at java.lang.UNIXProcess.waitFor(UNIXProcess.java:396) > - locked <0x00000000c207f620> (a java.lang.UNIXProcess) > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.stopInternal(ManagedDeployableContainer.java:275) > at org.jboss.as.arquillian.container.CommonDeployableContainer.stop(CommonDeployableContainer.java:122) > at org.jboss.arquillian.container.impl.ContainerImpl.stop(ContainerImpl.java:217) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$9.perform(ContainerLifecycleController.java:178) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$9.perform(ContainerLifecycleController.java:172) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.stopContainer(ContainerLifecycleController.java:171) > 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:497) > 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.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.stop(ClientContainerController.java:204) > at org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests.tearDown(OutboundBasicTests.java:86) > 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:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) > at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:459) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:80) > 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:497) > 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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > 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:497) > 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.junit.extension.UpdateTestResultBeforeAfter.update(UpdateTestResultBeforeAfter.java:54) > 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:497) > 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.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:122) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:264) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:315) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:72) > 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:497) > 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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > 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:497) > 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.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:311) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > "VM Thread" os_prio=0 tid=0x0000000012a65800 nid=0x6f31 runnable > "VM Periodic Task Thread" os_prio=0 tid=0x0000000012b05800 nid=0x6f38 waiting on condition > JNI global references: 255 > Heap > par new generation total 28864K, used 12323K [0x00000000a2a00000, 0x00000000a4950000, 0x00000000a7d30000) > eden space 25664K, 35% used [0x00000000a2a00000, 0x00000000a32e8dc0, 0x00000000a4310000) > from space 3200K, 100% used [0x00000000a4630000, 0x00000000a4950000, 0x00000000a4950000) > to space 3200K, 0% used [0x00000000a4310000, 0x00000000a4310000, 0x00000000a4630000) > concurrent mark-sweep generation total 64192K, used 30441K [0x00000000a7d30000, 0x00000000abbe0000, 0x0000000100000000) > Metaspace used 26517K, capacity 27428K, committed 27612K, reserved 1073152K > class space used 3152K, capacity 3467K, committed 3556K, reserved 1048576K > JNI global references: 339 > Heap > SUREFIRE-859: def new generation total 29056K, used 109K [0x00000000a2a00000, 0x00000000a4980000, 0x00000000c1c00000) > SUREFIRE-859: eden space 25856K, 0% used [0x00000000a2a00000, 0x00000000a2a1b518, 0x00000000a4340000) > SUREFIRE-859: from space 3200K, 0% used [0x00000000a4340000, 0x00000000a4340000, 0x00000000a4660000) > SUREFIRE-859: to space 3200K, 0% used [0x00000000a4660000, 0x00000000a4660000, 0x00000000a4980000) > SUREFIRE-859: tenured generation total 64192K, used 5286K [0x00000000c1c00000, 0x00000000c5ab0000, 0x0000000100000000) > SUREFIRE-859: the space 64192K, 8% used [0x00000000c1c00000, 0x00000000c2129ab8, 0x00000000c2129c00, 0x00000000c5ab0000) > SUREFIRE-859: Metaspace used 19536K, capacity 19712K, committed 20096K, reserved 1067008K > SUREFIRE-859: class space used 2501K, capacity 2576K, committed 2688K, reserved 1048576K > FATAL: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 31362D30 > hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 31362D30 > 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.$Proxy45.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: java.io.StreamCorruptedException: invalid stream header: 31362D30 > at hudson.remoting.Request.abort(Request.java:299) > at hudson.remoting.Channel.terminate(Channel.java:805) > at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) > Caused by: java.io.StreamCorruptedException: invalid stream header: 31362D30 > at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:806) > at java.io.ObjectInputStream.(ObjectInputStream.java:299) > at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) > at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) > at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 3 05:49:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 3 May 2016 05:49:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2648) Failing .Narayana qa testcase crashrecovery12 method CrashRecovery12_Test03 when journal object store is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2648: ---------------------------------- Steps to Reproduce: * git checkout 5.2.14.Final * ./build.sh clean install -Prelease,community -DskipTests -Didlj-enabled=true * cd qa * ant -Dorbtype=idlj dist * sed -i 's/^\(COMMAND_LINE_0=\)/#\1/' TaskImpl.properties && sed -i 's/#\(COMMAND_LINE_0=\${java.home}\)/\1/' TaskImpl.properties * sed -i -e '/^.*separator}jacorb/ d' TaskImpl.properties * export DISTOPENJDKORB=`echo dist/narayana-full-*Final/lib/ext/openjdk-orb.jar` * export DISTOPENJDKORB=`echo $DISTOPENJDKORB` * sed -i '' "s#NEXT_COMMAND_LINE_ARG.*#COMMAND_LINE_16=-Xbootclasspath/p:$DISTOPENJDKORB#" TaskImpl.properties * ant -f run-tests.xml -Dprofile=hornetq -Dtest.name=crashrecovery12 -Dtest.methods="CrashRecovery12_Test03" onetest was: * git checkout 5.2.14.Final * ./build.sh clean install -Prelease,community -DskipTests -Didlj-enabled=true * cd qa * ant -Dorbtype=idlj dist * sed -i 's/^\(COMMAND_LINE_0=\)/#\1/' TaskImpl.properties && sed -i 's/#\(COMMAND_LINE_0=\${java.home}\)/\1/' TaskImpl.properties * sed -i -e '/^.*separator}jacorb/ d' TaskImpl.properties * export DISTOPENJDKORB=`echo dist/narayana-full-*Final/lib/ext/openjdk-orb.jar` * export DISTOPENJDKORB=`echo $DISTOPENJDKORB` * sed -i "s#NEXT_COMMAND_LINE_ARG.*#COMMAND_LINE_16=-Xbootclasspath/p:$DISTOPENJDKORB#" TaskImpl.properties * ant -f run-tests.xml -Dprofile=hornetq -Dtest.name=crashrecovery12 -Dtest.methods="CrashRecovery12_Test03" onetest > Failing .Narayana qa testcase crashrecovery12 method CrashRecovery12_Test03 when journal object store is used > ------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2648 > URL: https://issues.jboss.org/browse/JBTM-2648 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.14.Final > Reporter: Ond?ej Chaloupka > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: TEST-org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12.txt, testoutput.zip > > > When using journal object store (amq) then we experience failues of test {{crashrecovery12 CrashRecovery12_Test03}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 3 06:12:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 3 May 2016 06:12:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2648) Failing .Narayana qa testcase crashrecovery12 method CrashRecovery12_Test03 when journal object store is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #1006 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Failing .Narayana qa testcase crashrecovery12 method CrashRecovery12_Test03 when journal object store is used > ------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2648 > URL: https://issues.jboss.org/browse/JBTM-2648 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.14.Final > Reporter: Ond?ej Chaloupka > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: TEST-org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12.txt, testoutput.zip > > > When using journal object store (amq) then we experience failues of test {{crashrecovery12 CrashRecovery12_Test03}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 3 06:21:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 3 May 2016 06:21:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2666) karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2666: ------------------------------------- Summary: karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart Key: JBTM-2666 URL: https://issues.jboss.org/browse/JBTM-2666 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator Reporter: Gytis Trikleris Assignee: Amos Feng Priority: Blocker Fix For: 5.next {code} [ERROR] Plugin org.apache.karaf.tooling:karaf-services-maven-plugin:4.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.karaf.tooling:karaf-services-maven-plugin:jar:4.1.0-SNAPSHOT: Could not find artifact org.apache.karaf.tooling:karaf-services-maven-plugin:pom:4.1.0-SNAPSHOT -> [Help 1] {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 3 09:15:05 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 3 May 2016 09:15:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2634) Create Narayana Spring Boot starter quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2634 started by Gytis Trikleris. --------------------------------------------- > Create Narayana Spring Boot starter quickstart > ---------------------------------------------- > > Key: JBTM-2634 > URL: https://issues.jboss.org/browse/JBTM-2634 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Create a demonstrator application for Narayana Spring Boot starter before raising pull request to Spring. This would allow to make a better review of the Narayana Spring Boot integration on the forum. > Quickstart should have a simple example of JTA and crash recovery. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 3 09:19:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 3 May 2016 09:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2658) Implement JMS integration classes for MessageListener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200278#comment-13200278 ] Tom Jenkinson commented on JBTM-2658: ------------------------------------- https://developer.jboss.org/thread/269475 > Implement JMS integration classes for MessageListener > ----------------------------------------------------- > > Key: JBTM-2658 > URL: https://issues.jboss.org/browse/JBTM-2658 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.3.2.Final > Reporter: Alexis Hassler > Priority: Minor > > The new JMS integration classes are working fine with a Publisher or a simple Consumer, but not with MessageListener. It would be nice to be able to implement something like a MDB without JavaEE. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 3 09:56:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 3 May 2016 09:56:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2634) Create Narayana Spring Boot starter quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #162 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Create Narayana Spring Boot starter quickstart > ---------------------------------------------- > > Key: JBTM-2634 > URL: https://issues.jboss.org/browse/JBTM-2634 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Create a demonstrator application for Narayana Spring Boot starter before raising pull request to Spring. This would allow to make a better review of the Narayana Spring Boot integration on the forum. > Quickstart should have a simple example of JTA and crash recovery. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 3 10:14:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 3 May 2016 10:14: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 ] Michael Musgrove updated JBTM-2463: ----------------------------------- Attachment: testoutput-idlj.tar > 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 > > Attachments: testoutput-idlj.tar > > > 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 Tue May 3 11:21:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 3 May 2016 11:21: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 ] Michael Musgrove updated JBTM-2539: ----------------------------------- Attachment: testoutput-jacorb.tar > 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 > > Attachments: testoutput-jacorb.tar > > > 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 Tue May 3 21:50:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 3 May 2016 21:50:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2666) karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200611#comment-13200611 ] Amos Feng commented on JBTM-2666: --------------------------------- It needs to update the job to build the karaf before running this quickstart as the the current 4.1.0-SNAPSHOT supports the narayana > karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart > -------------------------------------------------------------------------------- > > Key: JBTM-2666 > URL: https://issues.jboss.org/browse/JBTM-2666 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > {code} > [ERROR] Plugin org.apache.karaf.tooling:karaf-services-maven-plugin:4.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.karaf.tooling:karaf-services-maven-plugin:jar:4.1.0-SNAPSHOT: Could not find artifact org.apache.karaf.tooling:karaf-services-maven-plugin:pom:4.1.0-SNAPSHOT -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 01:52:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 4 May 2016 01:52:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2666) karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200659#comment-13200659 ] Amos Feng commented on JBTM-2666: --------------------------------- it works http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/340/ > karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart > -------------------------------------------------------------------------------- > > Key: JBTM-2666 > URL: https://issues.jboss.org/browse/JBTM-2666 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > {code} > [ERROR] Plugin org.apache.karaf.tooling:karaf-services-maven-plugin:4.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.karaf.tooling:karaf-services-maven-plugin:jar:4.1.0-SNAPSHOT: Could not find artifact org.apache.karaf.tooling:karaf-services-maven-plugin:pom:4.1.0-SNAPSHOT -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 05:21:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 05:21:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2666) karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2666: -------------------------------- Fix Version/s: (was: 5.next) > karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart > -------------------------------------------------------------------------------- > > Key: JBTM-2666 > URL: https://issues.jboss.org/browse/JBTM-2666 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > > {code} > [ERROR] Plugin org.apache.karaf.tooling:karaf-services-maven-plugin:4.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.karaf.tooling:karaf-services-maven-plugin:jar:4.1.0-SNAPSHOT: Could not find artifact org.apache.karaf.tooling:karaf-services-maven-plugin:pom:4.1.0-SNAPSHOT -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 05:22:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 05:22:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2666) karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2666. --------------------------------- Release Notes Text: Resolved in jenkins config Resolution: Migrated to another ITS > karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart > -------------------------------------------------------------------------------- > > Key: JBTM-2666 > URL: https://issues.jboss.org/browse/JBTM-2666 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > > {code} > [ERROR] Plugin org.apache.karaf.tooling:karaf-services-maven-plugin:4.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.karaf.tooling:karaf-services-maven-plugin:jar:4.1.0-SNAPSHOT: Could not find artifact org.apache.karaf.tooling:karaf-services-maven-plugin:pom:4.1.0-SNAPSHOT -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 05:23:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 05:23:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2666) karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2666: -------------------------------- Release Notes Text: (was: Resolved in jenkins config) > karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart > -------------------------------------------------------------------------------- > > Key: JBTM-2666 > URL: https://issues.jboss.org/browse/JBTM-2666 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > > {code} > [ERROR] Plugin org.apache.karaf.tooling:karaf-services-maven-plugin:4.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.karaf.tooling:karaf-services-maven-plugin:jar:4.1.0-SNAPSHOT: Could not find artifact org.apache.karaf.tooling:karaf-services-maven-plugin:pom:4.1.0-SNAPSHOT -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 05:23:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 05:23:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2666) karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200776#comment-13200776 ] Tom Jenkinson commented on JBTM-2666: ------------------------------------- Resolved in jenkins config > karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart > -------------------------------------------------------------------------------- > > Key: JBTM-2666 > URL: https://issues.jboss.org/browse/JBTM-2666 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > > {code} > [ERROR] Plugin org.apache.karaf.tooling:karaf-services-maven-plugin:4.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.karaf.tooling:karaf-services-maven-plugin:jar:4.1.0-SNAPSHOT: Could not find artifact org.apache.karaf.tooling:karaf-services-maven-plugin:pom:4.1.0-SNAPSHOT -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 06:23:00 2016 From: issues at jboss.org (Alexis Hassler (JIRA)) Date: Wed, 4 May 2016 06:23:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2667) JDBC Connection leak with Postgres In-Reply-To: References: Message-ID: Alexis Hassler created JBTM-2667: ------------------------------------ Summary: JDBC Connection leak with Postgres Key: JBTM-2667 URL: https://issues.jboss.org/browse/JBTM-2667 Project: JBoss Transaction Manager Issue Type: Feature Request Components: JTA Affects Versions: 5.3.2.Final Reporter: Alexis Hassler When using Narayana's JDBC TransactionalDriver with a Postgres XA datasource, the connections are never closed. The problem can be workarounded by adding a modifier : {code:java} ModifierFactory.putModifier ("postgresql native driver", -1, -1, PsqlConnectionModifier.class.getName()); {code} With a modifier, the close method is called on the XAConnection object, with no modifier it's called on the Connection object. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 06:47:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 06:47:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2667) JDBC Connection leak with Postgres In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2667: ----------------------------------- Assignee: Tom Jenkinson > JDBC Connection leak with Postgres > ---------------------------------- > > Key: JBTM-2667 > URL: https://issues.jboss.org/browse/JBTM-2667 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.3.2.Final > Reporter: Alexis Hassler > Assignee: Tom Jenkinson > Fix For: 5.next > > > When using Narayana's JDBC TransactionalDriver with a Postgres XA datasource, the connections are never closed. > The problem can be workarounded by adding a modifier : > {code:java} > ModifierFactory.putModifier ("postgresql native driver", -1, -1, PsqlConnectionModifier.class.getName()); > {code} > With a modifier, the close method is called on the XAConnection object, with no modifier it's called on the Connection object. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 06:47:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 06:47:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2667) JDBC Connection leak with Postgres In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2667: -------------------------------- Fix Version/s: 5.next > JDBC Connection leak with Postgres > ---------------------------------- > > Key: JBTM-2667 > URL: https://issues.jboss.org/browse/JBTM-2667 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.3.2.Final > Reporter: Alexis Hassler > Assignee: Tom Jenkinson > Fix For: 5.next > > > When using Narayana's JDBC TransactionalDriver with a Postgres XA datasource, the connections are never closed. > The problem can be workarounded by adding a modifier : > {code:java} > ModifierFactory.putModifier ("postgresql native driver", -1, -1, PsqlConnectionModifier.class.getName()); > {code} > With a modifier, the close method is called on the XAConnection object, with no modifier it's called on the Connection object. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 06:47:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 06:47:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2667) JDBC Connection leak with Postgres In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2667: -------------------------------- Issue Type: Bug (was: Feature Request) > JDBC Connection leak with Postgres > ---------------------------------- > > Key: JBTM-2667 > URL: https://issues.jboss.org/browse/JBTM-2667 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.3.2.Final > Reporter: Alexis Hassler > Assignee: Tom Jenkinson > Fix For: 5.next > > > When using Narayana's JDBC TransactionalDriver with a Postgres XA datasource, the connections are never closed. > The problem can be workarounded by adding a modifier : > {code:java} > ModifierFactory.putModifier ("postgresql native driver", -1, -1, PsqlConnectionModifier.class.getName()); > {code} > With a modifier, the close method is called on the XAConnection object, with no modifier it's called on the Connection object. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 07:27:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 07:27:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2667) JDBC Connection leak with Postgres In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #1007 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > JDBC Connection leak with Postgres > ---------------------------------- > > Key: JBTM-2667 > URL: https://issues.jboss.org/browse/JBTM-2667 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.3.2.Final > Reporter: Alexis Hassler > Assignee: Tom Jenkinson > Fix For: 5.next > > > When using Narayana's JDBC TransactionalDriver with a Postgres XA datasource, the connections are never closed. > The problem can be workarounded by adding a modifier : > {code:java} > ModifierFactory.putModifier ("postgresql native driver", -1, -1, PsqlConnectionModifier.class.getName()); > {code} > With a modifier, the close method is called on the XAConnection object, with no modifier it's called on the Connection object. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 11:53:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 11:53:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2655) QA suite failure: TestGroup_txcore_recovery (JDBC store) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2655: -------------------------------- Description: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-jdbcobjectstore/191/DB_TYPE=db2,jdk=jdk8.latest,slave=linux/consoleFull (was: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-jdbcobjectstore/164/DB_TYPE=db2,jdk=jdk7.latest,slave=linux/consoleFull) > QA suite failure: TestGroup_txcore_recovery (JDBC store) > -------------------------------------------------------- > > Key: JBTM-2655 > URL: https://issues.jboss.org/browse/JBTM-2655 > 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/view/Narayana/job/narayana-jdbcobjectstore/191/DB_TYPE=db2,jdk=jdk8.latest,slave=linux/consoleFull -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 16:36:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 16:36:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2655) QA suite failure: TestGroup_txcore_recovery (JDBC store) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #1009 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > QA suite failure: TestGroup_txcore_recovery (JDBC store) > -------------------------------------------------------- > > Key: JBTM-2655 > URL: https://issues.jboss.org/browse/JBTM-2655 > 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/view/Narayana/job/narayana-jdbcobjectstore/191/DB_TYPE=db2,jdk=jdk8.latest,slave=linux/consoleFull -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 16:37:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 16:37:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2655) QA suite failure: TestGroup_txcore_recovery (JDBC store) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2655: -------------------------------- Fix Version/s: 5.next (was: 5.later) > QA suite failure: TestGroup_txcore_recovery (JDBC store) > -------------------------------------------------------- > > Key: JBTM-2655 > URL: https://issues.jboss.org/browse/JBTM-2655 > 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/view/Narayana/job/narayana-jdbcobjectstore/191/DB_TYPE=db2,jdk=jdk8.latest,slave=linux/consoleFull -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 18:05:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 18:05:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2550: --------------------------------- > If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2550 > URL: https://issues.jboss.org/browse/JBTM-2550 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Affects Versions: 5.2.8.Final > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.2.10.Final > > > This exception happens with using the IBM MQ rar in the wildfly. > com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR > We can catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 4 18:05:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 4 May 2016 18:05:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2550: -------------------------------- Fix Version/s: 4.17.33 > If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2550 > URL: https://issues.jboss.org/browse/JBTM-2550 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Affects Versions: 5.2.8.Final > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 4.17.33, 5.2.10.Final > > > This exception happens with using the IBM MQ rar in the wildfly. > com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR > We can catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 5 05:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 5 May 2016 05:32:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2655) QA suite failure: TestGroup_txcore_recovery (JDBC store) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201422#comment-13201422 ] Tom Jenkinson commented on JBTM-2655: ------------------------------------- I noticed that if nothing was updated during write_state then we still returned true. I am not sure if that is the cause of this but it is wrong. I have added some more warnings to help isolate the issue. > QA suite failure: TestGroup_txcore_recovery (JDBC store) > -------------------------------------------------------- > > Key: JBTM-2655 > URL: https://issues.jboss.org/browse/JBTM-2655 > 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/view/Narayana/job/narayana-jdbcobjectstore/191/DB_TYPE=db2,jdk=jdk8.latest,slave=linux/consoleFull -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 5 05:54:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 5 May 2016 05:54:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-928) ATParticipantCrashAndRecover Crash Recovery test needs completing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-928: --------------------------------- Fix Version/s: (was: 5.later) > ATParticipantCrashAndRecover Crash Recovery test needs completing > ----------------------------------------------------------------- > > Key: JBTM-928 > URL: https://issues.jboss.org/browse/JBTM-928 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing, XTS > Affects Versions: 4.17.0.M1/5.0.0.M1 > Reporter: Paul Robinson > Assignee: Gytis Trikleris > > This test was not completed due to a problem with JBossWS that prevented the test case from being possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 5 06:01:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 5 May 2016 06:01:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2345) Off image storage for docker transaction service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2345. --------------------------------- Fix Version/s: (was: 5.later) Resolution: Done https://github.com/jbosstm/quickstart/tree/master/jts-docker has an explanation of how to mount a local directory as an object store, as well as how to use JDBC store with the Docker container. > Off image storage for docker transaction service > ------------------------------------------------ > > Key: JBTM-2345 > URL: https://issues.jboss.org/browse/JBTM-2345 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System, Cloud, JTS > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Gytis Trikleris > Labels: docker > > Now we have a docker image for JTS we need to look at making the state available after the image(s) go away. Remember that docker produces immutable images, so any state change that occurs within the running instance will be lost when the image dies, is taken out of service etc. Currently the docker image for JTS we have will store all of the transaction log information within the image, which is fine for testing purposes but not for a running deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 5 07:27:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 5 May 2016 07:27:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2622) Implement possible new compensations api from the meeting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2622 started by Gytis Trikleris. --------------------------------------------- > Implement possible new compensations api from the meeting > --------------------------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 5 09:44:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 5 May 2016 09:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2622) Implement possible new compensations api from the meeting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #1010 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Implement possible new compensations api from the meeting > --------------------------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 6 05:57:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 6 May 2016 05:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2668) Entity manager does not join transaction properly in JTA and Hibernate quickstart In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2668: ------------------------------------- Summary: Entity manager does not join transaction properly in JTA and Hibernate quickstart Key: JBTM-2668 URL: https://issues.jboss.org/browse/JBTM-2668 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next To reproduce begin transaction at the start of TestCase.testJpa method and roll it back just before assertion. During the abort in BasicAction pending list is empty and no resources are rolled back. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 6 06:25:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 6 May 2016 06:25:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2550. --------------------------------- Resolution: Done > If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2550 > URL: https://issues.jboss.org/browse/JBTM-2550 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Affects Versions: 5.2.8.Final > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 4.17.33, 5.2.10.Final > > > This exception happens with using the IBM MQ rar in the wildfly. > com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR > We can catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 6 07:25:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 6 May 2016 07:25:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2669) Refactor "impl" package in compensations module to "internal" In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2669: ------------------------------------- Summary: Refactor "impl" package in compensations module to "internal" Key: JBTM-2669 URL: https://issues.jboss.org/browse/JBTM-2669 Project: JBoss Transaction Manager Issue Type: Bug Components: Compensations 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 Mon May 9 08:44:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 9 May 2016 08:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2648) Failing .Narayana qa testcase crashrecovery12 method CrashRecovery12_Test03 when journal object store is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2648: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Failing .Narayana qa testcase crashrecovery12 method CrashRecovery12_Test03 when journal object store is used > ------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2648 > URL: https://issues.jboss.org/browse/JBTM-2648 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.14.Final > Reporter: Ond?ej Chaloupka > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: TEST-org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12.txt, testoutput.zip > > > When using journal object store (amq) then we experience failues of test {{crashrecovery12 CrashRecovery12_Test03}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 9 08:44:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 9 May 2016 08:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2650) Remove typo from BAControler interface and its implementations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2650: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove typo from BAControler interface and its implementations > -------------------------------------------------------------- > > Key: JBTM-2650 > URL: https://issues.jboss.org/browse/JBTM-2650 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Fix typos in BAControler, LocalBAControler, and RemoteBAControler names. Also variables when those classes are used also have typos. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 10 09:04:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 10 May 2016 09:04:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2668) Entity manager does not join transaction properly in JTA and Hibernate quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2668 started by Gytis Trikleris. --------------------------------------------- > Entity manager does not join transaction properly in JTA and Hibernate quickstart > --------------------------------------------------------------------------------- > > Key: JBTM-2668 > URL: https://issues.jboss.org/browse/JBTM-2668 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > To reproduce begin transaction at the start of TestCase.testJpa method and roll it back just before assertion. During the abort in BasicAction pending list is empty and no resources are rolled back. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 10 11:00:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 10 May 2016 11:00:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2670) Update raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2670: ------------------------------------- Summary: Update raw-xts-api-demo quickstart Key: JBTM-2670 URL: https://issues.jboss.org/browse/JBTM-2670 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator, XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next raw-xts-api-demo quickstart has out of date readme and dependencies. It doesn't work with current WildFly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 10 11:01:00 2016 From: issues at jboss.org (Jive JIRA Integration (JIRA)) Date: Tue, 10 May 2016 11:01:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2670) Update raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jive JIRA Integration updated JBTM-2670: ---------------------------------------- Forum Reference: https://developer.jboss.org/message/955897#955897 > Update raw-xts-api-demo quickstart > ---------------------------------- > > Key: JBTM-2670 > URL: https://issues.jboss.org/browse/JBTM-2670 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > raw-xts-api-demo quickstart has out of date readme and dependencies. It doesn't work with current WildFly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 11 03:36:00 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 11 May 2016 03:36:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2636) Backport deferred exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203581#comment-13203581 ] RH Bugzilla Integration commented on JBTM-2636: ----------------------------------------------- Ji?? B?lek changed the Status of [bug 1316270|https://bugzilla.redhat.com/show_bug.cgi?id=1316270] from ON_QA to VERIFIED > Backport deferred exceptions > ---------------------------- > > Key: JBTM-2636 > URL: https://issues.jboss.org/browse/JBTM-2636 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.32 > > > Includes > * JBTM-2120 > * https://github.com/jbosstm/narayana/pull/598/commits -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 11 03:36:00 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 11 May 2016 03:36: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:comment-tabpanel&focusedCommentId=13203582#comment-13203582 ] RH Bugzilla Integration commented on JBTM-2120: ----------------------------------------------- Ji?? B?lek changed the Status of [bug 1316270|https://bugzilla.redhat.com/show_bug.cgi?id=1316270] from ON_QA to VERIFIED > 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 May 11 04:47:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 11 May 2016 04:47:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2671) TXBridge quickstart execution steps are inaccurate In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2671: ------------------------------------- Summary: TXBridge quickstart execution steps are inaccurate Key: JBTM-2671 URL: https://issues.jboss.org/browse/JBTM-2671 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator, TxBridge, XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next Execution steps for both wsat-jta-multi_hop and wsat-jta-multi_service quickstarts tells to start WildFly in one console and then execute the test with managed Arquillian container. Which is obviously wrong. We shouldn't suggest to start the container manually, but only use the managed container. Also, it might be good to not redirect output to the file, but instead print it directly and use egrep as showed in the current execution steps. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 11 09:48:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 11 May 2016 09:48:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2668) Entity manager does not join transaction properly in JTA and Hibernate quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #163 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Entity manager does not join transaction properly in JTA and Hibernate quickstart > --------------------------------------------------------------------------------- > > Key: JBTM-2668 > URL: https://issues.jboss.org/browse/JBTM-2668 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > To reproduce begin transaction at the start of TestCase.testJpa method and roll it back just before assertion. During the abort in BasicAction pending list is empty and no resources are rolled back. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 12 00:21:00 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 12 May 2016 00:21:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2575) When checking for orphaned subordinate transactions in the middle of a tree branches that are eligible for orphan detection will be rolled back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204101#comment-13204101 ] RH Bugzilla Integration commented on JBTM-2575: ----------------------------------------------- Ondrej Chaloupka changed the Status of [bug 1289386|https://bugzilla.redhat.com/show_bug.cgi?id=1289386] from ON_QA to VERIFIED > When checking for orphaned subordinate transactions in the middle of a tree branches that are eligible for orphan detection will be rolled back > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2575 > URL: https://issues.jboss.org/browse/JBTM-2575 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 4.17.31, 5.2.9.Final > > > There is a check in the subordinate orphan detection that not only checks for matching gtrid but also for matching subordinate name. This will not match correctly for an intermediary node. E.g. > a->b b->c > When b scans c the xid it gets back will have subordinate name of c, b will look in its object store and match the subordinate on gtrid but the subordinate node ID in b subordinateatomicaction will be "b". > This check is actually superfluous anyway. We already know that the Xid returned from c was for b because of transport level checks. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 16 07:39:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 16 May 2016 07:39:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2655) QA suite failure: TestGroup_txcore_recovery (JDBC store) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2655: -------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Tom Jenkinson Resolution: Done > QA suite failure: TestGroup_txcore_recovery (JDBC store) > -------------------------------------------------------- > > Key: JBTM-2655 > URL: https://issues.jboss.org/browse/JBTM-2655 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-jdbcobjectstore/191/DB_TYPE=db2,jdk=jdk8.latest,slave=linux/consoleFull -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 17 06:03:00 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 17 May 2016 06:03:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2579) Throw XAException in XATerminator::commit if a wrapped resource fails transiently In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238495#comment-13238495 ] RH Bugzilla Integration commented on JBTM-2579: ----------------------------------------------- Ondrej Chaloupka changed the Status of [bug 1325726|https://bugzilla.redhat.com/show_bug.cgi?id=1325726] from ON_QA to VERIFIED > Throw XAException in XATerminator::commit if a wrapped resource fails transiently > --------------------------------------------------------------------------------- > > Key: JBTM-2579 > URL: https://issues.jboss.org/browse/JBTM-2579 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.31, 5.2.9.Final > > > It is possible for a resource that we are wrapping to return say XA_RETRY or XA_RMFAIL and therefore end up in the BasicAction failed list. However there is no error returned from commit in this circumstance as the recovery manager should ensure a consistent outcome. > The reason this becomes a problem for JTA and XATerminator in particular is that as no error is returned a parent coordinator will assume the branch completed successfully. In the future when it calls XATerminator::recover though this branch will be returned and detected as an orphan. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 03:27:00 2016 From: issues at jboss.org (Bartosz Baranowski (JIRA)) Date: Wed, 18 May 2016 03:27:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2672) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: Bartosz Baranowski created JBTM-2672: ---------------------------------------- Summary: Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection Key: JBTM-2672 URL: https://issues.jboss.org/browse/JBTM-2672 Project: JBoss Transaction Manager Issue Type: Bug Components: Recovery Affects Versions: 5.2.14.Final Reporter: Bartosz Baranowski Fix For: 5.2.17.Final Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 03:28:00 2016 From: issues at jboss.org (Bartosz Baranowski (JIRA)) Date: Wed, 18 May 2016 03:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2672) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Baranowski updated JBTM-2672: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1011 > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2672 > URL: https://issues.jboss.org/browse/JBTM-2672 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.2.14.Final > Reporter: Bartosz Baranowski > Fix For: 5.2.17.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 03:28:00 2016 From: issues at jboss.org (Bartosz Baranowski (JIRA)) Date: Wed, 18 May 2016 03:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2672) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2672?focusedWorklogId=12435911&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-12435911 ] Bartosz Baranowski logged work on JBTM-2672: -------------------------------------------- Author: Bartosz Baranowski Created on: 18/May/16 3:27 AM Start Date: 18/May/16 3:27 AM Worklog Time Spent: 4 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 4 hours Worklog Id: (was: 12435911) > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2672 > URL: https://issues.jboss.org/browse/JBTM-2672 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.2.14.Final > Reporter: Bartosz Baranowski > Fix For: 5.2.17.Final > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 03:31:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 May 2016 03:31:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2583: --------------------------------- > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 03:31:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 May 2016 03:31:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2583: -------------------------------- Fix Version/s: 5.2.17.Final > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.17.Final, 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 03:31:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 May 2016 03:31:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2583. ------------------------------- Resolution: Done > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.17.Final, 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 03:31:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 May 2016 03:31:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2672) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2672: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2672 > URL: https://issues.jboss.org/browse/JBTM-2672 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.2.14.Final > Reporter: Bartosz Baranowski > Fix For: 5.2.17.Final > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 03:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 May 2016 03:32:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2583: --------------------------------- > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.17.Final, 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 03:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 May 2016 03:32:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2583: -------------------------------- Fix Version/s: (was: 5.2.17.Final) > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 03:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 May 2016 03:32:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2583. ------------------------------- Resolution: Done > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 05:47:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 18 May 2016 05:47:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2670) Update raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2670 started by Gytis Trikleris. --------------------------------------------- > Update raw-xts-api-demo quickstart > ---------------------------------- > > Key: JBTM-2670 > URL: https://issues.jboss.org/browse/JBTM-2670 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > raw-xts-api-demo quickstart has out of date readme and dependencies. It doesn't work with current WildFly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 06:55:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 May 2016 06:55:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2673) ThreadUtil getThreadId(Thread) ignores argument In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2673: ----------------------------------- Summary: ThreadUtil getThreadId(Thread) ignores argument Key: JBTM-2673 URL: https://issues.jboss.org/browse/JBTM-2673 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next During investigation of https://developer.jboss.org/thread/269784?start=15&tstart=0 it was observed that the ThreadUtil implementation does not use the Thread argument and simply uses a ThreadLocal: https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/utils/ThreadUtil.java#L51 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 06:57:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 May 2016 06:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2673) ThreadUtil getThreadId(Thread) ignores argument In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239315#comment-13239315 ] Tom Jenkinson commented on JBTM-2673: ------------------------------------- Analysis shows that our usage of this internally (that doesn't use Thread.currentThread() as the argument) is: 1. BasicAction::addChildThread(Thread) which is a public method but is unused by ourselves 2. BasicAction::removeAllChildThreads - this is called by the reaper but because typical usage is via JTA which requires the app thread to disassociate we have not had reports on this > ThreadUtil getThreadId(Thread) ignores argument > ----------------------------------------------- > > Key: JBTM-2673 > URL: https://issues.jboss.org/browse/JBTM-2673 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > During investigation of https://developer.jboss.org/thread/269784?start=15&tstart=0 it was observed that the ThreadUtil implementation does not use the Thread argument and simply uses a ThreadLocal: > https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/utils/ThreadUtil.java#L51 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 10:42:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 18 May 2016 10:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2670) Update raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #165 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Update raw-xts-api-demo quickstart > ---------------------------------- > > Key: JBTM-2670 > URL: https://issues.jboss.org/browse/JBTM-2670 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > raw-xts-api-demo quickstart has out of date readme and dependencies. It doesn't work with current WildFly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 18 15:31:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 18 May 2016 15:31:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2670) Update raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2670: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update raw-xts-api-demo quickstart > ---------------------------------- > > Key: JBTM-2670 > URL: https://issues.jboss.org/browse/JBTM-2670 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > raw-xts-api-demo quickstart has out of date readme and dependencies. It doesn't work with current WildFly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 19 09:19:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Thu, 19 May 2016 09:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2674) JTA does not set transaction timeout for XAResource for propagated transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2674: ---------------------------------- Affects Version/s: 5.2.16.Final > JTA does not set transaction timeout for XAResource for propagated transactions > ------------------------------------------------------------------------------- > > Key: JBTM-2674 > URL: https://issues.jboss.org/browse/JBTM-2674 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > > I can see a fact that transaction timeout is not provided by subordinate transaction when passed by ejb remote call when JTA transaction are used. > Even when transaction timeout is defined (it could be seen that timeout is used when xaresources is used on client) the server where transaction is propagated shows xa resources using the default timeou value. > Client server (caller) - timeout is _6 seconds_ > {code} > 2016-05-19 11:50:51,461 TRACE [com.arjuna.ats.jta] (default task-18) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:483, xid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, timeout:6, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-483 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 7b44816f >, record id=0:ffff7f000001:57a802d4:573d8c57:21 > {code} > Server (callee) - uses timeout _0 seconds_ > {code} > 2016-05-19 11:50:39,374 TRACE [com.arjuna.ats.jta] (default task-12) XAResourceRecord.topLevelPrepare for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:502, xid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, timeout:0, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-502 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 4f35ed3f >, record id=0:ffff7f000001:3b603de1:573d8c5f:18 > {code} > Scenario that I'm running is > # enlist jms xa resource on client > # call to second server, it means enlist ejb remoting xa resource to transaction > # enlist test xa on server > # enlist jms xa resource on server > # enlist test xa on client > # starting 2PC > # prepare jms xa resource on server > # prepare ejb remoting xa resource on server > # prepare test xa resource on client > # transaction timeout is hit > # if underlying jms resource timeouts then XAResource.prepare call fails with XAER_NOTA and the whole transaction is rolled back > # > _(attaching server.log files for EAP 7.0.0/Narayana 5.2.16.Final where jbossts is caller and jbossts2 is callee)_ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 19 09:19:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Thu, 19 May 2016 09:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2674) JTA does not set transaction timeout for XAResource for propagated transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka reassigned JBTM-2674: ------------------------------------- Assignee: Tom Jenkinson > JTA does not set transaction timeout for XAResource for propagated transactions > ------------------------------------------------------------------------------- > > Key: JBTM-2674 > URL: https://issues.jboss.org/browse/JBTM-2674 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > > I can see a fact that transaction timeout is not provided by subordinate transaction when passed by ejb remote call when JTA transaction are used. > Even when transaction timeout is defined (it could be seen that timeout is used when xaresources is used on client) the server where transaction is propagated shows xa resources using the default timeou value. > Client server (caller) - timeout is _6 seconds_ > {code} > 2016-05-19 11:50:51,461 TRACE [com.arjuna.ats.jta] (default task-18) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:483, xid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, timeout:6, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-483 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 7b44816f >, record id=0:ffff7f000001:57a802d4:573d8c57:21 > {code} > Server (callee) - uses timeout _0 seconds_ > {code} > 2016-05-19 11:50:39,374 TRACE [com.arjuna.ats.jta] (default task-12) XAResourceRecord.topLevelPrepare for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:502, xid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, timeout:0, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-502 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 4f35ed3f >, record id=0:ffff7f000001:3b603de1:573d8c5f:18 > {code} > Scenario that I'm running is > # enlist jms xa resource on client > # call to second server, it means enlist ejb remoting xa resource to transaction > # enlist test xa on server > # enlist jms xa resource on server > # enlist test xa on client > # starting 2PC > # prepare jms xa resource on server > # prepare ejb remoting xa resource on server > # prepare test xa resource on client > # transaction timeout is hit > # if underlying jms resource timeouts then XAResource.prepare call fails with XAER_NOTA and the whole transaction is rolled back > # > _(attaching server.log files for EAP 7.0.0/Narayana 5.2.16.Final where jbossts is caller and jbossts2 is callee)_ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 19 09:19:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Thu, 19 May 2016 09:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2674) JTA does not set transaction timeout for XAResource for propagated transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2674: ---------------------------------- Component/s: JTA > JTA does not set transaction timeout for XAResource for propagated transactions > ------------------------------------------------------------------------------- > > Key: JBTM-2674 > URL: https://issues.jboss.org/browse/JBTM-2674 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > > I can see a fact that transaction timeout is not provided by subordinate transaction when passed by ejb remote call when JTA transaction are used. > Even when transaction timeout is defined (it could be seen that timeout is used when xaresources is used on client) the server where transaction is propagated shows xa resources using the default timeou value. > Client server (caller) - timeout is _6 seconds_ > {code} > 2016-05-19 11:50:51,461 TRACE [com.arjuna.ats.jta] (default task-18) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:483, xid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, timeout:6, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-483 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 7b44816f >, record id=0:ffff7f000001:57a802d4:573d8c57:21 > {code} > Server (callee) - uses timeout _0 seconds_ > {code} > 2016-05-19 11:50:39,374 TRACE [com.arjuna.ats.jta] (default task-12) XAResourceRecord.topLevelPrepare for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:502, xid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, timeout:0, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-502 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 4f35ed3f >, record id=0:ffff7f000001:3b603de1:573d8c5f:18 > {code} > Scenario that I'm running is > # enlist jms xa resource on client > # call to second server, it means enlist ejb remoting xa resource to transaction > # enlist test xa on server > # enlist jms xa resource on server > # enlist test xa on client > # starting 2PC > # prepare jms xa resource on server > # prepare ejb remoting xa resource on server > # prepare test xa resource on client > # transaction timeout is hit > # if underlying jms resource timeouts then XAResource.prepare call fails with XAER_NOTA and the whole transaction is rolled back > # > _(attaching server.log files for EAP 7.0.0/Narayana 5.2.16.Final where jbossts is caller and jbossts2 is callee)_ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 19 09:19:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Thu, 19 May 2016 09:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2674) JTA does not set transaction timeout for XAResource for propagated transactions In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-2674: ------------------------------------- Summary: JTA does not set transaction timeout for XAResource for propagated transactions Key: JBTM-2674 URL: https://issues.jboss.org/browse/JBTM-2674 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Ondra Chaloupka I can see a fact that transaction timeout is not provided by subordinate transaction when passed by ejb remote call when JTA transaction are used. Even when transaction timeout is defined (it could be seen that timeout is used when xaresources is used on client) the server where transaction is propagated shows xa resources using the default timeou value. Client server (caller) - timeout is _6 seconds_ {code} 2016-05-19 11:50:51,461 TRACE [com.arjuna.ats.jta] (default task-18) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:483, xid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, timeout:6, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-483 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 7b44816f >, record id=0:ffff7f000001:57a802d4:573d8c57:21 {code} Server (callee) - uses timeout _0 seconds_ {code} 2016-05-19 11:50:39,374 TRACE [com.arjuna.ats.jta] (default task-12) XAResourceRecord.topLevelPrepare for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:502, xid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, timeout:0, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-502 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 4f35ed3f >, record id=0:ffff7f000001:3b603de1:573d8c5f:18 {code} Scenario that I'm running is # enlist jms xa resource on client # call to second server, it means enlist ejb remoting xa resource to transaction # enlist test xa on server # enlist jms xa resource on server # enlist test xa on client # starting 2PC # prepare jms xa resource on server # prepare ejb remoting xa resource on server # prepare test xa resource on client # transaction timeout is hit # if underlying jms resource timeouts then XAResource.prepare call fails with XAER_NOTA and the whole transaction is rolled back # _(attaching server.log files for EAP 7.0.0/Narayana 5.2.16.Final where jbossts is caller and jbossts2 is callee)_ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 19 11:11:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 19 May 2016 11:11:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2668) Entity manager does not join transaction properly in JTA and Hibernate quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2668 started by Gytis Trikleris. --------------------------------------------- > Entity manager does not join transaction properly in JTA and Hibernate quickstart > --------------------------------------------------------------------------------- > > Key: JBTM-2668 > URL: https://issues.jboss.org/browse/JBTM-2668 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > To reproduce begin transaction at the start of TestCase.testJpa method and roll it back just before assertion. During the abort in BasicAction pending list is empty and no resources are rolled back. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 03:43:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 May 2016 03:43:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2646) Include a quickstart showing a command line equivalent of the wildfly transaction console In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2646: -------------------------------- Priority: Minor (was: Blocker) > Include a quickstart showing a command line equivalent of the wildfly transaction console > ----------------------------------------------------------------------------------------- > > Key: JBTM-2646 > URL: https://issues.jboss.org/browse/JBTM-2646 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tooling > Affects Versions: 5.3.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Provide a standalone tool (in the form of a quickstart) that duplicates the functionality of the wildfly transactions console. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 05:50:00 2016 From: issues at jboss.org (Ivo Studensky (JIRA)) Date: Fri, 20 May 2016 05:50:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation In-Reply-To: References: Message-ID: Ivo Studensky created JBTM-2675: ----------------------------------- Summary: Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation Key: JBTM-2675 URL: https://issues.jboss.org/browse/JBTM-2675 Project: JBoss Transaction Manager Issue Type: Bug Components: XTS Affects Versions: 5.3.2.Final, 5.2.17.Final Reporter: Ivo Studensky Assignee: Ivo Studensky ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 05:58:00 2016 From: issues at jboss.org (Ivo Studensky (JIRA)) Date: Fri, 20 May 2016 05:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ivo Studensky created pull request #1012 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2675 > URL: https://issues.jboss.org/browse/JBTM-2675 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > > ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 06:07:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 20 May 2016 06:07:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2293) Create a docker file to make web page update easier In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2293. --------------------------------- Resolution: Rejected > Create a docker file to make web page update easier > --------------------------------------------------- > > Key: JBTM-2293 > URL: https://issues.jboss.org/browse/JBTM-2293 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Cloud > Reporter: Gytis Trikleris > > Awestruct recuires quite a few dependencies to build a web page. Although it is not hard to install them manually, it is time consuming. It would be much easier to use docker for this. > This docker file is a good start: https://github.com/goldmann/dockerfiles/tree/master/awestruct -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 06:28:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 20 May 2016 06:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2675: ---------------------------------- Fix Version/s: 5.next > Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2675 > URL: https://issues.jboss.org/browse/JBTM-2675 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 4.17.34, 5.next > > > ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 06:28:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 20 May 2016 06:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2675: ---------------------------------- Fix Version/s: 4.17.34 > Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2675 > URL: https://issues.jboss.org/browse/JBTM-2675 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 4.17.34, 5.next > > > ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 06:30:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 May 2016 06:30:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2675: -------------------------------- Fix Version/s: 5.2.18.Final > Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2675 > URL: https://issues.jboss.org/browse/JBTM-2675 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 4.17.34, 5.2.18.Final, 5.next > > > ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 06:35:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 20 May 2016 06:35:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2675: ---------------------------------- Fix Version/s: (was: 4.17.34) > Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2675 > URL: https://issues.jboss.org/browse/JBTM-2675 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 5.2.18.Final, 5.next > > > ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 10:01:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 May 2016 10:01:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2675: -------------------------------- Fix Version/s: (was: 5.2.18.Final) > Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2675 > URL: https://issues.jboss.org/browse/JBTM-2675 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 5.next > > > ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 10:09:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 20 May 2016 10:09:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Hibernate tries to close connection in afterCompletion but TransactionDriver does not allow that In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2676: ------------------------------------- Summary: Hibernate tries to close connection in afterCompletion but TransactionDriver does not allow that Key: JBTM-2676 URL: https://issues.jboss.org/browse/JBTM-2676 Project: JBoss Transaction Manager Issue Type: Bug Components: Transactional Driver Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 10:12:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 May 2016 10:12:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2676: -------------------------------- Summary: Allow TransactionalDriver connection.close() in afterCompletion (was: Hibernate tries to close connection in afterCompletion but TransactionDriver does not allow that) > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 10:13:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 20 May 2016 10:13:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2668) Entity manager does not join transaction properly in JTA and Hibernate quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #166 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Entity manager does not join transaction properly in JTA and Hibernate quickstart > --------------------------------------------------------------------------------- > > Key: JBTM-2668 > URL: https://issues.jboss.org/browse/JBTM-2668 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > To reproduce begin transaction at the start of TestCase.testJpa method and roll it back just before assertion. During the abort in BasicAction pending list is empty and no resources are rolled back. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri May 20 10:30:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 20 May 2016 10:30:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2675: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2675 > URL: https://issues.jboss.org/browse/JBTM-2675 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 5.next > > > ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 23 04:31:00 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 23 May 2016 04:31:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2579) Throw XAException in XATerminator::commit if a wrapped resource fails transiently In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240963#comment-13240963 ] RH Bugzilla Integration commented on JBTM-2579: ----------------------------------------------- Radovan Netuka changed the Status of [bug 1329142|https://bugzilla.redhat.com/show_bug.cgi?id=1329142] from NEW to ASSIGNED > Throw XAException in XATerminator::commit if a wrapped resource fails transiently > --------------------------------------------------------------------------------- > > Key: JBTM-2579 > URL: https://issues.jboss.org/browse/JBTM-2579 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.31, 5.2.9.Final > > > It is possible for a resource that we are wrapping to return say XA_RETRY or XA_RMFAIL and therefore end up in the BasicAction failed list. However there is no error returned from commit in this circumstance as the recovery manager should ensure a consistent outcome. > The reason this becomes a problem for JTA and XATerminator in particular is that as no error is returned a parent coordinator will assume the branch completed successfully. In the future when it calls XATerminator::recover though this branch will be returned and detected as an orphan. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 23 05:37:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 23 May 2016 05:37:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-1107: ---------------------------------- Fix Version/s: 5.next (was: 5.later) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Compensations > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers would be invoked in case of the system crash. > In addition, @CompensationScoped beans should be available during the recovery. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 23 06:02:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 23 May 2016 06:02:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2634) Create Narayana Spring Boot starter quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2634: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create Narayana Spring Boot starter quickstart > ---------------------------------------------- > > Key: JBTM-2634 > URL: https://issues.jboss.org/browse/JBTM-2634 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Create a demonstrator application for Narayana Spring Boot starter before raising pull request to Spring. This would allow to make a better review of the Narayana Spring Boot integration on the forum. > Quickstart should have a simple example of JTA and crash recovery. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 24 05:28:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 24 May 2016 05:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-2677: ------------------------------------- Summary: XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used Key: JBTM-2677 URL: https://issues.jboss.org/browse/JBTM-2677 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Ondra Chaloupka I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. The scenario is following: There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. # RAR is deployed # RAR opens a java socket where listens for message # MDB of TestResourceMessageListener is deployed # test client sends prepare command # test client sends commit command # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL # test client receives error code XAER_RMFAIL # test client sends recover command # test client receives number of in-doubt xid - which is one # test client sends rollback command # XATerminator calls rollback on the in-doubt xid # expecting TestXAResource.rollback would be called After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). [1] {code} 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 24 05:29:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 24 May 2016 05:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka reassigned JBTM-2677: ------------------------------------- Assignee: Tom Jenkinson > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 24 05:29:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 24 May 2016 05:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2677: ---------------------------------- Affects Version/s: 5.2.16.Final > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 24 05:29:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 24 May 2016 05:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2677: ---------------------------------- Component/s: JTS > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 24 08:54:00 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 24 May 2016 08:54:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2579) Throw XAException in XATerminator::commit if a wrapped resource fails transiently In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241697#comment-13241697 ] RH Bugzilla Integration commented on JBTM-2579: ----------------------------------------------- Radovan Netuka changed the Status of [bug 1329142|https://bugzilla.redhat.com/show_bug.cgi?id=1329142] from ASSIGNED to MODIFIED > Throw XAException in XATerminator::commit if a wrapped resource fails transiently > --------------------------------------------------------------------------------- > > Key: JBTM-2579 > URL: https://issues.jboss.org/browse/JBTM-2579 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.31, 5.2.9.Final > > > It is possible for a resource that we are wrapping to return say XA_RETRY or XA_RMFAIL and therefore end up in the BasicAction failed list. However there is no error returned from commit in this circumstance as the recovery manager should ensure a consistent outcome. > The reason this becomes a problem for JTA and XATerminator in particular is that as no error is returned a parent coordinator will assume the branch completed successfully. In the future when it calls XATerminator::recover though this branch will be returned and detected as an orphan. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 24 10:08:01 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 24 May 2016 10:08:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2678) @TxLogged annotation not working In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2678: ------------------------------------- Summary: @TxLogged annotation not working Key: JBTM-2678 URL: https://issues.jboss.org/browse/JBTM-2678 Project: JBoss Transaction Manager Issue Type: Bug Components: Compensations Reporter: Gytis Trikleris Fix For: 5.next @TxLogged annotation does not work in Compensations framework. All it's assertions were removed from the tests with this commit: https://github.com/jbosstm/narayana/commit/efd15eeb080c6b6338f3658c4aa58158c5e3ac6a#diff-a01554d0172e1da7703c5134820edb6aL124 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 24 10:08:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 24 May 2016 10:08:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2678) @TxLogged annotation not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris reassigned JBTM-2678: ------------------------------------- Assignee: Gytis Trikleris > @TxLogged annotation not working > -------------------------------- > > Key: JBTM-2678 > URL: https://issues.jboss.org/browse/JBTM-2678 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > @TxLogged annotation does not work in Compensations framework. All it's assertions were removed from the tests with this commit: https://github.com/jbosstm/narayana/commit/efd15eeb080c6b6338f3658c4aa58158c5e3ac6a#diff-a01554d0172e1da7703c5134820edb6aL124 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 24 10:08:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 24 May 2016 10:08:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2678) @TxLogged annotation does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2678: ---------------------------------- Summary: @TxLogged annotation does not work (was: @TxLogged annotation not working) > @TxLogged annotation does not work > ---------------------------------- > > Key: JBTM-2678 > URL: https://issues.jboss.org/browse/JBTM-2678 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > @TxLogged annotation does not work in Compensations framework. All it's assertions were removed from the tests with this commit: https://github.com/jbosstm/narayana/commit/efd15eeb080c6b6338f3658c4aa58158c5e3ac6a#diff-a01554d0172e1da7703c5134820edb6aL124 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 24 13:47:00 2016 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Tue, 24 May 2016 13:47:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Robinson updated JBTM-1107: -------------------------------- Reporter: Tom Jenkinson (was: Paul Robinson) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Compensations > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers would be invoked in case of the system crash. > In addition, @CompensationScoped beans should be available during the recovery. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 24 13:58:00 2016 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Tue, 24 May 2016 13:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-928) ATParticipantCrashAndRecover Crash Recovery test needs completing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Robinson updated JBTM-928: ------------------------------- Reporter: Tom Jenkinson (was: Paul Robinson) > ATParticipantCrashAndRecover Crash Recovery test needs completing > ----------------------------------------------------------------- > > Key: JBTM-928 > URL: https://issues.jboss.org/browse/JBTM-928 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing, XTS > Affects Versions: 4.17.0.M1/5.0.0.M1 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > > This test was not completed due to a problem with JBossWS that prevented the test case from being possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 24 13:58:00 2016 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Tue, 24 May 2016 13:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2221) Remove old TXFramework API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Robinson updated JBTM-2221: -------------------------------- Reporter: Tom Jenkinson (was: Paul Robinson) > Remove old TXFramework API > -------------------------- > > Key: JBTM-2221 > URL: https://issues.jboss.org/browse/JBTM-2221 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 6.later > > > This is now replaced by the CDI based Compensations API. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 24 13:58:00 2016 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Tue, 24 May 2016 13:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-987) Document Compensations API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Robinson updated JBTM-987: ------------------------------- Reporter: Tom Jenkinson (was: Paul Robinson) > Document Compensations API > -------------------------- > > Key: JBTM-987 > URL: https://issues.jboss.org/browse/JBTM-987 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation, TXFramework > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Priority: Optional > Labels: TXFramework > Fix For: 5.later > > > Should cover all existing features and provide a skeleton for the final document. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 25 07:06:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 25 May 2016 07:06:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-2679: ------------------------------------- Summary: Artifact of narayana-full does not contain bits of jbossxts.jar Key: JBTM-2679 URL: https://issues.jboss.org/browse/JBTM-2679 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Affects Versions: 5.2.17.Final Reporter: Ondra Chaloupka Assignee: Tom Jenkinson Priority: Minor Zip file `narayana-full-${VERSION}-bin.zip` under directory `narayana-full/target` which is created from the built artifacts does not contains bits of `jbossxts.jar`. The artifact for xts with the filename `jbossxts.jar` is available but contains the same bits as it's counterpart `-api` jar file. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 25 07:09:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 25 May 2016 07:09:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2679: ---------------------------------- Description: Zip file {{narayana-full-${VERSION}-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. (was: Zip file `narayana-full-${VERSION}-bin.zip` under directory `narayana-full/target` which is created from the built artifacts does not contains bits of `jbossxts.jar`. The artifact for xts with the filename `jbossxts.jar` is available but contains the same bits as it's counterpart `-api` jar file.) > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Priority: Minor > > Zip file {{narayana-full-${VERSION}-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 25 07:09:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 25 May 2016 07:09:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2679: ---------------------------------- Description: Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. (was: Zip file {{narayana-full-${VERSION}-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file.) > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Priority: Minor > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 25 07:11:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 25 May 2016 07:11:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242414#comment-13242414 ] Ondra Chaloupka commented on JBTM-2679: --------------------------------------- I think this is an issue of assembly plugin which does not cope well with statement {{api}}. I haven't found some relevant note/issue on this for maven assembly plugin so I'm not sure. The solution or workaround is to change order of artifacts as specified in {{narayana-full/pom.xml}}. When the first is artifact without classifier, then it works fine. As initial version defines artifact with api classifier as first one then the trouble described here occurs. > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Priority: Minor > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 25 07:14:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 25 May 2016 07:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1014 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Priority: Minor > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 25 07:14:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 25 May 2016 07:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka reassigned JBTM-2679: ------------------------------------- Assignee: Ondra Chaloupka (was: Tom Jenkinson) > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 25 07:16:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 25 May 2016 07:16:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242418#comment-13242418 ] Ondra Chaloupka commented on JBTM-2679: --------------------------------------- [~tomjenkinson]: assigning to me as having that simple "fix". What do you think is ok that way. (_tried with assembly plugin in version 2.6 - instead of used 2.5.5 - and the issue stays)_ > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 25 07:16:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 25 May 2016 07:16:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242418#comment-13242418 ] Ondra Chaloupka edited comment on JBTM-2679 at 5/25/16 7:15 AM: ---------------------------------------------------------------- [~tomjenkinson]: assigning to me as having that simple "fix". What do you think is ok that way? (_tried with assembly plugin in version 2.6 - instead of used 2.5.5 - and the issue stays)_ was (Author: ochaloup): [~tomjenkinson]: assigning to me as having that simple "fix". What do you think is ok that way. (_tried with assembly plugin in version 2.6 - instead of used 2.5.5 - and the issue stays)_ > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed May 25 07:42:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 25 May 2016 07:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2680) Document compensations API In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2680: ------------------------------------- Summary: Document compensations API Key: JBTM-2680 URL: https://issues.jboss.org/browse/JBTM-2680 Project: JBoss Transaction Manager Issue Type: Task Components: Compensations Reporter: Gytis Trikleris Assignee: Gytis Trikleris There is no documentation for compensations API in our docs. Most of the things are covered in the quickstarts and blog, but adding something to the docs would be good too. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 26 08:57:00 2016 From: issues at jboss.org (Jesper Pedersen (JIRA)) Date: Thu, 26 May 2016 08:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2681) IllegalStateExceptions should contain the stack trace In-Reply-To: References: Message-ID: Jesper Pedersen created JBTM-2681: ------------------------------------- Summary: IllegalStateExceptions should contain the stack trace Key: JBTM-2681 URL: https://issues.jboss.org/browse/JBTM-2681 Project: JBoss Transaction Manager Issue Type: Enhancement Reporter: Jesper Pedersen F.ex. in a place like https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/objectstore/StoreManager.java#L43 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu May 26 11:29:00 2016 From: issues at jboss.org (Jesper Pedersen (JIRA)) Date: Thu, 26 May 2016 11:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2681) IllegalStateExceptions should contain the stack trace In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243464#comment-13243464 ] Jesper Pedersen commented on JBTM-2681: --------------------------------------- In the end this was the hidden dependency I was looking for {noformat} at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:153) at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:102) at com.arjuna.ats.arjuna.recovery.ActionStatusService.(ActionStatusService.java:64) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at java.lang.Class.newInstance(Class.java:442) at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.start(TransactionStatusManager.java:125) at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.(TransactionStatusManager.java:58) at com.arjuna.ats.arjuna.coordinator.TxControl.createTransactionStatusManager(TxControl.java:188) at com.arjuna.ats.arjuna.coordinator.TxControl.(TxControl.java:264) at java.lang.Class.forName0(Native Method) {noformat} > IllegalStateExceptions should contain the stack trace > ----------------------------------------------------- > > Key: JBTM-2681 > URL: https://issues.jboss.org/browse/JBTM-2681 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Jesper Pedersen > > F.ex. in a place like > https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/objectstore/StoreManager.java#L43 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon May 30 05:34:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 30 May 2016 05:34:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2622) Implement possible new compensations api In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2622: ---------------------------------- Summary: Implement possible new compensations api (was: Implement possible new compensations api from the meeting) > Implement possible new compensations api > ---------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 09:27:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 31 May 2016 09:27:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2682) RecoveryIntegrationTestCase.testCrashBeforeCommit did not recover In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2682: ------------------------------------- Summary: RecoveryIntegrationTestCase.testCrashBeforeCommit did not recover Key: JBTM-2682 URL: https://issues.jboss.org/browse/JBTM-2682 Project: JBoss Transaction Manager Issue Type: Bug Components: REST Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.later {code} ------------------------------------------------------------------------------- Test set: org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase ------------------------------------------------------------------------------- Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 191.234 sec <<< FAILURE! - in org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase testCrashBeforeCommit(org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase) Time elapsed: 126.558 sec <<< FAILURE! java.lang.AssertionError: Recovery failed at org.junit.Assert.fail(Assert.java:88) at org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase.testCrashBeforeCommit(RecoveryIntegrationTestCase.java:125) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 09:28:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 31 May 2016 09:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2682) RecoveryIntegrationTestCase.testCrashBeforeCommit did not recover In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2682: ---------------------------------- Description: {code} ------------------------------------------------------------------------------- Test set: org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase ------------------------------------------------------------------------------- Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 191.234 sec <<< FAILURE! - in org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase testCrashBeforeCommit(org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase) Time elapsed: 126.558 sec <<< FAILURE! java.lang.AssertionError: Recovery failed at org.junit.Assert.fail(Assert.java:88) at org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase.testCrashBeforeCommit(RecoveryIntegrationTestCase.java:125) {code} {code} javaagent:lib/byteman.jar=script:scripts/CrashBeforeCommit.btm,boot:lib/byteman.jar,listener:true, startupTimeoutInSeconds=60, serverConfig=standalone-rts.xml} May 17, 2016 7:55:38 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal WARNING: Bundles path is deprecated and no longer used. May 17, 2016 7:55:38 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, -Dorg.jboss.byteman.verbose, -Dorg.jboss.byteman.transform.all, -javaagent:lib/byteman.jar=script:scripts/CrashBeforeCommit.btm,boot:lib/byteman.jar,listener:true, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-rts.xml] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 TransformListener() : accepting requests on localhost:9091 19:55:39,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final 19:55:40,131 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final 19:55:40,513 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.2.0.CR2 "Kenny" starting 19:55:44,456 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) 19:55:44,559 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 42) WFLYCLINF0001: Activating Infinispan subsystem. 19:55:44,636 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 63) WFLYWS0002: Activating WebServices Extension 19:55:44,659 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.6.Final 19:55:44,670 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.6.Final 19:55:44,592 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 49) WFLYJSF0007: Activated the following JSF Implementations: [main] 19:55:44,619 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 61) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. 19:55:45,323 INFO [org.jboss.as.security] (ServerService Thread Pool -- 60) WFLYSEC0002: Activating Security Subsystem 19:55:45,345 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 1.3.21.Final starting 19:55:45,381 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 43) WFLYIIOP0001: Activating IIOP Subsystem 19:55:45,400 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 53) WFLYNAM0001: Activating Naming Subsystem 19:55:45,622 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final 19:55:45,580 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final 19:55:46,430 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 41) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors 19:55:46,561 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final) 19:55:46,803 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 37) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 19:55:46,967 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service 19:55:47,167 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] 19:55:47,181 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2 19:55:47,136 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] 19:55:48,041 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing. 19:55:48,132 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host. 19:55:48,116 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started 19:55:49,637 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server. 19:55:50,186 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting 19:55:50,265 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 19:55:50,400 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,435 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,436 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,436 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,437 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,440 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,440 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,442 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,443 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,445 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,446 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,447 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,447 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,456 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,460 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,460 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,463 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,463 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,464 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,476 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002200: Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:55:50,709 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,758 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule Kill JVM before commit in class org.jboss.narayana.rest.integration.ParticipantResource 19:55:50,786 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.narayana.rest.integration.ParticipantResource.commit(org.jboss.narayana.rest.integration.ParticipantInformation) void for rule Kill JVM before commit 19:55:50,803 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for Kill JVM before commit in class org.jboss.narayana.rest.integration.ParticipantResource 19:55:50,805 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,805 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:55:50,863 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /rest-at-coordinator 19:55:50,866 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,866 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,870 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,870 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,872 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,875 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:55:50,890 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: volatile-rest-at-participant 19:55:51,378 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/deployments 19:55:51,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: rest-at-participant 19:55:52,131 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final 19:55:52,379 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. 19:55:53,079 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] 19:55:53,163 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/paging) 19:55:53,226 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221013: Using NIO Journal 19:55:53,437 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.4.Final (Apache CXF 3.1.5) 19:55:53,576 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE 19:55:53,600 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP 19:55:53,636 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ 19:55:53,639 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP 19:55:55,441 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor 19:55:55,445 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor 19:55:55,442 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor 19:55:55,445 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor 19:55:57,287 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221007: Server is now live 19:55:57,288 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [nodeID=49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] 19:55:57,479 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA 19:55:57,585 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 19:55:57,651 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue 19:55:57,668 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 69) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory 19:55:57,669 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue jms.queue.DLQ 19:55:58,592 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-1) Resource adaptor started 19:55:58,592 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra 19:55:58,594 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] 19:55:58,594 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory 19:55:58,974 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management 19:55:58,974 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 19:55:58,975 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR2 "Kenny" started in 20406ms - Started 311 of 596 services (387 services are lazy, passive or on-demand) 19:55:59,088 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/content/be/c7e201753abfa9619059b6feac0ee41834122e/content 19:55:59,141 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") 19:55:59,446 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. 19:55:59,446 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. 19:56:00,376 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 32) WFLYUT0021: Registered web context: /test 19:56:01,492 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") May 17, 2016 7:56:02 PM org.jboss.remotingjmx.Util warnDeprecated WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. 19:56:03,832 INFO [org.hibernate.validator.internal.util.Version] (default task-2) HV000001: Hibernate Validator 5.2.4.Final 19:56:06,698 INFO [stdout] (default task-10) Rule.execute called for Kill JVM before commit_0 19:56:06,711 INFO [stdout] (default task-10) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper 19:56:06,712 INFO [stdout] (default task-10) calling activated() for helper class org.jboss.byteman.rule.helper.Helper 19:56:06,713 INFO [stdout] (default task-10) Default helper activated 19:56:06,719 INFO [stdout] (default task-10) calling installed(Kill JVM before commit) for helper classorg.jboss.byteman.rule.helper.Helper 19:56:06,719 INFO [stdout] (default task-10) Installed rule using default helper : Kill JVM before commit 19:56:06,720 INFO [stdout] (default task-10) Kill JVM before commit execute 19:56:06,724 INFO [stdout] (default task-10) rule.debug{Kill JVM before commit} : Killing JVM May 17, 2016 7:56:07 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start INFO: Manual starting of a server instance with overridden configuration. New configuration: {managementAddress=127.0.0.1, javaVmArguments=-server -Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, startupTimeoutInSeconds=60, serverConfig=standalone-rts.xml} May 17, 2016 7:56:07 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal WARNING: Bundles path is deprecated and no longer used. May 17, 2016 7:56:07 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-rts.xml] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 19:56:07,928 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final 19:56:08,509 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final 19:56:08,676 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.2.0.CR2 "Kenny" starting 19:56:14,309 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) 19:56:14,332 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final 19:56:14,341 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final 19:56:14,542 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 43) WFLYCLINF0001: Activating Infinispan subsystem. 19:56:14,582 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 64) WFLYWS0002: Activating WebServices Extension 19:56:14,588 INFO [org.jboss.as.security] (ServerService Thread Pool -- 61) WFLYSEC0002: Activating Security Subsystem 19:56:14,618 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 54) WFLYNAM0001: Activating Naming Subsystem 19:56:14,584 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 62) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. 19:56:14,779 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 50) WFLYJSF0007: Activated the following JSF Implementations: [main] 19:56:15,111 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.18.Final 19:56:15,393 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final) 19:56:15,397 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 42) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors 19:56:15,384 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final 19:56:15,364 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 44) WFLYIIOP0001: Activating IIOP Subsystem 19:56:15,482 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.21.Final starting 19:56:15,647 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service 19:56:16,045 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 38) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 19:56:16,348 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing. 19:56:16,403 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host. 19:56:16,514 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] 19:56:16,585 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] 19:56:16,675 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2 19:56:17,193 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. 19:56:18,843 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 19:56:18,844 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting 19:56:19,134 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,162 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,162 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,163 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,163 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,176 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,176 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,177 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,178 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,180 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,181 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,182 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,184 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,184 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,187 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,188 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,204 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,204 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,205 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,207 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,209 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,209 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,210 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,210 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,262 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,262 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,263 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,263 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,264 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication 19:56:19,519 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: rest-at-participant 19:56:19,524 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,528 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,528 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,540 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,540 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,541 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,547 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,550 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,550 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication 19:56:19,596 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: volatile-rest-at-participant 19:56:19,616 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,616 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,619 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,619 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,620 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,621 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,627 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,627 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication 19:56:20,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: /rest-at-coordinator 19:56:20,390 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started 19:56:20,449 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/deployments 19:56:20,462 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") 19:56:20,780 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. 19:56:21,802 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.4.Final (Apache CXF 3.1.5) 19:56:22,023 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final 19:56:22,222 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/paging) 19:56:22,251 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] 19:56:22,469 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. 19:56:22,469 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. 19:56:23,039 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221013: Using NIO Journal 19:56:23,341 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE 19:56:23,351 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP 19:56:23,364 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ 19:56:23,366 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP 19:56:23,742 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 2) WFLYUT0021: Registered web context: /test 19:56:24,236 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor 19:56:24,236 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor 19:56:24,239 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor 19:56:24,239 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor 19:56:24,359 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221007: Server is now live 19:56:24,359 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [nodeID=49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] 19:56:24,368 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 2) AMQ221003: trying to deploy queue jms.queue.DLQ 19:56:24,519 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA 19:56:24,602 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory 19:56:24,605 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue 19:56:24,608 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 69) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 19:56:24,676 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-1) Resource adaptor started 19:56:24,677 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra 19:56:24,680 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] 19:56:24,681 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory 19:56:24,730 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR2 "Kenny" started in 17840ms - Started 382 of 672 services (398 services are lazy, passive or on-demand) 19:56:26,692 INFO [org.hibernate.validator.internal.util.Version] (default task-1) HV000001: Hibernate Validator 5.2.4.Final 19:56:27,484 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:16 19:56:27,485 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 19:56:43,099 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 19:56:57,210 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 19:57:11,314 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 19:57:25,429 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 19:57:39,533 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 19:57:43,574 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: /test 19:57:43,608 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 52ms 19:57:43,832 INFO [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/content/be/c7e201753abfa9619059b6feac0ee41834122e/content 19:57:43,833 INFO [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") May 17, 2016 7:57:43 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop INFO: Manual stopping of a server instance 19:57:43,850 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout. 19:57:43,854 INFO [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown' 19:57:43,877 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory 19:57:43,877 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] 19:57:43,877 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] 19:57:43,897 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 78) AMQ151003: resource adaptor stopped 19:57:44,623 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /rest-at-coordinator 19:57:44,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: rest-at-participant 19:57:44,705 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: volatile-rest-at-participant 19:57:44,707 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0019: Host default-host stopping 19:57:44,707 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2 19:57:44,714 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 77) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 19:57:44,717 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 74) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory 19:57:44,879 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 74) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] stopped 19:57:44,880 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending 19:57:44,881 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 19:57:44,882 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.3.21.Final stopping 19:57:44,899 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.2.0.CR2 "Kenny" stopped in 43ms May 17, 2016 7:57:44 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill INFO: Hard killing of a server instance {code} was: {code} ------------------------------------------------------------------------------- Test set: org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase ------------------------------------------------------------------------------- Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 191.234 sec <<< FAILURE! - in org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase testCrashBeforeCommit(org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase) Time elapsed: 126.558 sec <<< FAILURE! java.lang.AssertionError: Recovery failed at org.junit.Assert.fail(Assert.java:88) at org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase.testCrashBeforeCommit(RecoveryIntegrationTestCase.java:125) {code} > RecoveryIntegrationTestCase.testCrashBeforeCommit did not recover > ----------------------------------------------------------------- > > Key: JBTM-2682 > URL: https://issues.jboss.org/browse/JBTM-2682 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 191.234 sec <<< FAILURE! - in org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase > testCrashBeforeCommit(org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase) Time elapsed: 126.558 sec <<< FAILURE! > java.lang.AssertionError: Recovery failed > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase.testCrashBeforeCommit(RecoveryIntegrationTestCase.java:125) > {code} > {code} > javaagent:lib/byteman.jar=script:scripts/CrashBeforeCommit.btm,boot:lib/byteman.jar,listener:true, startupTimeoutInSeconds=60, serverConfig=standalone-rts.xml} > May 17, 2016 7:55:38 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > May 17, 2016 7:55:38 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, -Dorg.jboss.byteman.verbose, -Dorg.jboss.byteman.transform.all, -javaagent:lib/byteman.jar=script:scripts/CrashBeforeCommit.btm,boot:lib/byteman.jar,listener:true, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-rts.xml] > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 19:55:39,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final > 19:55:40,131 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 19:55:40,513 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.2.0.CR2 "Kenny" starting > 19:55:44,456 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 19:55:44,559 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 42) WFLYCLINF0001: Activating Infinispan subsystem. > 19:55:44,636 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 63) WFLYWS0002: Activating WebServices Extension > 19:55:44,659 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.6.Final > 19:55:44,670 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.6.Final > 19:55:44,592 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 49) WFLYJSF0007: Activated the following JSF Implementations: [main] > 19:55:44,619 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 61) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 19:55:45,323 INFO [org.jboss.as.security] (ServerService Thread Pool -- 60) WFLYSEC0002: Activating Security Subsystem > 19:55:45,345 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 1.3.21.Final starting > 19:55:45,381 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 43) WFLYIIOP0001: Activating IIOP Subsystem > 19:55:45,400 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 53) WFLYNAM0001: Activating Naming Subsystem > 19:55:45,622 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final > 19:55:45,580 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final > 19:55:46,430 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 41) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors > 19:55:46,561 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final) > 19:55:46,803 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 37) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 19:55:46,967 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 19:55:47,167 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 19:55:47,181 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2 > 19:55:47,136 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 19:55:48,041 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing. > 19:55:48,132 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host. > 19:55:48,116 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started > 19:55:49,637 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server. > 19:55:50,186 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting > 19:55:50,265 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 19:55:50,400 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,435 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,436 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,436 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,437 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,440 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,440 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,442 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,443 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,445 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,446 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,447 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,447 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,456 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,460 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,460 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,463 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,463 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,464 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,476 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002200: Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,709 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,758 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule Kill JVM before commit in class org.jboss.narayana.rest.integration.ParticipantResource > 19:55:50,786 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.narayana.rest.integration.ParticipantResource.commit(org.jboss.narayana.rest.integration.ParticipantInformation) void for rule Kill JVM before commit > 19:55:50,803 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for Kill JVM before commit in class org.jboss.narayana.rest.integration.ParticipantResource > 19:55:50,805 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,805 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,863 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /rest-at-coordinator > 19:55:50,866 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,866 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,870 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,870 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,872 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,875 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,890 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: volatile-rest-at-participant > 19:55:51,378 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/deployments > 19:55:51,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: rest-at-participant > 19:55:52,131 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final > 19:55:52,379 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 19:55:53,079 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 19:55:53,163 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 19:55:53,226 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221013: Using NIO Journal > 19:55:53,437 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.4.Final (Apache CXF 3.1.5) > 19:55:53,576 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 19:55:53,600 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 19:55:53,636 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 19:55:53,639 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 19:55:55,441 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:55:55,445 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:55:55,442 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:55:55,445 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:55:57,287 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221007: Server is now live > 19:55:57,288 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [nodeID=49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] > 19:55:57,479 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA > 19:55:57,585 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:55:57,651 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 19:55:57,668 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 69) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 19:55:57,669 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue jms.queue.DLQ > 19:55:58,592 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-1) Resource adaptor started > 19:55:58,592 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra > 19:55:58,594 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 19:55:58,594 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:55:58,974 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 19:55:58,974 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 19:55:58,975 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR2 "Kenny" started in 20406ms - Started 311 of 596 services (387 services are lazy, passive or on-demand) > 19:55:59,088 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/content/be/c7e201753abfa9619059b6feac0ee41834122e/content > 19:55:59,141 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 19:55:59,446 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 19:55:59,446 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 19:56:00,376 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 32) WFLYUT0021: Registered web context: /test > 19:56:01,492 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > May 17, 2016 7:56:02 PM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > 19:56:03,832 INFO [org.hibernate.validator.internal.util.Version] (default task-2) HV000001: Hibernate Validator 5.2.4.Final > 19:56:06,698 INFO [stdout] (default task-10) Rule.execute called for Kill JVM before commit_0 > 19:56:06,711 INFO [stdout] (default task-10) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 19:56:06,712 INFO [stdout] (default task-10) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 19:56:06,713 INFO [stdout] (default task-10) Default helper activated > 19:56:06,719 INFO [stdout] (default task-10) calling installed(Kill JVM before commit) for helper classorg.jboss.byteman.rule.helper.Helper > 19:56:06,719 INFO [stdout] (default task-10) Installed rule using default helper : Kill JVM before commit > 19:56:06,720 INFO [stdout] (default task-10) Kill JVM before commit execute > 19:56:06,724 INFO [stdout] (default task-10) rule.debug{Kill JVM before commit} : Killing JVM > May 17, 2016 7:56:07 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance with overridden configuration. New configuration: {managementAddress=127.0.0.1, javaVmArguments=-server -Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, startupTimeoutInSeconds=60, serverConfig=standalone-rts.xml} > May 17, 2016 7:56:07 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > May 17, 2016 7:56:07 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-rts.xml] > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > 19:56:07,928 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final > 19:56:08,509 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 19:56:08,676 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.2.0.CR2 "Kenny" starting > 19:56:14,309 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 19:56:14,332 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final > 19:56:14,341 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final > 19:56:14,542 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 43) WFLYCLINF0001: Activating Infinispan subsystem. > 19:56:14,582 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 64) WFLYWS0002: Activating WebServices Extension > 19:56:14,588 INFO [org.jboss.as.security] (ServerService Thread Pool -- 61) WFLYSEC0002: Activating Security Subsystem > 19:56:14,618 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 54) WFLYNAM0001: Activating Naming Subsystem > 19:56:14,584 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 62) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 19:56:14,779 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 50) WFLYJSF0007: Activated the following JSF Implementations: [main] > 19:56:15,111 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.18.Final > 19:56:15,393 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final) > 19:56:15,397 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 42) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors > 19:56:15,384 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final > 19:56:15,364 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 44) WFLYIIOP0001: Activating IIOP Subsystem > 19:56:15,482 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.21.Final starting > 19:56:15,647 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service > 19:56:16,045 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 38) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 19:56:16,348 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing. > 19:56:16,403 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host. > 19:56:16,514 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 19:56:16,585 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 19:56:16,675 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2 > 19:56:17,193 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. > 19:56:18,843 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 19:56:18,844 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 19:56:19,134 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,162 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,162 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,163 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,163 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,176 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,176 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,177 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,178 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,180 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,181 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,182 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,184 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,184 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,187 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,188 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,204 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,204 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,205 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,207 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,209 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,209 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,210 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,210 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,262 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,262 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,263 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,263 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,264 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,519 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: rest-at-participant > 19:56:19,524 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,528 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,528 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,540 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,540 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,541 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,547 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,550 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,550 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,596 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: volatile-rest-at-participant > 19:56:19,616 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,616 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,619 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,619 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,620 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,621 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,627 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,627 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:20,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: /rest-at-coordinator > 19:56:20,390 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started > 19:56:20,449 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/deployments > 19:56:20,462 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 19:56:20,780 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 19:56:21,802 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.4.Final (Apache CXF 3.1.5) > 19:56:22,023 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final > 19:56:22,222 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 19:56:22,251 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 19:56:22,469 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 19:56:22,469 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 19:56:23,039 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221013: Using NIO Journal > 19:56:23,341 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 19:56:23,351 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 19:56:23,364 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 19:56:23,366 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 19:56:23,742 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 2) WFLYUT0021: Registered web context: /test > 19:56:24,236 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:56:24,236 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:56:24,239 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:56:24,239 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:56:24,359 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221007: Server is now live > 19:56:24,359 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [nodeID=49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] > 19:56:24,368 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 2) AMQ221003: trying to deploy queue jms.queue.DLQ > 19:56:24,519 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA > 19:56:24,602 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 19:56:24,605 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 19:56:24,608 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 69) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:56:24,676 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-1) Resource adaptor started > 19:56:24,677 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra > 19:56:24,680 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 19:56:24,681 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:56:24,730 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR2 "Kenny" started in 17840ms - Started 382 of 672 services (398 services are lazy, passive or on-demand) > 19:56:26,692 INFO [org.hibernate.validator.internal.util.Version] (default task-1) HV000001: Hibernate Validator 5.2.4.Final > 19:56:27,484 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:16 > 19:56:27,485 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:56:43,099 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:56:57,210 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:11,314 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:25,429 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:39,533 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:43,574 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: /test > 19:57:43,608 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 52ms > 19:57:43,832 INFO [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/content/be/c7e201753abfa9619059b6feac0ee41834122e/content > 19:57:43,833 INFO [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") > May 17, 2016 7:57:43 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 19:57:43,850 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout. > 19:57:43,854 INFO [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown' > 19:57:43,877 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:57:43,877 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 19:57:43,877 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > 19:57:43,897 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 78) AMQ151003: resource adaptor stopped > 19:57:44,623 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /rest-at-coordinator > 19:57:44,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: rest-at-participant > 19:57:44,705 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: volatile-rest-at-participant > 19:57:44,707 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0019: Host default-host stopping > 19:57:44,707 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 19:57:44,714 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 77) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:57:44,717 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 74) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory > 19:57:44,879 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 74) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] stopped > 19:57:44,880 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending > 19:57:44,881 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 19:57:44,882 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.3.21.Final stopping > 19:57:44,899 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.2.0.CR2 "Kenny" stopped in 43ms > May 17, 2016 7:57:44 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill > INFO: Hard killing of a server instance > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 09:45:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 31 May 2016 09:45:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245360#comment-13245360 ] Tom Jenkinson commented on JBTM-2679: ------------------------------------- Yes, that sounds fine. It would be worth raising an upstream issue on the assembly plugin if possible and linking it back here. > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 09:55:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 31 May 2016 09:55:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2678) @TxLogged annotation does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245379#comment-13245379 ] Tom Jenkinson commented on JBTM-2678: ------------------------------------- Is it worth contacting [~paul.robinson] to understand why that work was removed? > @TxLogged annotation does not work > ---------------------------------- > > Key: JBTM-2678 > URL: https://issues.jboss.org/browse/JBTM-2678 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > @TxLogged annotation does not work in Compensations framework. All it's assertions were removed from the tests with this commit: https://github.com/jbosstm/narayana/commit/efd15eeb080c6b6338f3658c4aa58158c5e3ac6a#diff-a01554d0172e1da7703c5134820edb6aL124 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue May 31 10:45:01 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 31 May 2016 10:45:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2550: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1333245 Bugzilla Update: Perform > If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2550 > URL: https://issues.jboss.org/browse/JBTM-2550 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Affects Versions: 5.2.8.Final > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 4.17.33, 5.2.10.Final > > > This exception happens with using the IBM MQ rar in the wildfly. > com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR > We can catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)