Set maintenance mode
Use maintenance mode to perform diagnostic tests, maintenance, or tuning on a node or server without disrupting incoming traffic to that node or server in a production environment.
Before you begin
You can set maintenance mode on a server or a node that is represented in the administrative console.To view the nodes that are configured, click...
System administration | Middleware nodesTo view all of the servers that are configured, click...
Servers | All serversYou can use maintenance mode when you route requests with ODR or proxy servers. If you are using a Web server to route requests, then maintenance mode is not recognized.
About this task
When a node or server is in running state, the dynamic operations environment considers that node or server to be available for servicing application requests. When problems occur, perform diagnostics, maintenance, or tuning on the node or server. Use maintenance mode to stop routing traffic to the node or server while you determine the problem.
When a server is in maintenance mode, the application placement controller cannot control that server. The server does not count toward the minimum or maximum running instances setting for the dynamic cluster.
For vertical stacking, the configured maximum minus the number of servers in maintenance mode on the node is used to determine if any servers need to be created on the node. By using this method, the dynamic operations environment does not create or destroy server instances to support the configured maximum number of instances as the dynamic cluster instances move in and out of maintenance mode.
Two routing policies, permitMM and permitstickyMM, are work class match actions which can be used to only route HTTP traffic to servers in maintenance mode.
Place nodes into or out of maintenance mode
- Select the nodes. In the administrative console, click...
System administration | Middleware nodes
Select the nodes for which you want to change the maintenance mode.
| Maintenance mode | Serves the remaining requests on the node. Any requests that have an open session on the node are still routed to the node until the session ends or times out. After all requests are completed, the node is moved into maintenance mode. Any new requests are routed to nodes that are not in maintenance mode. |
| Maintenance immediate stop | Stops all of the processes on the node and immediately moves the node and all the servers running on the node to maintenance mode, without serving the remaining requests on the node. The node and all the servers on the node are in maintenance mode after the node and servers stop. The nodes and servers continue to be in maintenance mode when you restart the node and servers on the node. |
| Normal | Moves the node out of maintenance mode, and the node begins to serve requests from the on demand router. |
In the administrative console, click...
Servers | All servers
Select the servers for which you want to change the maintenance mode.
| Maintenance mode | Serves the remaining requests on the server. Any requests that have an open session on the server are routed to the server until the session ends or times out. After all requests are completed, the server is moved to maintenance mode. Any new requests are routed to servers that are not in maintenance mode. |
| Maintenance mode - break affinity | Moves the selected servers into maintenance mode, and breaks HTTP and SIP request affinity to the servers. |
| Maintenance mode - immediate stop | Stops the server process and immediately moves the server to maintenance mode, without serving the remaining requests on the server. The server is in maintenance mode after the server stops. The server continues to be in maintenance mode when you restart the server. |
| Normal | Moves the server out of maintenance mode, and begins serving requests to the server. |
HTTP and SIP traffic is no longer routed to the nodes or servers that you have in maintenance mode. EJB affinity is not broken. Requests with EJB affinity and JMS traffic are still routed to the server that is in maintenance mode.
The health controller also uses server maintenance mode as an action that is taken when the health policy is breached. For example, if you are using an excessive response time condition, and the response time exceeds the specified maximum for a server, then the server can move to maintenance mode.