Stopping a proxy server

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

Before you begin

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

About this task

There are times you need to stop a proxy server. For example, you might want to upgrade the operating system, or you might want to change a configuration setting for the proxy server. You can use one of the following options to stop a proxy server.
[Fix Pack 9 or later] Note: To perform a proxy quiesce for your Session Initiation Protocol (SIP) proxy server, you must shut down the SIP proxy server by issuing the stopServer command from the command line. If you attempt to shut down the proxy server from the administrative console, then the server shuts down immediately and the proxy quiesce is not completed.

Procedure

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 administrative console, click Servers > Proxy servers.

What to do next

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

[Fix Pack 9 or later] 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.

[Fix Pack 9 or later] 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.

[Fix Pack 9 or later] 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.

[Fix Pack 9 or later] Complete these steps if you want to change the timeout period for proxy quiesce.
  1. From the administrative console, expand Servers, and select Proxy Servers > serverName .
  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.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 10:47:11 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-iseries&topic=tjpx_sipcfgpxquiesce
File name: tjpx_sipcfgpxquiesce.html