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.
[AIX Solaris HP-UX Linux Windows][IBM i]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.
Avoid trouble Avoid trouble: The quiesce function for the SIP proxy server is not supported on the z/OS platform. To use a similar function on z/OS, see the information center article, Pausing an application server listener to manually update a high availability application.gotcha

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 > Server Types > WebSphere proxy servers.
Note: 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.

What to do next

[AIX Solaris HP-UX Linux Windows][IBM i]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.

[AIX Solaris HP-UX Linux Windows][IBM i] 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.

[AIX Solaris HP-UX Linux Windows][IBM i]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.

[AIX Solaris HP-UX Linux Windows][IBM i]Complete these steps if you want to change the timeout period for proxy quiesce.
  1. From the administrative console, expand Servers > Server Types > WebSphere proxy servers > proxy_server_name.
  2. From Server infrastructure, click Java and Process management > Process definition.
  3. [z/OS]Select Control.
  4. Click Java virtual machine.
  5. Set the Generic JVM argument to -Dcom.ibm.ejs.sm.server.quiesceTimeout=120.
  6. 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.

Icon that indicates the type of topic Task topic



Timestamp icon Last updated: March 5, 2017 17:28
File name: tjpx_sipcfgpxquiesce.html