Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[WFCORE-1257] Handle QueryExp passed into ModelControllerMBeanServerPlugin #1335

Merged
merged 1 commit into from Jan 23, 2016
Merged

[WFCORE-1257] Handle QueryExp passed into ModelControllerMBeanServerPlugin #1335

merged 1 commit into from Jan 23, 2016

Conversation

bstansberry
Copy link
Contributor

No description provided.

@wildfly-ci
Copy link

Full integration - Windows Build 935 outcome was FAILURE using a merge of 875e977
Summary: Execution timeout (new); tests failed: 67 (67 new), passed: 2894, ignored: 173 Build time: 01:16:42

Failed tests

org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
23:35:35,326 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:90)

23:35:35,481 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
23:35:36,505 WARNING [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Bundles path is deprecated and no longer used.
23:35:36,507 INFO  [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [C:\Java\jdk1.8.0_45\bin\java, -D[Standalone], -Dorg.jboss.ejb.client.wildfly-testsuite-hack=true, -Xmx512m, -Djboss.dist=C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering/../../../dist/target/wildfly-10.0.0.Final-SNAPSHOT, -Djava.net.preferIPv4Stack=false, -Djava.net.preferIPv6Addresses=true, -server, -Dts.timeout.factor=100, -Dnode0=::1, -Dnode1=::1, -Dmcast=ff13::1, -Dmcast.ttl=0, -Djbossas.ts.submodule.dir=C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering, -Djbossas.ts.integ.dir=C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering/.., -Djbossas.ts.dir=C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering/../.., -Djbossas.project.dir=C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering/../../.., -Djboss.inst=C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering/target/wildfly-SYNC-tcp-1, -Djboss.node.name=node-1, -Djboss.port.offset=100, -ea, -Djboss.home.dir=C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1, -Dorg.jboss.boot.log.file=C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\log\server.log, -Dlogging.configuration=file:C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\configuration\logging.properties, -jar, C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\jboss-modules.jar, -mp, C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\modules;C:\BuildAgent\work\db872761b443af46\full\dist\target\wildfly-10.0.0.Final-SNAPSHOT\modules;C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\modules, org.jboss.as.standalone, -Djboss.home.dir=C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1, -Djboss.server.base.dir=C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone, -Djboss.server.log.dir=C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\log, -Djboss.server.config.dir=C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\configuration, -Dts.wildfly.version=10.0.0.Final-SNAPSHOT, -c=standalone-full-ha.xml]
23:35:36,558 INFO  [org.xnio] (main) XNIO version 3.3.4.Final
23:35:36,660 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.3.4.Final
23:35:36,794 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.17.Final-wildfly-1
23:35:37,269 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.0.Final
23:35:37,714 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
23:35:37,857 INFO  [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 10.0.0.Final-SNAPSHOT (WildFly Core 2.0.6.Final-SNAPSHOT) starting
23:35:41,403 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
23:35:41,503 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.3.4.Final
23:35:41,514 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.4.Final
23:35:41,628 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 68) WFLYWS0002: Activating WebServices Extension
23:35:41,624 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 66) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
23:35:41,702 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 57) WFLYNAM0001: Activating Naming Subsystem
23:35:41,805 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 64) WFLYSEC0002: Activating Security Subsystem
23:35:41,807 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 52) WFLYJSF0007: Activated the following JSF Implementations: [main]
23:35:41,811 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 44) WFLYCLINF0001: Activating Infinispan subsystem.
23:35:41,831 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 43) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
23:35:41,867 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 49) WFLYCLJG0001: Activating JGroups subsystem.
23:35:41,902 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 45) WFLYIIOP0001: Activating IIOP Subsystem
23:35:41,920 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 1.3.11.Final starting
23:35:41,920 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0003: Undertow 1.3.11.Final starting
23:35:41,950 INFO  [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=4.9.4.Final
23:35:41,973 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 39) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
23:35:41,991 INFO  [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.1.Final)
23:35:41,996 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
23:35:42,141 INFO  [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service
23:35:42,155 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
23:35:42,157 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.17.Final-wildfly-1
23:35:42,744 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0014: Creating file handler for path 'C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
23:35:42,858 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
23:35:42,866 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0018: Host default-host starting
23:35:43,022 INFO  [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
23:35:43,036 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
23:35:43,071 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on [::1]:8180
23:35:43,073 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow AJP listener ajp listening on [::1]:8009
23:35:43,097 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 71) MODCLUSTER000001: Initializing mod_cluster version 1.3.1.Final
23:35:43,202 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 71) MODCLUSTER000032: Listening to proxy advertisements on /ff13:0:0:0:0:0:0:1:23364


