RebootServer

Signals the webserver to perform a complete software reboot after the current script has finished and the response has been transmitted.

The reboot clears all active sessions, all server-side cookies, all database connections held by sessions, all runtime forms and the entire request queue, without terminating the webserver process itself. Connected clients holding old session cookies will be issued a fresh session on their next request.

The optional parameter restartListener controls whether the TCP/SSL listener is automatically restarted after the cleanup:
• True (default) – cleanup followed by an immediate restart of the listener; the webserver resumes accepting requests as soon as initialisation completes.
• False – cleanup without restart; the webserver remains stopped until manually started from the console or via an external trigger.

 

Note: this command affects all active sessions of all connected clients, not just the session that issued the call. It is intended as a recovery mechanism for situations in which the server has entered an unrecoverable state (typically following an unresolved database disconnect), and as a programmatic alternative to terminating and relaunching the CBBSWEB32 process. The actual reboot is scheduled to run on a separate timer tick, so the response to the current request is guaranteed to reach the client before any cleanup takes place. The calling script does not block and returns immediately.

 

CloseSession, Cookie, ParentSession, ParentResponse.