[jboss-jira] [JBoss JIRA] (WFCORE-533) Handling of ModelControllerClient means there is no safe way to reload a process from the wildfly maven plugin
Jean-Francois Denise (JIRA)
issues at jboss.org
Wed Jan 11 08:09:00 EST 2017
[ https://issues.jboss.org/browse/WFCORE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13346159#comment-13346159 ]
Jean-Francois Denise commented on WFCORE-533:
---------------------------------------------
The problem is still there but this time the third party (maven plugin) as the chance to implement its waiting logic thanks to the CLI AwaiterModelControllerClient interface that a ModelControllerClient can implement.
> Handling of ModelControllerClient means there is no safe way to reload a process from the wildfly maven plugin
> --------------------------------------------------------------------------------------------------------------
>
> 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
(v7.2.3#72005)
More information about the jboss-jira
mailing list