Restarting a JCS-SaaS Extension Instance

Use the Restart Service option to restart all managed servers in service’s domain.

One example of when you might need to restart an instance might be when adding an SSL certificate to the ssl trust-store requires a service restart for the changes to take effect. See Managing SSL Truststores.

When you restart a service, all servers in the service instance will be stopped and restarted. If the service instance only has a single server, this could result in downtime. If it has multiple servers, these servers will be restarted sequentially. Other operations are not permitted during a service instance restart.

To restart a JCS-SaaS Extension instance:

1. Navigate to the Home page.

2. Click Restart Service Instance.

   The Restart service instance dialog appears.

   
   Description of the illustration restart_dialog.png

3. Click OK when you are ready to restart your service instance.

4. Go to the Job Logs page to verify that you successfully restarted the job. When the service restart begins, there will be a Restart Service Instance log entry in the Jobs log page and it will show a Status of Running. When the restart is complete, the Status column for the restart will indicate Completed.

5. To see the content of the log, locate it on the job list and click View Details.

6. You can either save the log to disk or view it immediately in your browser.

   • To download it to your file system, click Download.

   • To view it in your browser, click View Log (in the Log column of the dialog)

   This is a sample log for restarting single managed-server service:

   2014-07-08 15:15:07 PDT: Starting action "Restart Service"
   2014-07-08 15:15:07 PDT: Restart Service started
   2014-07-08 15:15:07 PDT: Restarting service: server restart timeout = 600000 ms ...
   2014-07-08 15:15:07 PDT: 
   Stopping server m0 : current state = RUNNING ...
   2014-07-08 15:15:09 PDT: Server m0 stopped
   2014-07-08 15:15:09 PDT: 
   Starting server m0 : current state = SHUTDOWN ...
   2014-07-08 15:16:16 PDT: Server m0 started
   2014-07-08 15:16:16 PDT: "Restart Service" complete: status SUCCESS
   Server m0 started

Restarting a Single Managed Server Service

For single managed-server services, there may be some service downtime until the managed-server is restarted. Therefore, options like Application Deploy, Start, and Stop on the JCS - SaaS Extension Administration Console are disabled while a service restart is in progress.

Restarting a Multiple Managed Server Service

For multiple managed-server services, there should not be any service downtime because the managed servers are restarted sequentially, as follows:

• Restarts one server at a time.

• Waits for each server to boot up before executing restart on the next server.

• Restarts in sequence of m0, m1, m2, m3, etc.

• Time-outs after waiting for three minutes for a server to restart, and then triggers a restart on the next server.