Stop, Start, and Restart an Oracle Java Cloud Service Instance and Individual Nodes

You can stop and start an Oracle Java Cloud Service instance and, when the service instance is running, start, stop, and restart individual server or load balancer nodes.

Topics

About Stopping, Starting, and Restarting an Oracle Java Cloud Service Instance and Individual Nodes

You can stop and start an Oracle Java Cloud Service instance and, when the service instance is running, stop, start, and restart individual server or load balancer nodes.

Note:

The stop and restart procedures affect entire nodes. If you want to shut down the WebLogic Administration Server or Managed Server processes running on the nodes, without stopping the nodes, see Shut Down and Start Server Processes. You might want to do this if you have other processes besides the servers running on the nodes and you do not want to shut down these other processes.

Why Stop an Oracle Java Cloud Service Instance

Stopping an Oracle Java Cloud Service instance frees up compute resources used by the service instance’s nodes. Metering for those resources stops.

Storage volumes remain intact when the service instance is stopped, and are reattached when your start the service instance. IP address reservations are retained when the service instance is stopped, so the nodes will have the same public IP addresses as before when you start the service instance. Even the public IP addresses that are reserved by the service and assigned automatically to the nodes (during instance creation or when scaling out the instance) are retained.

Why Stop, Start, or Restart an Administration Server, Managed Server, or Load Balancer node

If an Oracle Java Cloud Service instance is running:

You can restart the nodes on which the Administration Server, Managed Server, or load balancer are running if you are experiencing problems with the server that would warrant a reboot. The restart operation is the same as stopping the server or load balancer node, then starting it immediately.
You can stop the nodes on which the Managed Server or the load balancer are running to free up resources and stop metering those resources. You might also want to stop the service instance instead of scaling, keeping the server or load balancer ready for a later time. If you stop all Managed Servers nodes except for one, you might want to stop the load balancer node because it is not needed.
You can start a Managed Server or load balancer node if it is stopped and you want to use it again. Metering begins again.

Note:

You can restart the Administration Server, and stop, start, and restart individual Managed Servers and the load balancer only if you specified Oracle Oracle WebLogic Server 12c (12.2.1) when you provisioned the service instance. This feature is not supported if you specified Oracle WebLogic Server 11g.

What Happens When an Oracle Java Cloud Service Instance is Stopped or Started

Stopping and starting an Oracle Java Cloud Service instance has the following results:

Stopping the service instance: The nodes on which the Administration Server, Managed Servers, load balancer, and Coherence Data Tier are running are stopped. You cannot start, stop, or restart the Administration Server, Manager Server, or load balancer nodes individually while the service instance is stopped.
Starting the service instance: All nodes on which the Administration Server, Managed Server, load balancer, and Coherence Data Tier are running are started. You can restart the Administration Server, and stop, start, or restart the Managed Servers and load balancer nodes individually. You cannot do the same for Coherence Data Tier nodes individually.

What Happens to IP addresses when an Instance or Node is Stopped and Started

Instances and nodes are assigned both a public and private IP address when the service instance is created. When an instance or node is stopped and started, IP addresses are released or retained depending on whether the service instance is based on Oracle Cloud Infrastructure or Oracle Cloud Infrastructure Classic.

Oracle Cloud Infrastructure

For both public and private IP addresses, the IP address persists when an instance or node stops. When the instance or node starts, the same public and private IP address is assigned.
Oracle Cloud Infrastructure Classic

If you create an instance or add a node to an instance on Oracle Cloud Infrastructure Classic, you can reserve public IP addresses instead of having Oracle Java Cloud Service assign them for you.

The public IP address persists when the instance or node stops. When the instance or node starts, and the same public IP address is assigned.

The private IP address is released when the instance or node stops. When the instance or node starts, the same address may or may not be assigned to the instance or node.

If a different private IP address has been assigned to the instance or node when it starts, and you have set up access rules on the private IP address, the access rules no longer apply.

For a service instance that is attached to an IP network, you can set a static private IP address or remove the static IP configuration when you restart a node or start a node that was stopped. This feature ensures that a node continues to use the same private IP address after it's restarted. This feature is supported by the REST API only. See Stop and Start a Service Instance and Individual VMs in REST API for Oracle Java Cloud Service.

What Happens to the Coherence Data Grid When a Service Instance is Stopped or Started

All nodes in a Coherence data grid cluster, including the data grid servers, are stopped when an Oracle Java Cloud Service is stopped, and started if an Oracle Java Cloud Service instance is started.

Note:

When the service instance is stopped, all data in the Coherence cache is lost.

Stopping, starting, and restarting Coherence data grid Managed Server nodes is not supported. The only way you can stop or start the data tier is to stop or start the Oracle Java Cloud Service instance.

How Do I Monitor the Stop, Start, or Restart Operation

You can monitor progress of a stop, start, or restart operation on the Activity page. See Monitor Activity.

You can also monitor the boot progress of individual nodes by using Oracle Cloud Infrastructure Compute Classic. See Viewing the Boot Log of an Instance in Using Oracle Cloud Infrastructure Compute Classic. Ignore information in this topic about the Compute API.

Note:

When you restart an Oracle Java Cloud Service instance, WebLogic Server may not restart.

To check the restart status, on the Activity page, for the Operation Status, click the Expand button and view the details. The operation status shows Succeeded, but in the details section, a warning message is displayed that indicates the admin server startup process has failed.

This occurs because the JCS restart operation considers the output of the VM restart status and not the restart status of the WebLogic Server.

What Happens When a Service Instance Is Stuck in Maintenance Mode While Stopping

When you try to stop an Oracle Java Cloud Service instance, on rare occasions it might become stuck in maintenance mode due to some problem with the service instance.

For six hours, the software will continue to attempt to stop the service instance, then change the instance status from maintenance state to error state. At this point, you can debug the problem causing the error and attempt to stop the service instance again.

Stop or Start an Instance

You can stop, start, or restart an Oracle Java Cloud Service instance (and all of its nodes) with a single operation.

When you stop a service instance, the following changes occur:

Users and other systems cannot access the service instance.
You cannot perform any other maintenance operations on the service instance, except to start it or to delete it.
Scheduled backups of the service instance do not occur.
Metering of Oracle Compute Unit (OCPU) and memory resources for the service instance stops.
Other resources and services associated with the service instance, including block storage, object storage, and IP reservations, continue to be metered.

Wait for any maintenance operations on this service instance to complete, such as backup, restoration or scaling operations, before you stop or restart a service instance.

Access your service console.
Click the name of the service instance that you want to stop or start.
On the Overview page, click Stop Instance , Start Instance , or Restart Instance .
When prompted for confirmation, click OK.
Periodically click Refresh until the operation is completed.

You can also monitor the progress of the operation from the Activity page.

Stop or Start a Node

As part of configuring or troubleshooting an Oracle Java Cloud Service instance, you can stop or start individual nodes.

You cannot stop certain Java Cloud Service nodes. For these nodes, you are limited to the following actions:

Restart the node, to stop the node and then immediately start it again.
Stop the service instance.

Oracle does not recommend that you perform any other management operations on the service instance during a start or stop operation.

(Not available on Oracle Cloud at Customer) For a service instance that is attached to an IP network, you can use the REST API to set a static private IP address or remove the static IP configuration when you restart a node or start a node that was stopped.

Access your service console.
Click the name of the service instance that contains the node that you want to start or stop.
Under Resources, beside the node you want to start or stop, click Manage this node , and then select Stop, Start, or Restart.
When prompted for confirmation, click OK.
Periodically click Refresh until the operation is completed.

You can also monitor the progress of the operation from the Activity page.