[0m [0m01:06:27,013 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "singleton-deployment-jboss-all.war" (runtime-name: "singleton-deployment-jboss-all.war")
 [0m01:06:27,024 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
01:06:27,025 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
01:06:27,026 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
 [0m01:06:27,054 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /opt/buildAgent/work/db872761b443af46/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/data/content/1f/4ff4c7ee3ff9a068a5b24cba1d182cbcb1762e/content
 [0m [0m01:06:27,059 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
 [0m [33m01:06:27,176 WARN  [org.jgroups.protocols.MPING] (MPING) node-0: discarding discovery request for cluster 'ee' from node-0; our cluster name is 'activemq-cluster'. Please separate your clusters properly
 [0m [33m01:06:27,176 WARN  [org.jgroups.protocols.MPING] (MPING) ae9d99cd-2415-1d0c-c09c-4a2c9fc2d2c1: discarding discovery request for cluster 'ee' from ae9d99cd-2415-1d0c-c09c-4a2c9fc2d2c1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
 [0m [0m01:06:30,220 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 78) ISPN000078: Starting JGroups channel server
 [0m [0m01:06:30,221 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 78) ISPN000094: Received new cluster view for channel server: [node-0|0] (1) [node-0]
 [0m [0m01:06:30,222 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 78) ISPN000079: Channel server local address is node-0, physical addresses are [0:0:0:0:0:0:0:1:7601]
 [0m [0m01:06:30,236 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0002: Started default cache from server container
 [0m [0m01:06:30,254 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "singleton-deployment-descriptor.war" (runtime-name : "singleton-deployment-descriptor.war")
 [0m01:06:30,262 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
 [0m01:06:30,268 INFO  [org.wildfly.clustering.server] (notification-thread--p25-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
 [0m [0m01:06:30,277 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /opt/buildAgent/work/db872761b443af46/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-1/standalone/data/content/9c/1613a36b40fd7dd3638710bdaf4b0fb6bf0ad5/content
 [0m [0m01:06:30,279 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
 [0m [0m01:06:30,313 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 79) WFLYUT0021: Registered web context: /singleton-deployment-descriptor
 [0m [33m01:06:30,376 WARN  [org.jgroups.protocols.MPING] (MPING) d4b0a2e7-1971-1a5e-b447-7f2b4261e7bc: discarding discovery request for cluster 'ee' from d4b0a2e7-1971-1a5e-b447-7f2b4261e7bc; our cluster name is 'activemq-cluster'. Please separate your clusters properly
 [0m [33m01:06:30,379 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
 [0m [0m01:06:30,443 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,ee,node-0) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
 [0m [33m01:06:31,143 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'activemq-cluster' from node-1; our cluster name is 'ee'. Please separate your clusters properly
 [0m [33m01:06:31,144 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'activemq-cluster' from node-1; our cluster name is 'ee'. Please separate your clusters properly
 [0m [0m01:06:31,689 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 26) ISPN000078: Starting JGroups channel server
 [0m [0m01:06:31,689 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 26) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
 [0m [0m01:06:31,689 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 26) ISPN000079: Channel server local address is node-1, physical addresses are [0:0:0:0:0:0:0:1:7700]
 [0m [0m01:06:31,703 INFO  [org.infinispan.CLUSTER] (remote-thread--p26-t1) ISPN000310: Starting cluster-wide rebalance for cache default, topology CacheTopology{id=1, rebalanceId=1, currentCH=ReplicatedConsistentHash{ns = 60, owners = (1)[node-0: 60]}, pendingCH=ReplicatedConsistentHash{ns = 60, owners = (2)[node-0: 30, node-1: 30]}, unionCH=null, actualMembers=[node-0, node-1]}
 [0m [0m01:06:31,722 INFO  [org.infinispan.CLUSTER] (remote-thread--p26-t1) ISPN000336: Finished cluster-wide rebalance for cache default, topology id = 1
 [0m [0m01:06:31,741 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 26) WFLYCLINF0002: Started default cache from server container
 [0m [0m01:06:31,760 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "singleton-deployment-descriptor.war" (runtime-name : "singleton-deployment-descriptor.war")
 [0m [0m01:06:31,769 INFO  [org.wildfly.clustering.server] (notification-thread--p25-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
 [0m01:06:31,779 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
01:06:31,780 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
01:06:31,780 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
 [0m01:06:31,790 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 79) WFLYUT0022: Unregistered web context: /singleton-deployment-descriptor
 [0m [0m01:06:31,802 INFO  [org.wildfly.clustering.server] (notification-thread--p81-t1) WFLYCLSV0003: node-1 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
 [0m [0m01:06:31,830 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 79) WFLYCLINF0003: Stopped default cache from server container
 [0m [0m01:06:31,838 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment singleton-deployment-descriptor.war (runtime-name: singleton-deployment-descriptor.war) in 48ms
 [0m [0m01:06:31,839 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000080: Disconnecting JGroups channel server
 [0m [0m01:06:31,840 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000082: Stopping the RpcDispatcher for channel server
 [0m [0m01:06:31,887 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0002: Content removed from location /opt/buildAgent/work/db872761b443af46/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/data/content/1f/4ff4c7ee3ff9a068a5b24cba1d182cbcb1762e/content
 [0m [0m01:06:31,887 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0009: Undeployed "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
 [0m01:06:31,889 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-1
 [0m01:06:31,895 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,ee,node-1) ISPN000094: Received new cluster view for channel server: [node-1|2] (1) [node-1]
 [0m [0m01:06:31,912 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 26) WFLYUT0021: Registered web context: /singleton-deployment-descriptor
 [0m [33m01:06:31,913 WARN  [org.infinispan.notifications.cachelistener.CacheNotifierImpl] (notification-thread--p81-t1) ISPN000331: Unable to invoke method public void org.wildfly.clustering.server.group.CacheGroup.topologyChanged(org.infinispan.notifications.cachelistener.event.TopologyChangedEvent) on Object instance org.wildfly.clustering.server.group.CacheGroup@1afda88 : java.lang.UnsupportedOperationException: Not supported in this implementation since additional locking is required and cannot directly be delegated to multiple calls to ConcurrentHashMap
	at org.infinispan.util.concurrent.ConcurrentHashSet.removeAll(ConcurrentHashSet.java:110)
	at org.wildfly.clustering.server.provider.CacheServiceProviderRegistry.lambda$membershipChanged$9(CacheServiceProviderRegistry.java:161)
	at org.wildfly.clustering.server.provider.CacheServiceProviderRegistry$$Lambda$166/14124208.run(Unknown Source)

Full integration - Windows Build 387 outcome was FAILURE using a merge of 23feaa0eaf8f34398482e6aaa2530f8b3f5ea69a
Summary: Tests failed: 1 (1 new), passed: 3189, ignored: 374 Build time: 00:54:46
Failed tests
org.jboss.as.test.clustering.cluster.singleton.SingletonDeploymentDescriptorTestCase(SYNC-tcp).test: ------- Stdout: -------
01:14:13,613 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
01:14:13,614 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
01:14:13,615 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
01:14:13,623 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\ce\ecb03caee4dfdf0ecea94d971d868f1dc6cb1f\content
01:14:13,625 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
01:14:13,798 WARN  [org.jgroups.protocols.MPING] (MPING) e28aebe7-3285-c2fd-ad6a-f586e190c52e: discarding discovery request for cluster 'ee' from e28aebe7-3285-c2fd-ad6a-f586e190c52e; our cluster name is 'activemq-cluster'. Please separate your clusters properly
01:14:13,798 WARN  [org.jgroups.protocols.MPING] (MPING) node-0: discarding discovery request for cluster 'ee' from node-0; our cluster name is 'activemq-cluster'. Please separate your clusters properly
01:14:16,834 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 33) ISPN000078: Starting JGroups channel server
01:14:16,835 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 33) ISPN000094: Received new cluster view for channel server: [node-0|0] (1) [node-0]
01:14:16,835 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 33) ISPN000079: Channel server local address is node-0, physical addresses are [0:0:0:0:0:0:0:1:7601]
01:14:16,843 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) WFLYCLINF0002: Started default cache from server container
01:14:16,855 INFO  [org.wildfly.clustering.server] (notification-thread--p73-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
01:14:16,857 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "singleton-deployment-descriptor.war" (runtime-name : "singleton-deployment-descriptor.war")
01:14:16,860 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
01:14:16,878 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\e3\82e4bbab3e10731d14cddd19e014a4f7e5332a\content
01:14:16,882 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
01:14:16,931 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 33) WFLYUT0021: Registered web context: /singleton-deployment-descriptor
01:14:17,080 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
01:14:17,080 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
01:14:17,137 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,ee,node-0) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
01:14:17,180 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 7) ISPN000078: Starting JGroups channel server
01:14:17,181 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 7) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
01:14:17,181 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 7) ISPN000079: Channel server local address is node-1, physical addresses are [0:0:0:0:0:0:0:1:7701]
01:14:17,196 INFO  [org.infinispan.CLUSTER] (remote-thread--p74-t1) ISPN000310: Starting cluster-wide rebalance for cache default, topology CacheTopology{id=1, rebalanceId=1, currentCH=ReplicatedConsistentHash{ns = 60, owners = (1)[node-0: 60]}, pendingCH=ReplicatedConsistentHash{ns = 60, owners = (2)[node-0: 30, node-1: 30]}, unionCH=null, actualMembers=[node-0, node-1]}
01:14:17,226 INFO  [org.infinispan.CLUSTER] (remote-thread--p74-t1) ISPN000336: Finished cluster-wide rebalance for cache default, topology id = 1
01:14:17,385 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 7) WFLYCLINF0002: Started default cache from server container
01:14:17,394 INFO  [org.wildfly.clustering.server] (notification-thread--p73-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
01:14:17,418 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "singleton-deployment-descriptor.war" (runtime-name : "singleton-deployment-descriptor.war")
01:14:17,629 WARN  [org.jboss.remotingjmx.Util] (main) The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'.
01:14:17,691 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
01:14:17,693 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
01:14:17,695 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
01:14:17,700 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 33) WFLYUT0022: Unregistered web context: /singleton-deployment-descriptor
01:14:17,713 INFO  [org.wildfly.clustering.server] (notification-thread--p17-t1) WFLYCLSV0003: node-1 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
01:14:17,716 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 11) WFLYCLINF0003: Stopped default cache from server container
01:14:17,718 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel server
01:14:17,719 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher for channel server
01:14:17,721 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment singleton-deployment-descriptor.war (runtime-name: singleton-deployment-descriptor.war) in 22ms
01:14:17,727 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,ee,node-1) ISPN000094: Received new cluster view for channel server: [node-1|2] (1) [node-1]
01:14:17,741 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0002: Content removed from location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\ce\ecb03caee4dfdf0ecea94d971d868f1dc6cb1f\content
01:14:17,741 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0009: Undeployed "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
01:14:17,743 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-1
01:14:17,946 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 35) WFLYUT0021: Registered web context: /singleton-deployment-descriptor
01:14:17,957 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0022: Unregistered web context: /singleton-deployment-descriptor
01:14:17,976 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment singleton-deployment-descriptor.war (runtime-name: singleton-deployment-descriptor.war) in 25ms
01:14:17,978 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 34) WFLYCLINF0003: Stopped default cache from server container
01:14:17,981 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000080: Disconnecting JGroups channel server
01:14:17,981 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000082: Stopping the RpcDispatcher for channel server
01:14:18,004 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0002: Content removed from location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\e3\82e4bbab3e10731d14cddd19e014a4f7e5332a\content
01:14:18,004 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0009: Undeployed "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")

Linux Build 2862 outcome was FAILURE using a merge of 23feaa0eaf8f34398482e6aaa2530f8b3f5ea69a
Summary: Execution timeout; tests passed: 103, ignored: 1 Build time: 01:00:05

Windows Build 2348 outcome was FAILURE using a merge of 23feaa0eaf8f34398482e6aaa2530f8b3f5ea69a
Summary: Execution timeout (new); tests passed: 850, ignored: 3 Build time: 01:00:10

retest this please

Full integration - Windows Build 398 outcome was FAILURE using a merge of 92af40cb88619f0b21e75cca541ca79bb05e5601
Summary: Tests failed: 2 (2 new), passed: 3188, ignored: 374 Build time: 00:53:42
Failed tests
org.jboss.as.test.clustering.cluster.singleton.SingletonDeploymentDescriptorTestCase(SYNC-tcp).test: ------- Stdout: -------
01:29:38,674 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
01:29:38,676 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
01:29:38,677 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
01:29:38,684 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\9c\28d1bf6e6301aba158e53cd124bee6df08dfca\content
01:29:38,686 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
01:29:38,790 WARN  [org.apache.activemq.artemis.core.client] (Finalizer) AMQ212008: I am closing a core ClientSessionFactory you left open. Please make sure you close all ClientSessionFactories explicitly before letting them go out of scope! 19,100,273: java.lang.Exception
	at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.<init>(ClientSessionFactoryImpl.java:164)
	at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:797)
	at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:657)
	at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:638)
	at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl$4.run(ServerLocatorImpl.java:1489)
	at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:94)
	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)

01:29:38,850 WARN  [org.jgroups.protocols.MPING] (MPING) abf0b53e-81f7-fe6e-8757-4563a3d27ecd: discarding discovery request for cluster 'ee' from abf0b53e-81f7-fe6e-8757-4563a3d27ecd; our cluster name is 'activemq-cluster'. Please separate your clusters properly
01:29:38,850 WARN  [org.jgroups.protocols.MPING] (MPING) node-0: discarding discovery request for cluster 'ee' from node-0; our cluster name is 'activemq-cluster'. Please separate your clusters properly
01:29:41,886 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 11) ISPN000078: Starting JGroups channel server
01:29:41,886 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 11) ISPN000094: Received new cluster view for channel server: [node-0|0] (1) [node-0]
01:29:41,887 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 11) ISPN000079: Channel server local address is node-0, physical addresses are [0:0:0:0:0:0:0:1:7601]
01:29:41,896 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 11) WFLYCLINF0002: Started default cache from server container
01:29:41,905 INFO  [org.wildfly.clustering.server] (notification-thread--p73-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
01:29:41,908 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "singleton-deployment-descriptor.war" (runtime-name : "singleton-deployment-descriptor.war")
01:29:41,912 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
01:29:41,934 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\cf\00369a969c0dc76b519e04b2476ac07880258b\content
01:29:41,939 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
01:29:41,961 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 5) WFLYUT0021: Registered web context: /singleton-deployment-descriptor
01:29:42,118 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
01:29:42,118 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
01:29:42,175 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,ee,node-0) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
01:29:43,355 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 6) ISPN000078: Starting JGroups channel server
01:29:43,356 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 6) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
01:29:43,356 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 6) ISPN000079: Channel server local address is node-1, physical addresses are [0:0:0:0:0:0:0:1:7701]
01:29:43,370 INFO  [org.infinispan.CLUSTER] (remote-thread--p74-t1) ISPN000310: Starting cluster-wide rebalance for cache default, topology CacheTopology{id=1, rebalanceId=1, currentCH=ReplicatedConsistentHash{ns = 60, owners = (1)[node-0: 60]}, pendingCH=ReplicatedConsistentHash{ns = 60, owners = (2)[node-0: 30, node-1: 30]}, unionCH=null, actualMembers=[node-0, node-1]}
01:29:43,397 INFO  [org.infinispan.CLUSTER] (remote-thread--p74-t1) ISPN000336: Finished cluster-wide rebalance for cache default, topology id = 1
01:29:43,400 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 6) WFLYCLINF0002: Started default cache from server container
01:29:43,416 INFO  [org.wildfly.clustering.server] (notification-thread--p73-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
01:29:43,436 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "singleton-deployment-descriptor.war" (runtime-name : "singleton-deployment-descriptor.war")
01:29:43,591 WARN  [org.jboss.remotingjmx.Util] (main) The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'.
01:29:43,639 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
01:29:43,640 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
01:29:43,642 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
01:29:43,647 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 5) WFLYUT0022: Unregistered web context: /singleton-deployment-descriptor
01:29:43,693 INFO  [org.wildfly.clustering.server] (notification-thread--p17-t1) WFLYCLSV0003: node-1 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
01:29:43,711 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment singleton-deployment-descriptor.war (runtime-name: singleton-deployment-descriptor.war) in 64ms
01:29:43,713 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 11) WFLYCLINF0003: Stopped default cache from server container
01:29:43,743 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000080: Disconnecting JGroups channel server
01:29:43,743 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000082: Stopping the RpcDispatcher for channel server
01:29:43,789 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,ee,node-1) ISPN000094: Received new cluster view for channel server: [node-1|2] (1) [node-1]

org.jboss.as.test.clustering.cluster.singleton.SingletonDeploymentJBossAllTestCase(SYNC-tcp).test: ------- Stdout: -------
01:29:44,062 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
01:29:44,074 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
01:29:44,075 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
01:29:44,089 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\a0\8c5c89ebe3a1d3f79358f63f4286af810ebfe6\content
01:29:44,091 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "singleton-deployment-jboss-all.war" (runtime-name: "singleton-deployment-jboss-all.war")
01:29:44,232 WARN  [org.jgroups.protocols.MPING] (MPING) 48dac235-3f00-3321-9f0c-39c61466dae6: discarding discovery request for cluster 'ee' from 48dac235-3f00-3321-9f0c-39c61466dae6; our cluster name is 'activemq-cluster'. Please separate your clusters properly
01:29:44,232 WARN  [org.jgroups.protocols.MPING] (MPING) node-0: discarding discovery request for cluster 'ee' from node-0; our cluster name is 'activemq-cluster'. Please separate your clusters properly
01:29:47,272 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 11) ISPN000078: Starting JGroups channel server
01:29:47,272 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 11) ISPN000094: Received new cluster view for channel server: [node-0|0] (1) [node-0]
01:29:47,272 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 11) ISPN000079: Channel server local address is node-0, physical addresses are [0:0:0:0:0:0:0:1:7601]
01:29:47,280 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 11) WFLYCLINF0002: Started default cache from server container
01:29:47,293 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "singleton-deployment-jboss-all.war" (runtime-name : "singleton-deployment-jboss-all.war")
01:29:47,298 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
01:29:47,300 INFO  [org.wildfly.clustering.server] (notification-thread--p81-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-jboss-all.war".FIRST_MODULE_USE service
01:29:47,309 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\69\6dea4213e62aec1bfb8e0abf22702521dca409\content
01:29:47,312 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "singleton-deployment-jboss-all.war" (runtime-name: "singleton-deployment-jboss-all.war")
01:29:47,348 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: /singleton-deployment-jboss-all
01:29:47,516 WARN  [org.jgroups.protocols.MPING] (MPING) 211a6bca-671f-f859-fc75-2c28777b73a1: discarding discovery request for cluster 'ee' from 211a6bca-671f-f859-fc75-2c28777b73a1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
01:29:47,518 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
01:29:47,585 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,ee,node-0) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
01:29:47,628 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 6) ISPN000078: Starting JGroups channel server
01:29:47,630 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 6) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
01:29:47,639 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 6) ISPN000079: Channel server local address is node-1, physical addresses are [0:0:0:0:0:0:0:1:7701]
01:29:47,655 INFO  [org.infinispan.CLUSTER] (remote-thread--p82-t1) ISPN000310: Starting cluster-wide rebalance for cache default, topology CacheTopology{id=1, rebalanceId=1, currentCH=ReplicatedConsistentHash{ns = 60, owners = (1)[node-0: 60]}, pendingCH=ReplicatedConsistentHash{ns = 60, owners = (2)[node-0: 30, node-1: 30]}, unionCH=null, actualMembers=[node-0, node-1]}
01:29:47,676 INFO  [org.infinispan.CLUSTER] (remote-thread--p82-t1) ISPN000336: Finished cluster-wide rebalance for cache default, topology id = 1
01:29:47,699 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 6) WFLYCLINF0002: Started default cache from server container
01:29:47,711 INFO  [org.wildfly.clustering.server] (notification-thread--p81-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-jboss-all.war".FIRST_MODULE_USE service
01:29:47,733 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "singleton-deployment-jboss-all.war" (runtime-name : "singleton-deployment-jboss-all.war")
01:29:47,746 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
01:29:47,747 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
01:29:47,750 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
01:29:47,756 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0022: Unregistered web context: /singleton-deployment-jboss-all
01:29:47,773 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment singleton-deployment-jboss-all.war (runtime-name: singleton-deployment-jboss-all.war) in 19ms
01:29:47,776 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 11) WFLYCLINF0003: Stopped default cache from server container
01:29:47,768 INFO  [org.wildfly.clustering.server] (notification-thread--p25-t1) WFLYCLSV0003: node-1 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-jboss-all.war".FIRST_MODULE_USE service
01:29:47,783 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel server
01:29:47,784 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher for channel server
01:29:47,785 WARN  [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p84-t4) ISPN000197: Error updating cluster member list: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node-1, see cause for remote stack trace
	at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:747)
	at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$80(JGroupsTransport.java:589)
	at org.infinispan.remoting.transport.jgroups.JGroupsTransport$$Lambda$82/14331383.apply(Unknown Source)
	at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602)
	at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
	at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
	at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1954)
	at org.infinispan.remoting.transport.jgroups.SingleResponseFuture.futureDone(SingleResponseFuture.java:30)
	at org.jgroups.blocks.Request.checkCompletion(Request.java:169)
	at org.jgroups.blocks.UnicastRequest.transportClosed(UnicastRequest.java:182)
	at org.jgroups.blocks.RequestCorrelator.stop(RequestCorrelator.java:270)
	at org.jgroups.blocks.MessageDispatcher.stop(MessageDispatcher.java:163)

Core - Full Integration Build 1977 outcome was FAILURE using a merge of 92af40cb88619f0b21e75cca541ca79bb05e5601
Summary: Tests failed: 1 (1 new), passed: 3189, ignored: 374 Build time: 00:54:09
Failed tests
org.jboss.as.test.clustering.cluster.singleton.SingletonDeploymentDescriptorTestCase(SYNC-tcp).test: ------- Stdout: -------
02:16:30,526 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
02:16:30,527 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
02:16:30,528 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
 [0m02:16:30,540 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /opt/buildAgent/work/db872761b443af46/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/data/content/21/7e247089008199e269c9ed09b773c7cbb9a2f3/content
 [0m [0m02:16:30,542 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
 [0m [33m02:16:30,602 WARN  [org.jgroups.protocols.MPING] (MPING) node-0: discarding discovery request for cluster 'ee' from node-0; our cluster name is 'activemq-cluster'. Please separate your clusters properly
 [0m [33m02:16:30,603 WARN  [org.jgroups.protocols.MPING] (MPING) ab36c039-62f7-93cc-9bc6-de913847b756: discarding discovery request for cluster 'ee' from ab36c039-62f7-93cc-9bc6-de913847b756; our cluster name is 'activemq-cluster'. Please separate your clusters properly
 [0m [33m02:16:31,427 WARN  [org.jgroups.protocols.MPING] (MPING) node-0: discarding discovery request for cluster 'activemq-cluster' from node-0; our cluster name is 'ee'. Please separate your clusters properly
 [0m [0m02:16:33,616 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 76) ISPN000078: Starting JGroups channel server
 [0m [0m02:16:33,619 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 76) ISPN000094: Received new cluster view for channel server: [node-0|0] (1) [node-0]
 [0m [0m02:16:33,619 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 76) ISPN000079: Channel server local address is node-0, physical addresses are [0:0:0:0:0:0:0:1:7601]
 [0m [0m02:16:33,628 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 76) WFLYCLINF0002: Started default cache from server container
 [0m [0m02:16:33,640 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "singleton-deployment-descriptor.war" (runtime-name : "singleton-deployment-descriptor.war")
 [0m02:16:33,649 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
 [0m02:16:33,654 INFO  [org.wildfly.clustering.server] (notification-thread--p25-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
 [0m [0m02:16:33,663 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /opt/buildAgent/work/db872761b443af46/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-1/standalone/data/content/18/a78143ee67675d6e04ba6c16dea8da2213a136/content
 [0m [0m02:16:33,665 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
 [0m [0m02:16:33,705 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 14) WFLYUT0021: Registered web context: /singleton-deployment-descriptor
 [0m [33m02:16:33,746 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
 [0m [33m02:16:33,747 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
 [0m [0m02:16:33,814 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,ee,node-0) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
 [0m [0m02:16:33,854 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 34) ISPN000078: Starting JGroups channel server
 [0m [0m02:16:33,857 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 34) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
 [0m [0m02:16:33,857 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 34) ISPN000079: Channel server local address is node-1, physical addresses are [0:0:0:0:0:0:0:1:7700]
 [0m [0m02:16:33,901 INFO  [org.infinispan.CLUSTER] (remote-thread--p26-t1) ISPN000310: Starting cluster-wide rebalance for cache default, topology CacheTopology{id=1, rebalanceId=1, currentCH=ReplicatedConsistentHash{ns = 60, owners = (1)[node-0: 60]}, pendingCH=ReplicatedConsistentHash{ns = 60, owners = (2)[node-0: 30, node-1: 30]}, unionCH=null, actualMembers=[node-0, node-1]}
 [0m [0m02:16:33,918 INFO  [org.infinispan.CLUSTER] (remote-thread--p26-t1) ISPN000336: Finished cluster-wide rebalance for cache default, topology id = 1
 [0m [0m02:16:33,921 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 34) WFLYCLINF0002: Started default cache from server container
 [0m [0m02:16:33,934 INFO  [org.wildfly.clustering.server] (notification-thread--p25-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
 [0m [0m02:16:33,945 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "singleton-deployment-descriptor.war" (runtime-name : "singleton-deployment-descriptor.war")
 [0m02:16:33,953 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
02:16:33,954 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
02:16:33,954 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
 [0m02:16:33,979 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 14) WFLYUT0022: Unregistered web context: /singleton-deployment-descriptor
 [0m [0m02:16:33,992 INFO  [org.wildfly.clustering.server] (notification-thread--p81-t1) WFLYCLSV0003: node-1 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
 [0m [0m02:16:34,010 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment singleton-deployment-descriptor.war (runtime-name: singleton-deployment-descriptor.war) in 36ms
 [0m [0m02:16:34,039 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 14) WFLYCLINF0003: Stopped default cache from server container
 [0m [0m02:16:34,056 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000080: Disconnecting JGroups channel server
 [0m [0m02:16:34,057 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000082: Stopping the RpcDispatcher for channel server
 [0m [0m02:16:34,068 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 34) WFLYUT0021: Registered web context: /singleton-deployment-descriptor
 [0m [0m02:16:34,079 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,ee,node-1) ISPN000094: Received new cluster view for channel server: [node-1|2] (1) [node-1]
 [0m [0m02:16:34,121 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location /opt/buildAgent/work/db872761b443af46/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/data/content/21/7e247089008199e269c9ed09b773c7cbb9a2f3/content
 [0m [0m02:16:34,121 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
 [0m02:16:34,125 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-1
 [0m02:16:34,128 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 34) WFLYUT0022: Unregistered web context: /singleton-deployment-descriptor
 [0m [0m02:16:34,134 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 8) WFLYCLINF0003: Stopped default cache from server container
 [0m [0m02:16:34,137 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000080: Disconnecting JGroups channel server
 [0m [0m02:16:34,137 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000082: Stopping the RpcDispatcher for channel server
 [0m [0m02:16:34,142 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment singleton-deployment-descriptor.war (runtime-name: singleton-deployment-descriptor.war) in 14ms
 [0m [0m02:16:34,160 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location /opt/buildAgent/work/db872761b443af46/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-1/standalone/data/content/18/a78143ee67675d6e04ba6c16dea8da2213a136/content
 [0m [0m02:16:34,160 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")

retest this please
@kabir i'm retesting again to get more reps, but it's looking good so far. Both of the core runs have passed 3 times with my latest.
What you looked at before is unchanged, but I've added another commit.

Windows Build 2361 outcome was FAILURE using a merge of 92af40cb88619f0b21e75cca541ca79bb05e5601
Summary: Tests failed: 1 (1 new), passed: 3443, ignored: 64 Build time: 00:36:00
Failed tests
org.jboss.as.test.manualmode.deployment.DeploymentScannerUnitTestCase.testStartup: java.lang.AssertionError: null
	at org.jboss.as.test.manualmode.deployment.DeploymentScannerUnitTestCase.testStartup(DeploymentScannerUnitTestCase.java:135)
------- Stdout: -------
03:17:34,512 INFO  [org.wildfly.core.testrunner.Server] (main) Starting container with: C:\Java\jdk1.8.0_11\jre\bin\java -D[Standalone] -javaagent:c:\store\repository\org\jboss\byteman\byteman\2.2.1\byteman-2.2.1.jar=port:9091,boot:c:\store\repository\org\jboss\byteman\byteman\2.2.1\byteman-2.2.1.jar,sys:C:\BuildAgent\work\8d74ae55e497982e\testsuite\shared\target\wildfly-core-testsuite-shared-2.0.0.CR6-SNAPSHOT.jar -Dorg.jboss.byteman.transform.all -Dorg.jboss.byteman.verbose=true -Dmaven.repo.local=c:\store\repository -Xmx512m -Djboss.dist=C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode/target/wildfly-core -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -server -Dts.timeout.factor=100 -Djbossas.ts.dir=C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode -ea -Dorg.jboss.boot.log.file=C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode\target\wildfly-core\standalone\log\server.log -Dlogging.configuration=file:C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode\target\wildfly-core\standalone\configuration\logging.properties -jar C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode\target\wildfly-core\jboss-modules.jar -mp C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode\target\wildfly-core\modules org.jboss.as.standalone -Djboss.home.dir=C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode\target\wildfly-core -Djboss.server.base.dir=C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode\target\wildfly-core\standalone -Djboss.server.log.dir=C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode\target\wildfly-core\standalone\log -Djboss.server.config.dir=C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode\target\wildfly-core\standalone\configuration -c=standalone.xml -bmanagement=::1 -Djboss.http.port=8080 -Djboss.bind.address=::1
03:17:34,614 INFO  [org.xnio] (main) XNIO version 3.3.2.Final
TransformListener() : accepting requests on localhost:9091
03:17:34,684 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.2.Final
03:17:34,747 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.14.Final
03:17:35,063 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
03:17:35,319 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
03:17:35,419 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Core 2.0.0.CR6-SNAPSHOT "Kenny" starting
03:17:36,017 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
03:17:36,040 INFO  [org.xnio] (MSC service thread 1-7) XNIO version 3.3.2.Final
03:17:36,053 INFO  [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.3.2.Final
03:17:36,105 INFO  [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 4.0.14.Final
03:17:36,218 WARN  [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-7) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console
03:17:36,505 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9990/management
03:17:36,506 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://[::1]:9990
03:17:36,506 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.0.0.CR6-SNAPSHOT "Kenny" started in 1829ms - Started 55 of 57 services (15 services are lazy, passive or on-demand)
03:17:37,321 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode\target\deployment-test-0ed6a7bd-5916-4b6d-af54-7aa17f03f275
03:17:37,339 INFO  [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode\target\wildfly-core\standalone\data\content\cd\a29d2352d2cbdd950525e266d1fb59b7f3bd9c\content
03:17:37,345 INFO  [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\8d74ae55e497982e\testsuite\manualmode\target\wildfly-core\standalone\data\content\9f\4b66fb8a8e3fab7a1bbadfb5a792e445b1dba7\content
03:17:37,360 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "deployment-one.jar" (runtime-name: "deployment-one.jar")
03:17:37,360 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "deployment-two.jar" (runtime-name: "deployment-two.jar")
03:17:37,400 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.module.service."deployment.deployment-two.jar".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.deployment-two.jar".main: WFLYSRV0179: Failed to load module: deployment.deployment-two.jar:main
	at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.modules.ModuleNotFoundException: non.existing.dependency:main
	at org.jboss.modules.Module.addPaths(Module.java:1042)
	at org.jboss.modules.Module.link(Module.java:1398)
	at org.jboss.modules.Module.relinkIfNecessary(Module.java:1426)
	at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:238)
	at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68)
	... 5 more

03:17:37,406 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "deployment-two.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.deployment-two.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.deployment-two.jar\".main: WFLYSRV0179: Failed to load module: deployment.deployment-two.jar:main
    Caused by: org.jboss.modules.ModuleNotFoundException: non.existing.dependency:main"}}
03:17:37,414 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "deployment-two.jar" (runtime-name : "deployment-two.jar")
03:17:37,414 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "deployment-one.jar" (runtime-name : "deployment-one.jar")
03:17:37,414 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
WFLYCTL0186:   Services which failed to start:      service jboss.module.service."deployment.deployment-two.jar".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.deployment-two.jar".main: WFLYSRV0179: Failed to load module: deployment.deployment-two.jar:main

03:17:37,505 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0211: Suspending server with 0ms timeout.
03:17:37,508 INFO  [org.jboss.as.server] (Thread-3) WFLYSRV0220: Server shutdown has been requested.
03:17:37,522 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment deployment-one.jar (runtime-name: deployment-one.jar) in 7ms
03:17:37,532 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment deployment-two.jar (runtime-name: deployment-two.jar) in 20ms
03:17:37,538 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.0.0.CR6-SNAPSHOT "Kenny" stopped in 22ms

Linux Build 2875 outcome was FAILURE using a merge of 92af40cb88619f0b21e75cca541ca79bb05e5601
Summary: Execution timeout (new); tests passed: 3037, ignored: 48 Build time: 01:00:06

Full integration - Windows Build 401 outcome was FAILURE using a merge of 92af40cb88619f0b21e75cca541ca79bb05e5601
Summary: Tests failed: 1 (1 new), passed: 3189, ignored: 374 Build time: 00:54:20
Failed tests
org.jboss.as.test.clustering.cluster.singleton.SingletonDeploymentDescriptorTestCase(SYNC-tcp).test: ------- Stdout: -------
04:29:31,398 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
04:29:31,399 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
04:29:31,400 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
04:29:31,407 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\71\cc3b031f4181e956bdc40ccfb624eba2405fd1\content
04:29:31,409 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
04:29:31,571 WARN  [org.jgroups.protocols.MPING] (MPING) 75460120-6c98-a847-94c8-5ca47de034dd: discarding discovery request for cluster 'ee' from 75460120-6c98-a847-94c8-5ca47de034dd; our cluster name is 'activemq-cluster'. Please separate your clusters properly
04:29:31,571 WARN  [org.jgroups.protocols.MPING] (MPING) node-0: discarding discovery request for cluster 'ee' from node-0; our cluster name is 'activemq-cluster'. Please separate your clusters properly
04:29:34,608 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 31) ISPN000078: Starting JGroups channel server
04:29:34,609 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 31) ISPN000094: Received new cluster view for channel server: [node-0|0] (1) [node-0]
04:29:34,609 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 31) ISPN000079: Channel server local address is node-0, physical addresses are [0:0:0:0:0:0:0:1:7601]
04:29:34,617 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) WFLYCLINF0002: Started default cache from server container
04:29:34,627 INFO  [org.wildfly.clustering.server] (notification-thread--p73-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
04:29:34,629 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "singleton-deployment-descriptor.war" (runtime-name : "singleton-deployment-descriptor.war")
04:29:34,637 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
04:29:34,670 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\05\f58ace8190fe25418570bf283badfdb525182d\content
04:29:34,674 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
04:29:34,696 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 31) WFLYUT0021: Registered web context: /singleton-deployment-descriptor
04:29:34,887 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
04:29:34,887 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
04:29:34,946 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,ee,node-0) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
04:29:34,992 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 12) ISPN000078: Starting JGroups channel server
04:29:34,993 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 12) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
04:29:34,993 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 12) ISPN000079: Channel server local address is node-1, physical addresses are [0:0:0:0:0:0:0:1:7701]
04:29:35,052 INFO  [org.infinispan.CLUSTER] (remote-thread--p74-t1) ISPN000310: Starting cluster-wide rebalance for cache default, topology CacheTopology{id=1, rebalanceId=1, currentCH=ReplicatedConsistentHash{ns = 60, owners = (1)[node-0: 60]}, pendingCH=ReplicatedConsistentHash{ns = 60, owners = (2)[node-0: 30, node-1: 30]}, unionCH=null, actualMembers=[node-0, node-1]}
04:29:35,120 INFO  [org.infinispan.CLUSTER] (remote-thread--p74-t1) ISPN000336: Finished cluster-wide rebalance for cache default, topology id = 1
04:29:35,123 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 12) WFLYCLINF0002: Started default cache from server container
04:29:35,131 INFO  [org.wildfly.clustering.server] (notification-thread--p73-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
04:29:35,154 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "singleton-deployment-descriptor.war" (runtime-name : "singleton-deployment-descriptor.war")
04:29:35,264 WARN  [org.jboss.remotingjmx.Util] (main) The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'.
04:29:35,304 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
04:29:35,305 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
04:29:35,307 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
04:29:35,312 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 31) WFLYUT0022: Unregistered web context: /singleton-deployment-descriptor
04:29:35,329 INFO  [org.wildfly.clustering.server] (notification-thread--p17-t1) WFLYCLSV0003: node-1 elected as the singleton provider of the jboss.deployment.unit."singleton-deployment-descriptor.war".FIRST_MODULE_USE service
04:29:35,344 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment singleton-deployment-descriptor.war (runtime-name: singleton-deployment-descriptor.war) in 34ms
04:29:35,353 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) WFLYCLINF0003: Stopped default cache from server container
04:29:35,408 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000080: Disconnecting JGroups channel server
04:29:35,409 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000082: Stopping the RpcDispatcher for channel server
04:29:35,438 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,ee,node-1) ISPN000094: Received new cluster view for channel server: [node-1|2] (1) [node-1]
04:29:35,455 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\71\cc3b031f4181e956bdc40ccfb624eba2405fd1\content
04:29:35,456 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")
04:29:35,457 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-1
04:29:35,598 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 16) WFLYUT0021: Registered web context: /singleton-deployment-descriptor
04:29:35,614 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 12) WFLYUT0022: Unregistered web context: /singleton-deployment-descriptor
04:29:35,632 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment singleton-deployment-descriptor.war (runtime-name: singleton-deployment-descriptor.war) in 29ms
04:29:35,634 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 16) WFLYCLINF0003: Stopped default cache from server container
04:29:35,637 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) ISPN000080: Disconnecting JGroups channel server
04:29:35,637 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) ISPN000082: Stopping the RpcDispatcher for channel server
04:29:35,663 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0002: Content removed from location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\05\f58ace8190fe25418570bf283badfdb525182d\content
04:29:35,663 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0009: Undeployed "singleton-deployment-descriptor.war" (runtime-name: "singleton-deployment-descriptor.war")

retest this please
Had a different hang of some sort. Investigating

Core - Full Integration Build 1987 outcome was FAILURE using a merge of 92af40cb88619f0b21e75cca541ca79bb05e5601
Summary: Tests failed: 1 (1 new), passed: 3189, ignored: 374 Build time: 00:55:44
Failed tests
org.jboss.as.test.integration.ejb.remote.client.api.tx.EJBClientUserTransactionTestCase.testBatchOperationsInTx: java.lang.IllegalStateException: EJBCLIENT000050: Node of the current transaction build13-el7 does not accept StatelessEJBLocator for "ejb-remote-client-api-usertx-test/ejb/BatchCreationBean", view is interface org.jboss.as.test.integration.ejb.remote.client.api.tx.RemoteBatch, affinity is None
	at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:49)
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
	at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
	at com.sun.proxy.$Proxy87.createBatch(Unknown Source)
	at org.jboss.as.test.integration.ejb.remote.client.api.tx.EJBClientUserTransactionTestCase.testBatchOperationsInTx(EJBClientUserTransactionTestCase.java:163)
------- Stdout: -------
 [0m17:25:02,930 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0010: Stopping weld service for deployment ejb-client-interceptor-test-module.jar
 [0m [0m17:25:02,933 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment ejb-client-interceptor-test-module.jar (runtime-name: ejb-client-interceptor-test-module.jar) in 5ms
 [0m [0m17:25:02,937 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location /opt/buildAgent/work/db872761b443af46/full/testsuite/integration/basic/target/jbossas/standalone/data/content/9d/6a10579b7a5e20d4987b3ee200e1980f71d579/content
 [0m [0m17:25:02,937 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "ejb-client-interceptor-test-module.jar" (runtime-name: "ejb-client-interceptor-test-module.jar")
 [0m [0m17:25:02,961 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /opt/buildAgent/work/db872761b443af46/full/testsuite/integration/basic/target/jbossas/standalone/data/content/a3/72f2001c1facab91ffb8fb955e6a7de1e3e36d/content
 [0m [0m17:25:02,962 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "ejb-remote-client-api-usertx-test.ear" (runtime-name: "ejb-remote-client-api-usertx-test.ear")
 [0m [0m17:25:02,964 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "ejb.jar")
 [0m [0m17:25:02,965 INFO  [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for ejb-client-tx-pu
 [0m [33m17:25:02,969 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ejb-remote-client-api-usertx-test.ear" is using a private module ("org.wildfly.security.manager:main") which may be changed or removed in future versions without notice.
 [0m [33m17:25:02,970 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ejb-remote-client-api-usertx-test.ear.ejb.jar" is using a private module ("org.wildfly.security.manager:main") which may be changed or removed in future versions without notice.
 [0m [0m17:25:02,971 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment ejb-remote-client-api-usertx-test.ear
 [0m [0m17:25:02,981 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 62) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'ejb-remote-client-api-usertx-test.ear/ejb.jar#ejb-client-tx-pu'
 [0m [0m17:25:02,982 INFO  [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 62) HHH000204: Processing PersistenceUnitInfo [
	name: ejb-client-tx-pu
	...]
 [0m [0m17:25:02,987 INFO  [org.hibernate.orm.deprecation] (ServerService Thread Pool -- 62) HHH90000001: Found usage of deprecated setting for specifying Scanner [hibernate.ejb.resource_scanner]; use [hibernate.archive.scanner] instead
 [0m [0m17:25:02,994 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment ejb.jar
 [0m [0m17:25:02,995 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'BatchFetchingBean' in deployment unit 'subdeployment "ejb.jar" of deployment "ejb-remote-client-api-usertx-test.ear"' are as follows:

	java:global/ejb-remote-client-api-usertx-test/ejb/BatchFetchingBean!org.jboss.as.test.integration.ejb.remote.client.api.tx.BatchRetriever
	java:app/ejb/BatchFetchingBean!org.jboss.as.test.integration.ejb.remote.client.api.tx.BatchRetriever
	java:module/BatchFetchingBean!org.jboss.as.test.integration.ejb.remote.client.api.tx.BatchRetriever
	java:jboss/exported/ejb-remote-client-api-usertx-test/ejb/BatchFetchingBean!org.jboss.as.test.integration.ejb.remote.client.api.tx.BatchRetriever
	java:global/ejb-remote-client-api-usertx-test/ejb/BatchFetchingBean
	java:app/ejb/BatchFetchingBean
	java:module/BatchFetchingBean

 [0m [0m17:25:02,995 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'BatchCreationBean' in deployment unit 'subdeployment "ejb.jar" of deployment "ejb-remote-client-api-usertx-test.ear"' are as follows:

	java:global/ejb-remote-client-api-usertx-test/ejb/BatchCreationBean!org.jboss.as.test.integration.ejb.remote.client.api.tx.RemoteBatch
	java:app/ejb/BatchCreationBean!org.jboss.as.test.integration.ejb.remote.client.api.tx.RemoteBatch
	java:module/BatchCreationBean!org.jboss.as.test.integration.ejb.remote.client.api.tx.RemoteBatch
	java:jboss/exported/ejb-remote-client-api-usertx-test/ejb/BatchCreationBean!org.jboss.as.test.integration.ejb.remote.client.api.tx.RemoteBatch
	java:global/ejb-remote-client-api-usertx-test/ejb/BatchCreationBean
	java:app/ejb/BatchCreationBean
	java:module/BatchCreationBean

 [0m [0m17:25:02,995 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'CMTBean' in deployment unit 'subdeployment "ejb.jar" of deployment "ejb-remote-client-api-usertx-test.ear"' are as follows:

	java:global/ejb-remote-client-api-usertx-test/ejb/CMTBean!org.jboss.as.test.integration.ejb.remote.client.api.tx.CMTRemote
	java:app/ejb/CMTBean!org.jboss.as.test.integration.ejb.remote.client.api.tx.CMTRemote

retest this please

Linux Build 2890 outcome was FAILURE using a merge of b73d3107fdd0da440fa1caca80e25b1c1111a1e6
Summary: Execution timeout (new); tests passed: 3038, ignored: 48 Build time: 01:00:09

I'm good with this whenever you are @bstansberry.

@jamezp now there have twice been hangs in HcExtensionAndSubsystemManagementTestCase. For some reason an HC reload isn't completing. Hard to see how it relates to this, but I haven't noticed it elsewhere.
#1129 aims to tighten up that test a bit, but what I did in that PR should just mean things happen a bit more cleanly. If the reload doesn't complete the test run will still be screwed up.

retest this please

retest this please

Full integration - Windows Build 441 outcome was FAILURE using a merge of f1ed9ff1f5ec9aa68f1cbb1f7be9c44787c79ac5
Summary: Tests failed: 1 (1 new), passed: 3189, ignored: 374 Build time: 00:57:18
Failed tests
org.jboss.as.test.clustering.cluster.singleton.SingletonServiceTestCase(SYNC-tcp).testSingletonService: org.apache.http.conn.HttpHostConnectException: Connect to [::1]:8080 [/0:0:0:0:0:0:0:1] failed: Connection refused: connect
	at java.net.DualStackPlainSocketImpl.connect0(Native Method)
	at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
	at org.jboss.as.test.clustering.cluster.singleton.SingletonServiceTestCase.testSingletonService(SingletonServiceTestCase.java:219)
------- Stdout: -------
23:21:14,476 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
23:21:14,477 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
23:21:14,478 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
23:21:14,488 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\63\8cc44cd1b282cf6d7b2b672cd8f72d9cb33542\content
23:21:14,491 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "singleton.war" (runtime-name: "singleton.war")
23:21:14,532 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.singleton.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
23:21:14,651 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 87) WFLYUT0021: Registered web context: /singleton
23:21:14,708 WARN  [org.jgroups.protocols.MPING] (MPING) fa661960-5829-56ee-3ca2-9782eb4935f4: discarding discovery request for cluster 'ee' from fa661960-5829-56ee-3ca2-9782eb4935f4; our cluster name is 'activemq-cluster'. Please separate your clusters properly
23:21:14,708 WARN  [org.jgroups.protocols.MPING] (MPING) node-0: discarding discovery request for cluster 'ee' from node-0; our cluster name is 'activemq-cluster'. Please separate your clusters properly
23:21:17,745 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 87) ISPN000078: Starting JGroups channel server
23:21:17,746 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 87) ISPN000094: Received new cluster view for channel server: [node-0|0] (1) [node-0]
23:21:17,746 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 87) ISPN000079: Channel server local address is node-0, physical addresses are [0:0:0:0:0:0:0:1:7601]
23:21:17,754 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 87) WFLYCLINF0002: Started default cache from server container
23:21:17,756 INFO  [org.wildfly.clustering.server] (notification-thread--p105-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.test.myservice.default service
23:21:17,760 INFO  [org.wildfly.clustering.server] (notification-thread--p105-t1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.test.myservice.default service
23:21:17,760 ERROR [org.wildfly.clustering.server] (notification-thread--p105-t1) WFLYCLSV0006: Failed to reach quorum of 2 for jboss.test.myservice.quorum service. No singleton master will be elected.
23:21:17,767 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "singleton.war" (runtime-name : "singleton.war")
23:21:17,772 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
23:21:17,782 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\b8\b80ba8c39610b3a75bbf7bf1093b6c79fe619a\content
23:21:17,784 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "singleton.war" (runtime-name: "singleton.war")
23:21:17,810 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.singleton.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
23:21:17,850 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 76) WFLYUT0021: Registered web context: /singleton
23:21:17,966 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
23:21:17,966 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
23:21:18,025 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,ee,node-0) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
23:21:18,066 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 76) ISPN000078: Starting JGroups channel server
23:21:18,067 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 76) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
23:21:18,067 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 76) ISPN000079: Channel server local address is node-1, physical addresses are [0:0:0:0:0:0:0:1:7701]
23:21:18,079 INFO  [org.infinispan.CLUSTER] (remote-thread--p106-t1) ISPN000310: Starting cluster-wide rebalance for cache default, topology CacheTopology{id=1, rebalanceId=1, currentCH=ReplicatedConsistentHash{ns = 60, owners = (1)[node-0: 60]}, pendingCH=ReplicatedConsistentHash{ns = 60, owners = (2)[node-0: 30, node-1: 30]}, unionCH=null, actualMembers=[node-0, node-1]}

retest this please

retest this please

Core - Full Integration Build 2038 outcome was FAILURE using a merge of f1ed9ff1f5ec9aa68f1cbb1f7be9c44787c79ac5
Summary: Tests passed: 3068, ignored: 366; exit code 137 (new) Build time: 00:49:25

Core - Full Integration Build 2039 outcome was FAILURE using a merge of f1ed9ff1f5ec9aa68f1cbb1f7be9c44787c79ac5
Summary: Tests passed: 3068, ignored: 366; exit code 137 Build time: 00:50:02

retest this please

Linux Build 2952 outcome was FAILURE using a merge of 00ce2ee5380338d9f81022bb44600f9fbfe9785c
Summary: Tests failed: 1 (1 new), passed: 3447, ignored: 64 Build time: 00:35:14
Failed tests
org.jboss.as.domain.management.security.auditlog.AuditLogHandlerBootEnabledTestCase.testMessageTransfer: java.net.BindException: Address already in use
	at java.net.PlainDatagramSocketImpl.bind0(Native Method)
	at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:94)
	at java.net.DatagramSocket.bind(DatagramSocket.java:392)
	at java.net.DatagramSocket.<init>(DatagramSocket.java:242)
	at java.net.DatagramSocket.<init>(DatagramSocket.java:299)
	at java.net.DatagramSocket.<init>(DatagramSocket.java:271)
	at org.jboss.as.domain.management.security.auditlog.SimpleSyslogServer$Udp.<init>(SimpleSyslogServer.java:130)
	at org.jboss.as.domain.management.security.auditlog.SimpleSyslogServer.createUdp(SimpleSyslogServer.java:63)
	at org.jboss.as.domain.management.security.auditlog.AuditLogHandlerBootEnabledTestCase.testMessageTransfer(AuditLogHandlerBootEnabledTestCase.java:445)

Linux Build 2953 outcome was FAILURE using a merge of 00ce2ee5380338d9f81022bb44600f9fbfe9785c
Summary: Tests failed: 1 (1 new), passed: 3447, ignored: 64 Build time: 00:37:36
Failed tests
org.jboss.as.test.integration.domain.suites.CompositeOperationTestCase.testMultipleProcessReadWriteOperation:     "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-2" => {
            "outcome" => "failed",
            "result" => "1",
            "rolled-back" => true
        },
        "step-3" => {"outcome" => undefined},
        "step-4" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-5" => {
            "outcome" => "failed",
            "result" => "2",
            "rolled-back" => true
        },
        "step-6" => {"outcome" => undefined},
        "step-7" => undefined,
        "step-8" => {
            "outcome" => "failed",
            "result" => "2",
            "rolled-back" => true
        },
        "step-9" => {"outcome" => undefined},
        "step-10" => {
            "outcome" => "success",
            "result" => {
                "step-1" => {
                    "outcome" => "failed",
                    "rolled-back" => true
                },
                "step-2" => {
                    "outcome" => "failed",
                    "result" => "4",
                    "rolled-back" => true
                },
                "step-3" => undefined,
                "step-4" => {
                    "outcome" => "failed",
                    "rolled-back" => true
                },
                "step-5" => {
                    "outcome" => "failed",
                    "result" => "5",
                    "rolled-back" => true
                },

retest this please

retest this please

Core - Full Integration Build 2056 outcome was FAILURE using a merge of 00ce2ee5380338d9f81022bb44600f9fbfe9785c
Summary: Tests failed: 1 (1 new), passed: 3189, ignored: 374 Build time: 00:52:47
Failed tests
org.jboss.as.test.clustering.cluster.provider.ServiceProviderRegistrationTestCase(SYNC-tcp).test: java.lang.AssertionError: expected:<2> but was:<1>
	at org.jboss.as.test.clustering.cluster.provider.ServiceProviderRegistrationTestCase.test(ServiceProviderRegistrationTestCase.java:74)
------- Stdout: -------
01:17:22,860 INFO  [org.jboss.as.test.clustering.cluster.provider.ServiceProviderRegistrationTestCase] (main) service-provider-registration.jar:
/org/
/org/jboss/
/org/jboss/as/
/org/jboss/as/test/
/org/jboss/as/test/clustering/
/org/jboss/as/test/clustering/cluster/
/org/jboss/as/test/clustering/cluster/provider/
/org/jboss/as/test/clustering/cluster/provider/bean/
/org/jboss/as/test/clustering/cluster/provider/bean/ServiceProviderRetriever.class
/org/jboss/as/test/clustering/cluster/provider/bean/ServiceProviderRetrieverBean.class
/org/jboss/as/test/clustering/cluster/provider/bean/ServiceProviderRegistrationBean.class
01:17:22,861 INFO  [org.jboss.as.test.clustering.cluster.provider.ServiceProviderRegistrationTestCase] (main) service-provider-registration.jar:
/org/
/org/jboss/
/org/jboss/as/
/org/jboss/as/test/
/org/jboss/as/test/clustering/
/org/jboss/as/test/clustering/cluster/
/org/jboss/as/test/clustering/cluster/provider/
/org/jboss/as/test/clustering/cluster/provider/bean/
/org/jboss/as/test/clustering/cluster/provider/bean/ServiceProviderRetriever.class
/org/jboss/as/test/clustering/cluster/provider/bean/ServiceProviderRetrieverBean.class
/org/jboss/as/test/clustering/cluster/provider/bean/ServiceProviderRegistrationBean.class
01:17:22,863 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
01:17:22,864 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
01:17:22,864 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
 [0m01:17:22,880 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /opt/buildAgent/work/db872761b443af46/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/data/content/ad/4888241f157b3810a510454bb34289b92f80a3/content
 [0m [0m01:17:22,884 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "service-provider-registration.jar" (runtime-name: "service-provider-registration.jar")
 [0m [0m01:17:22,893 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment service-provider-registration.jar
 [0m [0m01:17:22,906 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'ServiceProviderRetrieverBean' in deployment unit 'deployment "service-provider-registration.jar"' are as follows:

	java:global/service-provider-registration/ServiceProviderRetrieverBean!org.jboss.as.test.clustering.cluster.provider.bean.ServiceProviderRetriever
	java:app/service-provider-registration/ServiceProviderRetrieverBean!org.jboss.as.test.clustering.cluster.provider.bean.ServiceProviderRetriever
	java:module/ServiceProviderRetrieverBean!org.jboss.as.test.clustering.cluster.provider.bean.ServiceProviderRetriever
	java:jboss/exported/service-provider-registration/ServiceProviderRetrieverBean!org.jboss.as.test.clustering.cluster.provider.bean.ServiceProviderRetriever
	java:global/service-provider-registration/ServiceProviderRetrieverBean
	java:app/service-provider-registration/ServiceProviderRetrieverBean
	java:module/ServiceProviderRetrieverBean

 [0m [0m01:17:22,906 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'ServiceProviderRegistrationBean' in deployment unit 'deployment "service-provider-registration.jar"' are as follows:

	java:global/service-provider-registration/ServiceProviderRegistrationBean!org.wildfly.clustering.provider.ServiceProviderRegistration
	java:app/service-provider-registration/ServiceProviderRegistrationBean!org.wildfly.clustering.provider.ServiceProviderRegistration
	java:module/ServiceProviderRegistrationBean!org.wildfly.clustering.provider.ServiceProviderRegistration
	java:global/service-provider-registration/ServiceProviderRegistrationBean
	java:app/service-provider-registration/ServiceProviderRegistrationBean
	java:module/ServiceProviderRegistrationBean

retest this please

Full integration - Windows Build 483 outcome was FAILURE using a merge of 00ce2ee5380338d9f81022bb44600f9fbfe9785c
Summary: Tests failed: 1 (1 new), passed: 3189, ignored: 374 Build time: 00:56:58
Failed tests
org.jboss.as.test.clustering.cluster.singleton.SingletonServiceTestCase(SYNC-tcp).testSingletonService: org.apache.http.conn.HttpHostConnectException: Connect to [::1]:8080 [/0:0:0:0:0:0:0:1] failed: Connection refused: connect
	at java.net.DualStackPlainSocketImpl.connect0(Native Method)
	at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
	at org.jboss.as.test.clustering.cluster.singleton.SingletonServiceTestCase.testSingletonService(SingletonServiceTestCase.java:219)
------- Stdout: -------
05:15:34,582 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\29\d16140caaae61c30e42f01174ae6fad212d4c1\content
05:15:34,582 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "singleton-deployment-helper.war" (runtime-name: "singleton-deployment-helper.war")
05:15:34,597 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
05:15:34,601 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
05:15:34,602 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
05:15:34,613 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\c7\49e19a99a749cca8409e61049d2893159d34b6\content
05:15:34,615 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "singleton.war" (runtime-name: "singleton.war")
05:15:34,643 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.singleton.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
05:15:34,698 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 79) WFLYUT0021: Registered web context: /singleton
05:15:34,800 WARN  [org.jgroups.protocols.MPING] (MPING) 71f4ff59-8d22-b9c7-535e-979da20ee4c8: discarding discovery request for cluster 'ee' from 71f4ff59-8d22-b9c7-535e-979da20ee4c8; our cluster name is 'activemq-cluster'. Please separate your clusters properly
05:15:34,800 WARN  [org.jgroups.protocols.MPING] (MPING) node-0: discarding discovery request for cluster 'ee' from node-0; our cluster name is 'activemq-cluster'. Please separate your clusters properly
05:15:37,838 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 79) ISPN000078: Starting JGroups channel server
05:15:37,839 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 79) ISPN000094: Received new cluster view for channel server: [node-0|0] (1) [node-0]
05:15:37,840 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 79) ISPN000079: Channel server local address is node-0, physical addresses are [0:0:0:0:0:0:0:1:7601]
05:15:37,847 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 79) WFLYCLINF0002: Started default cache from server container
05:15:37,849 INFO  [org.wildfly.clustering.server] (notification-thread--p105-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.test.myservice.default service
05:15:37,882 INFO  [org.wildfly.clustering.server] (notification-thread--p105-t1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.test.myservice.default service
05:15:37,882 ERROR [org.wildfly.clustering.server] (notification-thread--p105-t1) WFLYCLSV0006: Failed to reach quorum of 2 for jboss.test.myservice.quorum service. No singleton master will be elected.
05:15:37,897 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "singleton.war" (runtime-name : "singleton.war")
05:15:37,903 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
05:15:37,914 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\2a\ab05b7d48ad995c7b7d38a8609009aa8f580a1\content
05:15:37,916 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "singleton.war" (runtime-name: "singleton.war")
05:15:37,945 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.singleton.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
05:15:37,991 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 79) WFLYUT0021: Registered web context: /singleton
05:15:38,099 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
05:15:38,099 WARN  [org.jgroups.protocols.MPING] (MPING) node-1: discarding discovery request for cluster 'ee' from node-1; our cluster name is 'activemq-cluster'. Please separate your clusters properly
05:15:38,156 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,ee,node-0) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]
05:15:39,305 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 79) ISPN000078: Starting JGroups channel server
05:15:39,307 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 79) ISPN000094: Received new cluster view for channel server: [node-0|1] (2) [node-0, node-1]

retest this please

retest this please

Windows Build 2468 outcome was FAILURE using a merge of 00ce2ee5380338d9f81022bb44600f9fbfe9785c
Summary: Tests failed: 1 (1 new), passed: 3451, ignored: 64 Build time: 00:38:24
Failed tests
org.jboss.as.jmx.rbac.JmxRbacDisabledTestCase.testAdministratorNonSensitiveMBeans: java.lang.RuntimeException: java.security.PrivilegedActionException: javax.management.ListenerNotFoundException: Unknown listener
	at org.jboss.as.jmx.rbac.JmxRbacTestCase.checkMBeanAccess(JmxRbacTestCase.java:484)
	at org.jboss.as.jmx.rbac.JmxRbacTestCase.testAdministratorNonSensitiveMBeans(JmxRbacTestCase.java:178)
Caused by: java.security.PrivilegedActionException: null
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:422)
	at org.jboss.as.jmx.rbac.JmxRbacTestCase.checkMBeanAccess(JmxRbacTestCase.java:254)
	at org.jboss.as.jmx.rbac.JmxRbacTestCase.testAdministratorNonSensitiveMBeans(JmxRbacTestCase.java:178)
Caused by: javax.management.ListenerNotFoundException: Unknown listener
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.removeNotificationListener(DefaultMBeanServerInterceptor.java:1339)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.removeNotificationListener(DefaultMBeanServerInterceptor.java:1242)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.removeNotificationListener(JmxMBeanServer.java:870)
	at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.removeNotificationListener(PluggableMBeanServerImpl.java:1544)
	at org.jboss.as.jmx.PluggableMBeanServerImpl.removeNotificationListener(PluggableMBeanServerImpl.java:969)
	at org.jboss.as.jmx.rbac.JmxRbacTestCase$1.run(JmxRbacTestCase.java:368)
	at org.jboss.as.jmx.rbac.JmxRbacTestCase$1.run(JmxRbacTestCase.java:254)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:422)
	at org.jboss.as.jmx.rbac.JmxRbacTestCase.checkMBeanAccess(JmxRbacTestCase.java:254)
	at org.jboss.as.jmx.rbac.JmxRbacTestCase.testAdministratorNonSensitiveMBeans(JmxRbacTestCase.java:178)

Linux Build 2979 outcome was FAILURE using a merge of 00ce2ee5380338d9f81022bb44600f9fbfe9785c
Summary: Execution timeout (new); tests passed: 3041, ignored: 48 Build time: 01:00:15

Full integration - Windows Build 511 outcome was FAILURE using a merge of f9db7523bf61ca887c9c05b98f8b57634b7a5df0
Summary: Tests failed: 5 (5 new), passed: 3186, ignored: 374 Build time: 01:05:40
Failed tests
org.jboss.as.test.integration.management.api.ModelPersistenceTestCase.testSimpleOperation: java.lang.AssertionError: null
	at org.jboss.as.test.integration.management.api.ModelPersistenceTestCase.testSimpleOperation(ModelPersistenceTestCase.java:119)
------- Stdout: -------
21:50:18,304 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0268: Failed to rename temp file C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml.tmp to C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0268: Failed to rename temp file C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml.tmp to C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml
	at org.jboss.as.controller.persistence.FilePersistenceUtils.moveTempFileToMain(FilePersistenceUtils.java:89)
	at org.jboss.as.controller.persistence.ConfigurationFile.commitTempFile(ConfigurationFile.java:538)
	at org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.doCommit(ConfigurationFilePersistenceResource.java:63)
	at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.commit(AbstractFilePersistenceResource.java:58)
	at org.jboss.as.controller.ModelControllerImpl$4.commit(ModelControllerImpl.java:781)
	at org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:743)
	at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:680)
	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
	at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1336)
	at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
	at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:207)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:129)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:151)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:147)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:422)
	at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:147)
	at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:364)
	at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:466)
	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)
	at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.nio.file.FileSystemException: C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml: The process cannot access the file because it is being used by another process.

	at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
	at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
	at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
	at sun.nio.fs.WindowsFileCopy.copy(WindowsFileCopy.java:165)
	at sun.nio.fs.WindowsFileSystemProvider.copy(WindowsFileSystemProvider.java:278)
	at java.nio.file.Files.copy(Files.java:1274)
	at org.jboss.as.controller.persistence.FilePersistenceUtils.copyFile(FilePersistenceUtils.java:73)
	at org.jboss.as.controller.persistence.FilePersistenceUtils.rename(FilePersistenceUtils.java:78)
	at org.jboss.as.controller.persistence.FilePersistenceUtils.moveTempFileToMain(FilePersistenceUtils.java:85)
	... 24 more

org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.testHashedBase64: java.lang.AssertionError: Unexpected status code returned after the authentication. expected:<200> but was:<401>
	at org.jboss.as.test.integration.security.common.Utils.makeCallWithBasicAuthn(Utils.java:458)
	at org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.testAccess(DatabaseLoginModuleTestCase.java:186)
	at org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.testHashedBase64(DatabaseLoginModuleTestCase.java:159)
------- Stdout: -------
21:50:52,314 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 2) WFLYUT0022: Unregistered web context: /custom-login-module
21:50:52,326 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment custom-login-module.war (runtime-name: custom-login-module.war) in 11ms
21:50:52,333 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0268: Failed to rename temp file C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml.tmp to C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0268: Failed to rename temp file C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml.tmp to C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml
	at org.jboss.as.controller.persistence.FilePersistenceUtils.moveTempFileToMain(FilePersistenceUtils.java:89)
	at org.jboss.as.controller.persistence.ConfigurationFile.commitTempFile(ConfigurationFile.java:538)
	at org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.doCommit(ConfigurationFilePersistenceResource.java:63)
	at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.commit(AbstractFilePersistenceResource.java:58)
	at org.jboss.as.controller.ModelControllerImpl$4.commit(ModelControllerImpl.java:781)
	at org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:743)
	at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:680)
	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
	at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1336)
	at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
	at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:207)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:129)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:151)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:147)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:422)
	at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:147)
	at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:364)
	at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:466)
	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)
	at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.nio.file.FileSystemException: C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml: The process cannot access the file because it is being used by another process.

	at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
	at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
	at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
	at sun.nio.fs.WindowsFileCopy.copy(WindowsFileCopy.java:165)
	at sun.nio.fs.WindowsFileSystemProvider.copy(WindowsFileSystemProvider.java:278)
	at java.nio.file.Files.copy(Files.java:1274)
	at org.jboss.as.controller.persistence.FilePersistenceUtils.copyFile(FilePersistenceUtils.java:73)
	at org.jboss.as.controller.persistence.FilePersistenceUtils.rename(FilePersistenceUtils.java:78)
	at org.jboss.as.controller.persistence.FilePersistenceUtils.moveTempFileToMain(FilePersistenceUtils.java:85)
	... 24 more

21:50:52,336 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0002: Content removed from location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\data\content\bb\c96e78971ef8e467a75afbe5008909185d0d68\content
21:50:52,336 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0009: Undeployed "custom-login-module.war" (runtime-name: "custom-login-module.war")
21:50:52,347 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0268: Failed to rename temp file C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml.tmp to C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0268: Failed to rename temp file C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml.tmp to C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml
	at org.jboss.as.controller.persistence.FilePersistenceUtils.moveTempFileToMain(FilePersistenceUtils.java:89)
	at org.jboss.as.controller.persistence.ConfigurationFile.commitTempFile(ConfigurationFile.java:538)

org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.testHashedHex: java.lang.AssertionError: Unexpected status code returned after the authentication. expected:<200> but was:<401>
	at org.jboss.as.test.integration.security.common.Utils.makeCallWithBasicAuthn(Utils.java:458)
	at org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.testAccess(DatabaseLoginModuleTestCase.java:186)
	at org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.testHashedHex(DatabaseLoginModuleTestCase.java:168)
------- Stdout: -------
21:50:53,838 INFO  [org.jboss.as.test.integration.security.common.Utils] (main) Requesting URL http://[::1]:8080/DEP4/SimpleSecuredServlet

org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.testDefault: java.lang.AssertionError: Unexpected status code returned after the authentication. expected:<200> but was:<401>
	at org.jboss.as.test.integration.security.common.Utils.makeCallWithBasicAuthn(Utils.java:458)
	at org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.testAccess(DatabaseLoginModuleTestCase.java:186)
	at org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.testDefault(DatabaseLoginModuleTestCase.java:141)
------- Stdout: -------
21:50:53,853 INFO  [org.jboss.as.test.integration.security.common.Utils] (main) Requesting URL http://[::1]:8080/DEP1/SimpleSecuredServlet

org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.testHashed: java.lang.AssertionError: Unexpected status code returned after the authentication. expected:<200> but was:<401>
	at org.jboss.as.test.integration.security.common.Utils.makeCallWithBasicAuthn(Utils.java:458)
	at org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.testAccess(DatabaseLoginModuleTestCase.java:186)
	at org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase.testHashed(DatabaseLoginModuleTestCase.java:150)
------- Stdout: -------
21:50:53,867 INFO  [org.jboss.as.test.integration.security.common.Utils] (main) Requesting URL http://[::1]:8080/DEP2/SimpleSecuredServlet

retest this please

Full integration - Windows Build 524 outcome was FAILURE using a merge of 2cf651da9a7c20bae6c2c100885250d8d35016d7
Summary: Execution timeout (new); tests passed: 550, ignored: 149 Build time: 01:17:19

@rhusar @kabir the "Full integration - Windows" job that timed out in the previous comment hung here:
[03:08:57][org.wildfly:wildfly-clustering-infinispan-extension] Running org.jboss.as.clustering.infinispan.subsystem.TransformersTestCase
[04:17:32][org.wildfly:wildfly-clustering-infinispan-extension] The build Pull Request::WildFly Core Full - Integration - Windows #524 {buildId=74614} has been running for more than 75 minutes. Terminating...
Unfortunately on the Windows runs the thread dump captured in the Team City build log doesn't include the relevant processes.
That hang is very unlikely to be related to this PR, as this PR is about remote communication between separate processes and the subsystem unit tests do not rely on that.

retest this please

The only known hang now is on https://issues.jboss.org/browse/WFLY-5290 but I don't see how that would be now triggerd with this change. Anyway any additional info would be very helpful.

@rhusar I don't believe the hang I reported has anything to do with this PR. I think it was just my bad luck that it happened to this one.

retest this please

retest this please

Core - Full Integration Build 2114 outcome was FAILURE using a merge of 0426234b42dc6d2c056ea8678168b296c6fdd15c
Summary: Tests failed: 1 (1 new), passed: 3202, ignored: 369 Build time: 00:52:48
Failed tests
org.jboss.as.test.integration.ejb.mdb.ejb2x.MDB20TopicTestCase.testEjb20TopicMDBs: java.lang.AssertionError: Reply message was null on reply queue: ActiveMQQueue[ejb2x/replyQueueA]
	at org.jboss.as.test.integration.ejb.mdb.ejb2x.MDB20TopicTestCase.testEjb20TopicMDBs(MDB20TopicTestCase.java:117)
------- Stdout: -------
 [0m16:16:09,894 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment mdb.jar (runtime-name: mdb.jar) in 25ms
 [0m [0m16:16:09,899 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0002: Content removed from location /opt/buildAgent/work/db872761b443af46/full/testsuite/integration/basic/target/jbossas/standalone/data/content/4c/e1c7612139f3384b6577cb3db94a89eca445c1/content
 [0m [0m16:16:09,899 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0009: Undeployed "mdb.jar" (runtime-name: "mdb.jar")
 [0m16:16:09,917 INFO  [org.jboss.as.test.integration.common.jms.JMSOperationsProvider] (main) Operation successful for update = {
    "operation" => "remove",
    "address" => [
        ("subsystem" => "messaging-activemq"),
        ("server" => "default"),
        ("jms-queue" => "ejb2x/queue")
    ]
}
16:16:09,928 INFO  [org.jboss.as.test.integration.common.jms.JMSOperationsProvider] (main) Operation successful for update = {
    "operation" => "remove",
    "address" => [
        ("subsystem" => "messaging-activemq"),
        ("server" => "default"),
        ("jms-queue" => "ejb2x/replyQueue")
    ]
}
16:16:09,934 INFO  [org.jboss.as.test.integration.ejb.mdb.ejb2x.AbstractMDB2xTestCase] (main) MDB20TopicTestCase.jar:
/org/
/org/jboss/
/org/jboss/as/
/org/jboss/as/test/
/org/jboss/as/test/integration/
/org/jboss/as/test/integration/ejb/
/org/jboss/as/test/integration/ejb/mdb/
/org/jboss/as/test/integration/ejb/mdb/ejb2x/
/org/jboss/as/test/integration/ejb/mdb/ejb2x/MDB20TopicTestCase$JmsQueueSetup.class
/org/jboss/as/test/integration/ejb/mdb/ejb2x/EJB2xMDB.class
/org/jboss/as/test/integration/ejb/mdb/ejb2x/AbstractMDB2xTestCase.class
/org/jboss/as/test/integration/common/
/org/jboss/as/test/integration/common/jms/
/org/jboss/as/test/integration/common/jms/JMSOperations.class
/org/jboss/as/test/integration/common/jms/JMSOperationsProvider.class
/org/jboss/as/test/integration/common/jms/ActiveMQProviderJMSOperations.class
/org/jboss/as/test/integration/common/jms/JMSOperationsException.class
/org/jboss/as/test/shared/
/org/jboss/as/test/shared/TimeoutUtil.class
/META-INF/
/META-INF/MANIFEST.MF
/META-INF/ejb-jar.xml
/META-INF/jboss-ejb3.xml
 [0m16:16:09,951 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 29) AMQ221003: trying to deploy queue jms.topic.ejb2x/topic
 [0m16:16:09,964 INFO  [org.jboss.as.test.integration.common.jms.JMSOperationsProvider] (main) Operation successful for update = {
    "operation" => "add",
    "address" => [
        ("subsystem" => "messaging-activemq"),

retest this please

Full integration - Windows Build 557 outcome was FAILURE using a merge of 0426234b42dc6d2c056ea8678168b296c6fdd15c
Summary: Tests failed: 1 (1 new), passed: 3202, ignored: 369 Build time: 00:54:40
Failed tests
org.jboss.as.test.integration.management.api.ModelPersistenceTestCase.testSimpleOperation: java.lang.AssertionError: null
	at org.jboss.as.test.integration.management.api.ModelPersistenceTestCase.testSimpleOperation(ModelPersistenceTestCase.java:119)
------- Stdout: -------
12:46:38,441 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0081: Failed to back up C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0081: Failed to back up C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml
	at org.jboss.as.controller.persistence.ConfigurationFile.fileWritten(ConfigurationFile.java:552)
	at org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.doCommit(ConfigurationFilePersistenceResource.java:65)
	at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.commit(AbstractFilePersistenceResource.java:58)
	at org.jboss.as.controller.ModelControllerImpl$4.commit(ModelControllerImpl.java:781)
	at org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:743)
	at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:680)
	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
	at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1336)
	at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
	at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:207)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:129)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:151)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:147)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:422)
	at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:147)
	at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:364)
	at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:466)
	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)
	at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.nio.file.FileSystemException: C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone_xml_history\standalone.last.xml: The process cannot access the file because it is being used by another process.

	at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
	at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
	at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
	at sun.nio.fs.WindowsFileCopy.copy(WindowsFileCopy.java:165)
	at sun.nio.fs.WindowsFileSystemProvider.copy(WindowsFileSystemProvider.java:278)
	at java.nio.file.Files.copy(Files.java:1274)
	at org.jboss.as.controller.persistence.FilePersistenceUtils.copyFile(FilePersistenceUtils.java:73)
	at org.jboss.as.controller.persistence.ConfigurationFile.fileWritten(ConfigurationFile.java:550)
	... 23 more

retest this please

retest this please

retest this please

Linux Build 3069 outcome was FAILURE using a merge of 21a0d6893d37665fe82ced7590337838a3f1d2ed
Summary: Tests failed: 1 (1 new), passed: 3451, ignored: 64 Build time: 00:37:02
Failed tests
org.jboss.as.test.manualmode.deployment.DeploymentScannerUnitTestCase.testStartup: java.lang.AssertionError: null
	at org.jboss.as.test.manualmode.deployment.DeploymentScannerUnitTestCase.testStartup(DeploymentScannerUnitTestCase.java:135)
------- Stdout: -------
04:10:47,483 INFO  [org.wildfly.core.testrunner.Server] (main) Starting container with: /usr/java/jdk1.8.0_40/jre/bin/java -D[Standalone] -javaagent:/store/repository/org/jboss/byteman/byteman/2.2.1/byteman-2.2.1.jar=port:9091,boot:/store/repository/org/jboss/byteman/byteman/2.2.1/byteman-2.2.1.jar,sys:/opt/buildAgent/work/8d74ae55e497982e/testsuite/shared/target/wildfly-core-testsuite-shared-2.0.0.CR8-SNAPSHOT.jar -Dorg.jboss.byteman.transform.all -Dorg.jboss.byteman.verbose=true -Dmaven.repo.local=/store/repository -Xmx512m -Djboss.dist=/opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode/target/wildfly-core -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -server -Dts.timeout.factor=100 -Djbossas.ts.dir=/opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode -ea -Dorg.jboss.boot.log.file=/opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode/target/wildfly-core/standalone/log/server.log -Dlogging.configuration=file:/opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode/target/wildfly-core/standalone/configuration/logging.properties -jar /opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode/target/wildfly-core/jboss-modules.jar -mp /opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode/target/wildfly-core/modules org.jboss.as.standalone -Djboss.home.dir=/opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode/target/wildfly-core -Djboss.server.base.dir=/opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode/target/wildfly-core/standalone -Djboss.server.log.dir=/opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode/target/wildfly-core/standalone/log -Djboss.server.config.dir=/opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode/target/wildfly-core/standalone/configuration -c=standalone.xml -bmanagement=::1 -Djboss.http.port=8080 -Djboss.bind.address=::1
04:10:47,658 INFO  [org.xnio] (main) XNIO version 3.3.2.Final
TransformListener() : accepting requests on localhost:9091
04:10:47,809 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.2.Final
04:10:47,910 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.14.Final
 [0m04:10:48,184 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
 [0m [0m04:10:48,482 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
 [0m [0m04:10:48,588 INFO  [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Core 2.0.0.CR8-SNAPSHOT "Kenny" starting
 [0m [0m04:10:49,205 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m04:10:49,226 INFO  [org.xnio] (MSC service thread 1-3) XNIO version 3.3.2.Final
 [0m [0m04:10:49,261 INFO  [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.3.2.Final
 [0m [0m04:10:49,370 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.14.Final
 [0m [33m04:10:49,386 WARN  [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-2) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console
 [0m [0m04:10:49,589 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9990/management
 [0m [0m04:10:49,590 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://[::1]:9990
 [0m [0m04:10:49,590 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.0.0.CR8-SNAPSHOT "Kenny" started in 1866ms - Started 55 of 57 services (15 services are lazy, passive or on-demand)
 [0m [0m04:10:49,977 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode/target/deployment-test-da68b007-cb93-433d-b88b-1ee89283c557
 [0m [0m04:10:50,003 INFO  [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location /opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode/target/wildfly-core/standalone/data/content/63/697a5daaf9cefccb2130632ed4ff64667c8953/content
 [0m [0m04:10:50,017 INFO  [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location /opt/buildAgent/work/8d74ae55e497982e/testsuite/manualmode/target/wildfly-core/standalone/data/content/1f/d0e28b3c4aa0ac341a6ce0a0588724aa19080a/content
 [0m [0m04:10:50,034 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "deployment-one.jar" (runtime-name: "deployment-one.jar")
 [0m [0m04:10:50,035 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "deployment-two.jar" (runtime-name: "deployment-two.jar")
 [0m [31m04:10:50,069 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.module.service."deployment.deployment-two.jar".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.deployment-two.jar".main: WFLYSRV0179: Failed to load module: deployment.deployment-two.jar:main
	at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.modules.ModuleNotFoundException: non.existing.dependency:main
	at org.jboss.modules.Module.addPaths(Module.java:1042)
	at org.jboss.modules.Module.link(Module.java:1398)
	at org.jboss.modules.Module.relinkIfNecessary(Module.java:1426)
	at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:238)
	at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68)
	... 5 more

 [0m [31m04:10:50,075 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "deployment-two.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.deployment-two.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.deployment-two.jar\".main: WFLYSRV0179: Failed to load module: deployment.deployment-two.jar:main