11-06-2011 03:53 PM - edited 03-17-2019 10:35 PM
We have a customer that has recently upgraded their TMS to 13.1.1 and have since noticed that the TMS server locks at 100% CPU.
The Culprit is java.exe and this has happed several times now. Java on TMS is version 6 update 17.
This is not at server reboot.It does not appear to effect any other utilities on TMS , but obviously the server is not very manageable.
2 Questions .
Can they end task java.exe without affecting TMS ? They have Movi running and I understand the TMS Agent is Java based.
Is this a known issue ?
Thanks.
Thanks for your input folks.
I am at present trying to obtain log files and screen captures to look at as TB suspect there may be some corrupt files during the upgrade to TMS 13.1 happened.
There may be an issue with the TMS AGENT and openDS.
Will update as I get more info.
Thanks
FYI *****************************************
We
TB had a Webex session and noticed the OpenDS service start in Windows was set to automatic which should be manual.
they have changed the parameters of OpenDS and saw the Java process utilization came down.
OpenDS service set to manual after TMS installation is by design as TMS agent service has to trigger the OpenDS service when provisioning is configured on TMS.
OpenDS service should not be set to automatic.
I guess the new release coming out shortly will reslove this . !!!
Thanks
Rob
11-07-2011 07:25 PM
Hi Rob,
please check if the TMS still open graphic monitoring page, because it is consume much java resources
Regards,
Acer
11-08-2011 02:17 PM
Did you see:
https://supportforums.cisco.com/message/3481275#3481275
maybe thats related.
Is your TMS on a public or internal network?
In general I would guess it shold work to kill the java process. But in doubt or you
see any strange behavoir I would reboot the TMS (or at least restart the services).
mek
Please remember to rate helpful responses and identify
04-01-2012 08:21 PM
FYI *****************************************
We
TB had a Webex session and noticed the OpenDS service start in Windows was set to automatic which should be manual.
they #have changed the parameters of OpenDS and saw the Java process utilization came down.
OpenDS service set to manual after TMS installation is by design as TMS agent service has to trigger the OpenDS service when provisioning is configured on TMS.
OpenDS service should not be set to automatic.
I guess the new release coming out shortly will reslove this . !!!
Thanks
Rob
04-17-2012 09:28 AM
Hi Rob,
I am also problems with high CPU utilization.
Can you explain me how do I know if my OpenDS is set to Manual or Automatic?
If it is Automatic, which procedure to switch to Manual on Windows Server 2008?
My TMS version is 13.1.2.
Thank you!
Franklin
04-17-2012 03:23 PM
Hi Franklin
The OpenDS service start in Windows should be set to manual.
Sorry not sure on Windows Server 2008 , but on windows 2003
Go to Computer management / Services and then to openDS – right click properties and change to manual.
04-18-2012 06:30 AM
Hi Rob,
Thank you.
I'll take the test to see if solves my problem of high cpu usage!
This procedure may cause some problem?
Franklin
04-19-2012 02:36 PM
Hi again Rob.
I tested the service of OpenDS.
The OpenDS was to Manual, but it was initialized.
I decided to stop the service.
The processing dropped dramatically!
My question is:
The OpenDS service must be initialized?
What is the process that starts the OpenDS?
Sorry the questions, but I think important to understand how the OpenDS. And so he serves on the TMS.
Could you provide me the contact of the TAC engineer to solve your problem? Or the number of TAC?
I have a TAC open, but I think they can help you solve my problem!
Again thank you!
Franklin
04-19-2012 02:43 PM
Hi Franklin
Ask TAC to contact their Engineer Sanjit Roy sanjitr@cisco.com
He is really good and knows of the 100% cpu issues.
Cheers
Rob
04-19-2012 02:48 PM
Thank you Rob.
I'll talk to the TAC engineer!
You helped me a lot!
hugs
Franklin
04-19-2012 02:45 PM
FYI and Reference my previous TAC case number was SR 619685907
Hope this helps
Rob
04-23-2012 12:25 AM
Hi all,
If i upgrade TMS from 12.6 to 13.1.2, then upgrade was succeded but, the logo Tandberg didn't change to Cisco, maybe this ih not major problem, but anyone know why ?
Thanks so much
04-23-2012 12:59 AM
Are you sure you have upgraded to version 13.1 ?
Regards
Rob
Sent from my iPad2
04-23-2012 01:06 AM
04-23-2012 01:12 AM
Looks ok to me. I will check against our one in the morning.
Is everything working ok? Any alarms showing
Regards
Rob
Sent from my iPad2
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide