[jboss-jira] [JBoss JIRA] (WFLY-4314) Add blocking option to reload command for standalone server
Tomas Rohovsky (JIRA)
issues at jboss.org
Thu Feb 5 03:54:49 EST 2015
[ https://issues.jboss.org/browse/WFLY-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037760#comment-13037760 ]
Tomas Rohovsky commented on WFLY-4314:
--------------------------------------
Brian thanks for the prompt answer. I tied to use reload without colon and I got {{Command execution failed for command ' reload'. Unsupported ModelControllerClient implementation org.jboss.as.plugin.cli.Commands$NonClosingModelControllerClient}}. It looks to be this issue JBASMP-59. I tried to execute it with jboss-cli.sh as well. The result was {{if request failed: JBAS013493: System boot is in process; execution of remote management operations is not currently available}}. Any of these two ways didn't changed standalone-full.xml.
> Add blocking option to reload command for standalone server
> -----------------------------------------------------------
>
> Key: WFLY-4314
> URL: https://issues.jboss.org/browse/WFLY-4314
> Project: WildFly
> Issue Type: Enhancement
> Components: Domain Management
> Affects Versions: JBoss AS7 7.2.0.Final, 8.2.0.Final
> Reporter: Tomas Rohovsky
> Assignee: Brian Stansberry
>
> reload command is non-blocking which causes problems in CLI scripts. Let's take this as an example:
> {code}
> if (outcome == failed) of /subsystem=resource-adapters/resource-adapter=activemq-ra:read-resource
> /subsystem=resource-adapters/resource-adapter=activemq-ra:add(archive=activemq-ra.rar)
> :reload
> end-if
> {code}
> I use jboss-as-maven-plugin for its execution and sometimes I get: {Command execution failed for command 'end-if'. if request failed: java.util.concurrent.ExecutionException: Operation failed: Channel closed}
> This functionality has already been asked in WFLY-208, but for some reason it was implemented only for domain-related commands but not standalone-related (reload and shutdown).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jboss-jira
mailing list