hotRestarthotRestart
Initiates a Hot Restart
Home > Books > NetKernel API and Services Reference > Accessor Listing > Kernel Management and Development APIs > hotRestart

Rate this page:
Really useful
Satisfactory
Not helpful
Confusing
Incorrect
Unsure
Extra comments:


Module

urn:org:ten60:netkernel:ext:kernel

The hotRestart accessor is exported by the urn:org:ten60:netkernel:ext:kernel module. Import this module to gain access to the accessor.

Syntax

URI
active:hotRestart

Example Usage

DPML

<instr>
  <type>hotRestart</type>
</instr>

NetKernel Foundation API

req=context.createSubRequest("active:hotRestart");
result=context.issueSubRequest(req);

Purpose

Initiates a hotRestart. The purpose of hot restart is to allow the configuration of a deployed server to be changed without any interruption of service. Transports that are not taken out of the configuration remain active so no external requests will be lost. Upon restart changes to kernel configuration will be detected including linking in any new or upgraded modules or decommissioning removed modules and stopping their transports.

Specifically hot Restart is not a development aid. It will not detect changes in modules, in fact to allow transports to continue uninterrupted, classloaders cannot change. Only modules with changed versions will be decommissioned/commisioned.

Alternatively, active:coldRestart will perform a complete cold restart of the system including a full reconfiguration of all modules and restart of all transports.

© 2003-2007, 1060 Research Limited. 1060 registered trademark, NetKernel trademark of 1060 Research Limited.