org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
23:35:49,254 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:90)

23:35:49,258 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
23:35:49,259 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0


org.jboss.as.test.clustering.cluster.dispatcher.CommandDispatcherTestCase(SYNC-tcp).test: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
23:35:49,295 INFO  [org.jboss.as.test.clustering.cluster.dispatcher.CommandDispatcherTestCase] (main) command-dispatcher.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/dispatcher/
/org/jboss/as/test/clustering/cluster/dispatcher/bean/
/org/jboss/as/test/clustering/cluster/dispatcher/bean/ClusterTopology.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/CommandDispatcherBean.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/TestCommand.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/CommandDispatcherFactoryBean.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/ClusterTopologyRetriever.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/ClusterTopologyRetrieverBean.class
23:35:49,297 INFO  [org.jboss.as.test.clustering.cluster.dispatcher.CommandDispatcherTestCase] (main) command-dispatcher.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/dispatcher/
/org/jboss/as/test/clustering/cluster/dispatcher/bean/
/org/jboss/as/test/clustering/cluster/dispatcher/bean/ClusterTopology.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/CommandDispatcherBean.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/TestCommand.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/CommandDispatcherFactoryBean.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/ClusterTopologyRetriever.class
/org/jboss/as/test/clustering/cluster/dispatcher/bean/ClusterTopologyRetrieverBean.class
23:35:49,305 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:90)

23:35:49,308 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
23:35:49,309 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0


org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).failoverOnStop: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
23:35:49,358 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:90)

23:35:49,362 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
23:35:49,362 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0


org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).nestedBeanFailover: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
23:35:49,380 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:90)

23:35:49,384 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
23:35:49,384 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0


org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).connectionFactoryFailover: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
23:35:49,398 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:90)

23:35:49,402 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
23:35:49,402 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0


org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).jmsConnectionFactoryFailover: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
23:35:49,411 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:90)

23:35:49,417 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
23:35:49,417 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0


org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).noFailover: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
23:35:49,428 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:90)

23:35:49,431 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
23:35:49,432 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0


org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).simpleFailover: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
23:35:49,439 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:90)

23:35:49,442 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
23:35:49,442 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0


org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulTimeoutTestCase(SYNC-tcp).timeout: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
23:35:49,471 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:90)

23:35:49,474 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
23:35:49,474 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0


org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testBasicXPC: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:91)
------- Stdout: -------
23:35:49,503 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.beforeTestMethod(ClusterAbstractTestCase.java:90)

23:35:49,507 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
23:35:49,507 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0



##### there are 57 more failed tests, see build details

@wildfly-ci
Copy link

Core - Full Integration Build 2500 outcome was FAILURE using a merge of 875e977
Summary: Execution timeout (new); tests passed: 3125, ignored: 191 Build time: 01:16:43

@bstansberry
Copy link
Contributor Author

retest this please

@jamezp jamezp added the ready-for-merge This PR is ready to be merged and fulfills all requirements label Jan 22, 2016
bstansberry added a commit that referenced this pull request Jan 23, 2016
@bstansberry
Merge pull request #1335 from bstansberry/WFCORE-1257
e7a7292 
[WFCORE-1257] Handle QueryExp passed into ModelControllerMBeanServerPlugin
@bstansberry bstansberry merged commit e7a7292 into wildfly:master Jan 23, 2016
@bstansberry bstansberry deleted the WFCORE-1257 branch January 23, 2016 00:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
ready-for-merge This PR is ready to be merged and fulfills all requirements
Projects
None yet
Milestone
No milestone
3 participants
@bstansberry @wildfly-ci @jamezp