Tuning considerations using the JSR 289 Application Router with multiple applications

Leverage tuning considerations to avoid overload and error conditions when using the JSR 289 Application Router with multiple applications.

Note: 這個主題參照一或多個應用程式伺服器日誌檔。 此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.logSystemErr.log, trace.logactivity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。
When you deploy more than one application, you might see the following errors in the log files when heavy SIP protocol traffic exists for a single application server or cluster of servers:
  • Unexpected and excessive SIP application 503 Server Unavailable error messages
  • Proxy and Server overload errors
Note: These error messages do not occur when you deploy one application.
The proxy server and Session Initiation Protocol (SIP) containers are not synchronized when they are tracking the amount of messages that are flowing through the system. Using the application router, multiple messages might be routed between applications. These messages cause container message counters to increment even though the messages do not flow through the proxy server.
You can diagnose this problem when you have the following conditions:
  • Heavy SIP protocol traffic exists.
  • Multiple applications are deployed on a single node or cluster.

Check the proxy server, the application server SystemOut.log log files, or both for an unexpected overload condition that is detected at the proxy server, the application server, or both. Also, look for 503 Server unavailable messages that are logged from the SIP application.

Resolving the problem

Messages are shared between applications at the SIP container before they are sent to the proxy server. To avoid these error messages and a decrease in SIP performance, tune the SIP containers to consider the additional SIP messages that are generated when using the application router with multiple applications. Complete the following steps in the administrative console to tune the SIP containers:
  1. Expand Servers > Server Types and click WebSphere application servers > server_name
  2. Under Container Settings, expand SIP Container Settings and click SIP container.
  3. Increase the Maximum messages per averaging period value to compensate for the anticipated increase in messages that are generated by the SIP application router.
  4. Increase the Maximum application sessions value to compensate for the increased Maximum messages per averaging period value.

The proxy server cannot detect the amount of messages that are generated at the server. However, modifications to the following settings might increase the messaging capacity at the containers for the number of applications that are deployed per container.

Table 1. DAR and CAR SIP container tuning values.

This table lists the DAR and CAR SIP container tuning values for the number of applications that are deployed per container.

SIP Container Single Deployed SIP Application Three Deployed SIP Applications
Maximum messages per averaging period value = 26640 value = 79920
Maximum application sessions value = 36000 value = 96000
Note: The values for the Maximum messages per averaging period and Maximum application sessions fields depend on the processing power, memory, and the deployed application. Use the values for these fields as listed in the SIP container settings topic and adjust them to meet the needs of your environment.

指出主題類型的圖示 概念主題



時間戳記圖示 前次更新: July 9, 2016 11:10
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=ccea_sipapprouter_tuning
檔名:ccea_sipapprouter_tuning.html