November 29, 2004
CallManager - 4.1(2)
Upgrading the Cisco MCS Operating System on a Cisco CallManager 4.1(2) cluster causes the Cisco Tomcat process CPU utilization to increase to 100 percent.
This CPU utilization occurs on the Subscriber(s) server when the Publisher is being upgraded. CPU starvation can prevent other processes from getting CPU time and may result in a service impacting outage.
This issue was introduced when a change was implemented for DDTS CSCin79192. Short term resolution changes for CSCin79192 have been backed out from all affected branches, including the 4.1(2)es branch.
An additional fix, CSCeg30670, which modifies the installation behavior for this identified case of CPU utilization, has also been added to the WinOS 2000.2.6 SR6. The estimated CCO availability is December 20, 2004.
Windows Task Manager indicates Cisco Tomcat process at 100 percent CPU Utilization on Subscriber nodes in the Cisco CallManager 4.1(2) cluster.
The following process will need to be followed until the Cisco MCS OS 2000.2.6 SR 6 is released.
Customers must manually stop the Cisco Tomcat service on all of the Subscriber servers via the Serviceability Web page while upgrading the MCS Operating System on the Publisher server.
To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.
CSCeg30670 (registered customers only)
Tomcat proc uses 100% CPU on sub when upgrading pub to 2000.2.6 SR5
CSCin79192 (registered customers only)
Change in EM service parameters not taken effect sometimes
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
Receive Email Notification For New Field Notices
Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.