Reload: Difference between revisions
No edit summary |
|||
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
The <tt>:reload</tt> management model operation is available on the root of the management model. Reloads the server by shutting down all its services and starting again. The JVM itself is not restarted. | |||
In domain mode, it can | In domain mode, it can reload the configuration on a per-host basis and then restart the servers. | ||
The CLI <tt>reload</tt> command sends the <tt>:reload</tt> operation request to the server/domain controller and waits for the controller to close the connection. Then it returns the control back to the client. It does not put the CLI client into the disconnected state. Instead, for the next entered command or operation it will try to automatically re-connect to the controller. | |||
=Standalone= | =Standalone= | ||
Management model command: | |||
<pre> | <pre> | ||
cd / | cd / | ||
:reload | :reload | ||
</pre> | |||
CLI wrapper: | |||
<pre> | |||
reload [--admin-only=true|false] [--use-current-server-config=true|false] | |||
</pre> | </pre> | ||
| Line 30: | Line 40: | ||
</pre> | </pre> | ||
Domain mode syntax: | |||
<pre> | |||
reload --host=host_name [--admin-only=true|false] | reload --host=host_name [--admin-only=true|false] | ||
[--restart-servers=true|false] | [--restart-servers=true|false] | ||
[--user-current-domain-config=true|false] | [--user-current-domain-config=true|false] | ||
[--user-current-host-config=true|false] | [--user-current-host-config=true|false] | ||
</pre> | |||
=Behavior on Error= | |||
If there was an i/o error while sending the request or receiving he response, the reload handler will disconnect from the controller. | |||
If the reload operation failed, i.e. the response received successfully indicated a failure, the handler will log the failure message and will not disconnect from the controller. | |||
=Batch= | |||
This command cannot be used in a batch because the handler is waiting for the controller to shutdown before returning the control back to the client which would not possible if the command was executed as a step in a composite operation. So, if there is a need to reload the controller from a batch, <tt>:reload</tt> operation must be used instead (and should be the last operation in the batch). | |||
=Command Arguments= | |||
==<tt>--admin-only</tt>== | |||
==<tt>--host</tt>== | |||
==<tt>--restart-servers</tt>== | |||
==<tt>--use-current-domain-config</tt>== | |||
==<tt>--use-current-host-config</tt>== | |||
==<tt>--use-current-server-config</tt>== | |||
Latest revision as of 19:18, 27 May 2016
Internal
Overview
The :reload management model operation is available on the root of the management model. Reloads the server by shutting down all its services and starting again. The JVM itself is not restarted.
In domain mode, it can reload the configuration on a per-host basis and then restart the servers.
The CLI reload command sends the :reload operation request to the server/domain controller and waits for the controller to close the connection. Then it returns the control back to the client. It does not put the CLI client into the disconnected state. Instead, for the next entered command or operation it will try to automatically re-connect to the controller.
Standalone
Management model command:
cd / :reload
CLI wrapper:
reload [--admin-only=true|false] [--use-current-server-config=true|false]
Domain Mode
To reload the domain controller configuration, execute on the domain controller:
reload --host=dc1
To reload a subordinate host controller and associated servers:
reload --host=h1 --restart-servers=true
Domain mode syntax:
reload --host=host_name [--admin-only=true|false]
[--restart-servers=true|false]
[--user-current-domain-config=true|false]
[--user-current-host-config=true|false]
Behavior on Error
If there was an i/o error while sending the request or receiving he response, the reload handler will disconnect from the controller.
If the reload operation failed, i.e. the response received successfully indicated a failure, the handler will log the failure message and will not disconnect from the controller.
Batch
This command cannot be used in a batch because the handler is waiting for the controller to shutdown before returning the control back to the client which would not possible if the command was executed as a step in a composite operation. So, if there is a need to reload the controller from a batch, :reload operation must be used instead (and should be the last operation in the batch).