12-05-2012 03:39 AM - edited 03-18-2019 12:14 AM
Hi,
A colleague of mine has an issue with high CPU load caused by the java process under the wrapper, he's using the latest version of TMS 13.2.2 with TMSPE, the server is running Server 2008 R2 Enterprise, 4GB RAM, 64bit, the latest java update (9) has been applied but to no avail.
The java process on my TMS system is running at 0.54% avg, the only difference I can see is the amount of RAM, his userbase is tiny (80 users).
Any suggestions on what he could try to diagnose the issue?
Solved! Go to Solution.
12-06-2012 01:53 AM
Hi are you using findme?
Can you check if the video address pattern is the same as the device address pattern?
Also in the tmspe diagnostics can you see if the device import has a "working"
Circle on it like its doing a constant import?
If you are not using findme, disable it on the tmspe settings in tms and restart the tmspe service. Has the cpu stabilized now?
/Magnus
Sent from Cisco Technical Support iPhone App
12-05-2012 03:56 AM
Is you TMS on a public ip or do you have any scans in your internal network?
https://supportforums.cisco.com/message/3481275#3481275
Please remember to rate helpful responses and identify
12-06-2012 01:34 AM
The TMS server is running on an internal IP address. My colleague doesn't now if there are network scans running on the network but I've asked him to investigate.
12-06-2012 01:53 AM
Hi are you using findme?
Can you check if the video address pattern is the same as the device address pattern?
Also in the tmspe diagnostics can you see if the device import has a "working"
Circle on it like its doing a constant import?
If you are not using findme, disable it on the tmspe settings in tms and restart the tmspe service. Has the cpu stabilized now?
/Magnus
Sent from Cisco Technical Support iPhone App
12-06-2012 04:45 AM
Hi Darren!
Btw, the scan problem should go away after a reboot (at least if there is no immidiate new scan :-)
The issue Magnus mentioned sounds quite resitant and might survive a reboot.
In short, did you reboot the TMS and what was the result?
Btw, for TMSPE and x64 I would suggest some more ram, if I recall it right the 4GB is the minimum.
I do not like to operate on minimum requirements :-)
Martin
Darren: Please rate the postings using the stars below and set the thread to answered if it is!
Please remember to rate helpful responses and identify
12-06-2012 07:01 AM
Thanks for your input guys, disabling FindMe on TMS resolved the issue.
12-06-2012 06:46 PM
Hi Darren,
Current TMSPE 1.0 Deployment Guide states:
Java Version 6 (32-bit), update 33 recommended. Updates 4-33 supported
And yes, official support for Java 7 will be coming in the next TMSPE release, so if you can installe Java 6 Findme also should work fine.
BR,
Mahesh Adithiyha
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: