[jboss-jira] [JBoss JIRA] (JBASMP-71) JBoss Maven Plugin fails deploy in domain mode if one server is stopped

[Chris Dollar (JIRA)]

    [ https://issues.jboss.org/browse/JBASMP-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042163#comment-13042163 ] 

Chris Dollar commented on JBASMP-71:
------------------------------------

I'd like to add my vote to have this pull request merged in.

I'm actually an EAP customer and I had logged a support request dealing with the plugin not allowing me to deploy. As it turns out the reason for the failure was not all the servers in my server group were started (and support pointed me to this pull request). In my particular use case our business traffic coincides with normal school years, so our peak traffic comes during the start of a new school semester. With our managed servers we start more instances during peak times to handle the load, and shut them down as our load decreases. This means that most of the time we have managed servers defined in our domain that are not started.

Chris

> JBoss Maven Plugin fails deploy in domain mode if one server is stopped
> -----------------------------------------------------------------------
>
>                 Key: JBASMP-71
>                 URL: https://issues.jboss.org/browse/JBASMP-71
>             Project: JBoss AS Maven Plugins
>          Issue Type: Bug
>          Components: deploy
>    Affects Versions: 7.5.Final
>            Reporter: Jorge Solorzano
>            Assignee: James Perkins
>
> I have a cluster in domain mode and configured my project to do the deploy on a server group (jboss-as:deploy), but if I have one server stopped the deploy fails.
> I think it should do the deploy even if all servers are stopped, after all the master is the one who get the deploy and when the servers come back online then the master sends the content to the servers.
> If I do the deploy directly from the manangement console it don't care if all servers (in the server group) are stopped.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)