[jboss-jira] [JBoss JIRA] (WFCORE-1427) Add a timeout param to reload op and use it for "graceful reload"
[
https://issues.jboss.org/browse/WFCORE-1427?page=com.atlassian.jira.plugi...
]
Yeray Santana Borges commented on WFCORE-1427:
----------------------------------------------
[~brian.stansberry] Just a note, reload command when it is used via CLI has a default
connection timeout awaiting for the servers in "starting" status:
org.jboss.as.cli.handlers.ReloadHandler L273, using the reload CLI together with a
--timeout would require a different connection timeout instead of the default
configuration.
I haven't changed it yet, maybe get the default configured connection timeout plus the
--timeout used via CLI and use it instead in L273?, maybe check if the servers are in
suspend and just wait before use the default connection timeout?
Add a timeout param to reload op and use it for "graceful
reload"
-----------------------------------------------------------------
Key: WFCORE-1427
URL: https://issues.jboss.org/browse/WFCORE-1427
Project: WildFly Core
Issue Type: Enhancement
Components: CLI, Domain Management
Reporter: Brian Stansberry
Assignee: Yeray Santana Borges
So instead of
{code}
:suspend(20)
:reload
{code}
It's just
{code}
:reload(20)
{code}
The high level 'reload' command in the CLI should take a --timeout param as
well.
If doing the graceful suspend as part of server side ":reload" handling proves
problematic (I haven't looked into it at all before filing this) then a simpler
alternative is to only go with the --timeout param on the CLI reload command, and have the
CLI implement the graceful behavior internally by first calling :suspend and then :reload.
Web console could do the same thing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)