[jboss-jira] [JBoss JIRA] Created: (AS7-750) Deploy fails if any server is stopped

Deploy fails if any server is stopped ------------------------------------- Key: AS7-750 URL: https://issues.jboss.org/browse/AS7-750 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Beta3 Reporter: Stan Silvert Assignee: Jason Greene I have the default setup which has a "main-server-group" with two servers, "server-one" and "server-two". I stop server-two using the admin console. Then I go to the CLI and try to deploy something to the main-server-group with this command: [domain@localhost:9999 /] deploy --server-groups=main-server-group C:\as7trunk\as7jsf\mojarra2.0\beanvalidation\target\beanvalidation.war Operation was not applied successfully to any servers In the domain console, I get: [Server:server-one] 13:16:43,432 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) Starting deployment of "beanvalidation.war" [Server:server-one] 13:16:43,443 WARN [org.jboss.vfs] (MSC service thread 1-6) VFS was unable to set the URLStreamHandlerFactory. This will have unpredictable results [Server:server-one] 13:16:44,099 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-6) Initializing Mojarra 2.0.4 (FCS b09) for context '/bea nvalidation' [Server:server-one] 13:16:44,697 INFO [javax.enterprise.resource.webcontainer.jsf.application] (MSC service thread 1-6) JSF1048: PostConstruct/PreDestroy annotations pre sent. ManagedBeans methods marked with these annotations will have said annotations processed. [Server:server-one] 13:16:44,907 INFO [org.jboss.web] (MSC service thread 1-6) registering web context: /beanvalidation [Server:server-one] 13:16:44,989 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Stopped deployment beanvalidation.war in 71ms I don't see any reason why this shouldn't work for server-one, which is still running. In fact, it does deploy the application but for some reason it also stops it. Also, if I check the deployment it says that it is enabled, which is only half-true. It's enabled, but it's not running. [domain@localhost:9999 /] /server-group=main-server-group:read-children-resources(child-type=deployment) { "outcome" => "success", "result" => [("beanvalidation.war" => { "name" => "beanvalidation.war", "runtime-name" => "beanvalidation.war", "hash" => bytes { 0xc6, 0x1d, 0xa1, 0xd2, 0x8a, 0x4c, 0xd4, 0xe9, 0x01, 0xe3, 0xe6, 0x6e, 0xb7, 0xbd, 0x98, 0x47, 0x82, 0xfc, 0x30, 0xc4 }, "enabled" => true })], "compensating-operation" => undefined } I restart the domain and both servers in the main-server-group are started. So stopping the server from the admin console was not "sticky". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira