Cisco Tomcat High CPU Utilization 99 percent
So a client was experience slow web interface usage to their calling node. As well RTMT was shooting off the alert. The alert is for Call Process CPU Node Pegging. The culprit tomcat!
Cisco Tomcat Service - In enterprise edition this is a web server service. In the business edition (BE Servers) this uses the web server and unity utilizes the service as well.
Log in to each call manager node and issue the following command:
show process load cpu
**OUTPUT**
top - 08:55:48 up 340 days, 4:03, 1 user, load average: 4.64, 3.25, 2.98
Tasks: 142 total, 2 running, 140 sleeping, 0 stopped, 0 zombie
Cpu(s): 16.3%us, 3.4%sy, 0.0%ni, 80.1%id, 0.1%wa, 0.0%hi, 0.2%si, 0.0%st
Mem: 4016964k total, 3856400k used, 160564k free, 29904k buffers
Swap: 2064280k total, 1664k used, 2062616k free, 598124k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8065 tomcat 25 0 2317m 1.9g 22m S 99.4 50.4 358084:37 tomcat
1 root 15 0 2172 684 584 S 0.0 0.0 9:12.24 init.real
2 root RT -5 0 0 0 S 0.0 0.0 0:00.00 migration/0
3 root 34 19 0 0 0 R 0.0 0.0 0:38.20 ksoftirqd/0
4 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
5 root 10 -5 0 0 0 S 0.0 0.0 0:00.01 events/0
6 root 13 -5 0 0 0 S 0.0 0.0 0:00.00 khelper
7 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kthread
10 root 10 -5 0 0 0 S 0.0 0.0 0:08.83 kblockd/0
11 root 20 -5 0 0 0 S 0.0 0.0 0:00.00 kacpid
From the above output it shows that top running cpu hog is tomcat at 99.4 percent.
What does this affect?
This can degrade a number of items that include access to the web gui ( main administration of CUCM), call processing, and end user serviceability.
Also if you log into RTMT you should be able to see this alert being pegged and the CPU threshold being throttled as well
like the following image:
Workaround / Quick Fix
A nice workaround and quick fix to this is to log back into the CLI of the actual node(s) being affected.
Issue the following command to restart Tomcat.
utils service restart Cisco Tomcat
This will restart the tomcat service by first stopping it and then starting it again.
After all said and done the CPU utilization should drop. We can recheck the graph like that above or we can go to the process tab to get the actual number data to see tomcat service usage.
Cisco Tomcat Service - In enterprise edition this is a web server service. In the business edition (BE Servers) this uses the web server and unity utilizes the service as well.
Log in to each call manager node and issue the following command:
show process load cpu
**OUTPUT**
top - 08:55:48 up 340 days, 4:03, 1 user, load average: 4.64, 3.25, 2.98
Tasks: 142 total, 2 running, 140 sleeping, 0 stopped, 0 zombie
Cpu(s): 16.3%us, 3.4%sy, 0.0%ni, 80.1%id, 0.1%wa, 0.0%hi, 0.2%si, 0.0%st
Mem: 4016964k total, 3856400k used, 160564k free, 29904k buffers
Swap: 2064280k total, 1664k used, 2062616k free, 598124k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8065 tomcat 25 0 2317m 1.9g 22m S 99.4 50.4 358084:37 tomcat
1 root 15 0 2172 684 584 S 0.0 0.0 9:12.24 init.real
2 root RT -5 0 0 0 S 0.0 0.0 0:00.00 migration/0
3 root 34 19 0 0 0 R 0.0 0.0 0:38.20 ksoftirqd/0
4 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
5 root 10 -5 0 0 0 S 0.0 0.0 0:00.01 events/0
6 root 13 -5 0 0 0 S 0.0 0.0 0:00.00 khelper
7 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kthread
10 root 10 -5 0 0 0 S 0.0 0.0 0:08.83 kblockd/0
11 root 20 -5 0 0 0 S 0.0 0.0 0:00.00 kacpid
From the above output it shows that top running cpu hog is tomcat at 99.4 percent.
What does this affect?
This can degrade a number of items that include access to the web gui ( main administration of CUCM), call processing, and end user serviceability.
Also if you log into RTMT you should be able to see this alert being pegged and the CPU threshold being throttled as well
Workaround / Quick Fix
A nice workaround and quick fix to this is to log back into the CLI of the actual node(s) being affected.
Issue the following command to restart Tomcat.
utils service restart Cisco Tomcat
This will restart the tomcat service by first stopping it and then starting it again.
After all said and done the CPU utilization should drop. We can recheck the graph like that above or we can go to the process tab to get the actual number data to see tomcat service usage.
Comments
Post a Comment