[
https://issues.jboss.org/browse/AS7-1242?page=com.atlassian.jira.plugin.s...
]
Karel Piwko reopened AS7-1242:
------------------------------
This is broken with current version.
{code}
[kpiwko@kapy-ntb jboss-as-7.1.0.Alpha1-SNAPSHOT]$ ./bin/standalone.sh -server-config
standalone-ha.xml
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/kpiwko/party/1/jboss-as-7.1.0.Alpha1-SNAPSHOT
JAVA: /opt/jdk1.6.0_24/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
-Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman
-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
=========================================================================
Listening for transport dt_socket at address: 8787
14:00:28,926 INFO [org.jboss.modules] JBoss Modules version 1.0.1.GA
14:00:29,386 INFO [org.jboss.msc] JBoss MSC version 1.0.0.GA
14:00:29,451 INFO [org.jboss.as] JBoss AS 7.1.0.Alpha1-SNAPSHOT "Lightning"
starting
14:00:31,445 INFO [org.jboss.as] creating http management service using network interface
(management) port (19990) securePort (-1)
14:00:31,459 INFO [org.jboss.as.logging] Removing bootstrap log handlers
14:00:31,494 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot
Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
14:00:31,513 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread)
Activating Infinispan subsystem.
14:00:31,645 INFO [org.jboss.as.clustering.jgroups.subsystem] (Controller Boot Thread)
Activating JGroups subsystem.
14:00:31,658 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
14:00:31,673 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming
Subsystem
14:00:31,682 INFO [org.jboss.as.naming] (MSC service thread 1-3) Starting Naming Service
14:00:31,690 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security
Subsystem
14:00:31,698 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version
3.2.0.Beta2
14:00:31,725 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.0.Beta3
14:00:31,737 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version
3.0.0.Beta3
14:00:31,861 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread
1-1) The Apache Tomcat Native library which allows optimal performance in production
environments was not found on the java.library.path:
/opt/jdk1.6.0_24/jre/lib/amd64/server:/opt/jdk1.6.0_24/jre/lib/amd64:/opt/jdk1.6.0_24/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
14:00:31,906 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1)
Starting remote JMX connector
14:00:31,908 INFO [org.jboss.as.remoting] (MSC service thread 1-3) Listening on
/127.0.0.1:19999
14:00:31,914 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
14:00:31,956 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4)
Starting Coyote HTTP/1.1 on http--127.0.0.1-8180
14:00:32,093 INFO [org.jboss.as.modcluster] (MSC service thread 1-3) Mod_cluster uses
default load balancer provider
14:00:32,147 INFO [org.jboss.modcluster.ModClusterService] (MSC service thread 1-3)
Initializing mod_cluster 1.1.2.Final
14:00:32,189 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC
service thread 1-3) Listening to proxy advertisements on 224.0.1.105:23364
14:00:32,251 INFO [org.jboss.as.connector] (MSC service thread 1-2) Starting JCA
Subsystem (JBoss IronJacamar 1.0.1.Final)
14:00:32,332 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread
1-1) Bound data source [java:jboss/datasources/ExampleDS]
14:00:32,630 INFO [org.jboss.as.deployment] (MSC service thread 1-2) Started
FileSystemDeploymentService for directory
/home/kpiwko/party/1/jboss-as-7.1.0.Alpha1-SNAPSHOT/standalone/deployments
14:00:32,647 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.Alpha1-SNAPSHOT
"Lightning" started in 4173ms - Started 94 of 170 services (76 services are
passive or on-demand)
14:00:51,474 INFO [org.jboss.as.server.deployment] (pool-1-thread-1) Content added at
location
/home/kpiwko/party/1/jboss-as-7.1.0.Alpha1-SNAPSHOT/standalone/data/content/fd/1774722b37f895cece6906c644290b2c6af601/content
14:00:51,489 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting
deployment of "distributable1.war"
14:00:51,573 INFO [org.jboss.as.jpa] (MSC service thread 1-1) added javax.persistence.api
dependency to distributable1.war
14:00:51,777 INFO [org.jboss.as.server.controller] (pool-1-thread-1) Deployment of
"distributable1.war" was rolled back with failure message {"Services with
missing/unavailable dependencies" =>
["jboss.deployment.unit.\"distributable1.war\".CONFIGURE_MODULE missing [
jboss.module.information.service.\"deployment.arquillian-service\".main
]"]}
14:00:51,797 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Stopped
deployment distributable1.war in 19ms
14:00:51,840 ERROR [org.jboss.as.controller] (pool-1-thread-1) Operation
("undeploy") failed - address: ([("deployment" =>
"distributable1.war")]): java.util.NoSuchElementException: No child
'runtime-name' exists
at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:362)
at org.jboss.dmr.ModelNode.require(ModelNode.java:703)
at
org.jboss.as.server.deployment.DeploymentUndeployHandler.execute(DeploymentUndeployHandler.java:58)
at
org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:351)
at
org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:298)
at
org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:223)
at
org.jboss.as.controller.CompositeOperationHandler.execute(CompositeOperationHandler.java:83)
at
org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:351)
at
org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:298)
at
org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:223)
at
org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:350)
at
org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:351)
at
org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:298)
at
org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:223)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:119)
at
org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doProcessRequest(ModelControllerClientOperationHandler.java:154)
at
org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$100(ModelControllerClientOperationHandler.java:85)
at
org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.call(ModelControllerClientOperationHandler.java:114)
at
org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.call(ModelControllerClientOperationHandler.java:112)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_24]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
{code}
arquillian-service is only deployed to first container in group
---------------------------------------------------------------
Key: AS7-1242
URL:
https://issues.jboss.org/browse/AS7-1242
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.CR1
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 7.0.1.Final
When using the Arquillian group feature with the JBoss AS 7 remote container adapter, the
arquillian-service is only deployed to the first container. For an example of the problem,
see the multinode example in the Arquillian showcase [1].
The test only runs if I use servers that already have the arquillian-service deployed.
http://github.com/arquillian/arquillian-showcase
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira