[jboss-jira] [JBoss JIRA] (WFCORE-533) Add blocking option to reload command for standalone server

Joe Wertz (JIRA) issues at jboss.org
Fri Aug 7 07:00:06 EDT 2015


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

Joe Wertz commented on WFCORE-533:
----------------------------------

>From the CLI one-liner example this seems like a duplicate of an issue reported against EAP and solve recently.

The higher level CLI reload command now does block until the server restarts, so the intermittent connection error after the reload should be gone.

> Add blocking option to reload command for standalone server
> -----------------------------------------------------------
>
>                 Key: WFCORE-533
>                 URL: https://issues.jboss.org/browse/WFCORE-533
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: CLI
>            Reporter: Tomas Rohovsky
>            Assignee: Alexey Loubyansky
>
> 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.15#6346)


More information about the jboss-jira mailing list