Stopping a proxy server

Stopping a proxy server ends a server process based on the process definition settings in the current appserver configuration.

Ensure that you understand how stopping a particular server affects your ability to handle work requests, especially to maintain a highly available environment.

There are times we need to stop a proxy server. For example, you might want to upgrade the operating system, or we might want to change a configuration setting for the proxy server. Use one of the following options to stop a proxy server.

To perform a proxy quiesce for the Session Initiation Protocol (SIP) proxy server, shut down the SIP proxy server by issuing the stopServer command from the command line. If we attempt to shut down the proxy server from the admin console, then the server shuts down immediately and the proxy quiesce is not completed.

 

• We can issue the stopServer command from the command line to stop a single proxy server. You can issue the stopServer command from the PROFILE_HOME\AppSrv02\bin directory.

  #  .\stopServer.sh proxyserver1
  
  

  
  [AIX] We can issue the stopServer command from the /usr/WebSphere/AppServer/bin directory.

  #  ./stopServer.sh proxyserver1
  
  

• Use the admin console to stop a proxy server.

  1. From the admin console ...

     Servers > Server Types > WebSphere proxy servers.

  2. Select the proxy server, and click Stop.

  3. Confirm to stop the selected proxy server.

  4. View the Status value and any messages or logs to see whether the proxy server stops.

 

Results

The specified proxy server stops as soon as requests assigned to that server finish processing. To verify that the proxy server is in the stop state, in the admin console ...

Servers > Server Types > WebSphere proxy servers.

If the stopServer command is issued from the command line, then the server delays shutdown for a period of time until new inbound messages to route are not no longer being received. The quiesce feature notifies the load balancer to discontinue routing inbound messages by sending error responses to the advisor messages.

 

Next steps

If errors occur when you shut down a server, then read about Troubleshooting administration.

By default, the SIP proxy server stops the flow of messages between the load balancer and the back-end containers to prevent calls from being lost when the proxy server shuts down. This process is called a proxy quiesce.

During proxy quiesce, the SIP proxy server notifies the load balancer and the back-end containers that the server is shutting down. After the devices stop forwarding messages through the proxy server, the server shuts down.

The default quiesce timeout period is three minutes. The SIP proxy server also waits a minimum of 20 seconds to allow the quiesce process to complete. The SIP proxy server continues to forward messages to the back-end containers while it responds to advisor messages from the load balancer with an error response. During a quiesce, the SIP proxy server also notifies the back-end containers that the proxy server is no longer a member of the cluster. After the initial 20 seconds, the SIP proxy server shuts down based on the specified amount of time configured for the proxy quiesce, which ranges from one second to a maximum of three minutes. Complete these steps to change the timeout period for proxy quiesce.

1. From the admin console, expand Servers > Server Types > WebSphere proxy servers > proxy_server_name.

2. From Server infrastructure, click Java and Process management > Process definition.

3. Click Java virtual machine.

4. Set the Generic JVM argument to -Dcom.ibm.ejs.sm.server.quiesceTimeout=120.

5. Define these SIP proxy custom properties to set the SIP proxy server to be fronted by a load balancer running a SIP advisor: LBIPADDr and SIPAdvisorMethodName.

 

Related tasks

Starting a proxy server
Create a proxy server

 

Related

SIP container custom properties
SIP proxy server custom properties