TMSPE Java 6 Update 39

[Steve Deslandes]

I have a customer who claims that running TMSPE on his server, the CPU is running 100% all the time and the memory usage is showing 450 Meg. Everything works perfectly well and this is more a concern than anything. Customer so far has tried uninstalling Jave and re-installed it but the same problem occurs. Has anybody ever seen this issue? Thank you

[Justin Ferello]

Steve,

Nothing above JAVA v6 Update 33 is supported in TMS 14.x right now.

Download here:

http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6-419409.html#jre-6u33-oth-JPR

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
e/v: justin.ferello@kbz.com

[Magnus Ohm]

This is most likely because the client have findme enabled in TMS provisioning extension settings. Its a bug. It happens if you set the video address pattern == device address pattern. If you look on the tmspe diagnostics, if you see a gray circle spinning forever this is the reason of the high cpu. Just disable findme in tmspe settings and restart the tmspe service should fox the problem. It could be something else also but this is the most likely issue. Let me know if this was not the case.

We have discussed the same issue in other threads here as well. Search for findme. :) hope it helps.

/Magnus

Sent from Cisco Technical Support iPhone App

[Steve Deslandes]

Hello Magnus. My customer confirmed that disabling FINDME has helped in lowering his CPU to normal. He reports though that now the provisionning doesn't work anymore. He tried creating a new Jabber account and gets a login failed when he tries to use that new account. He simply re-enable the FINDME feature and the new created user started working. They use AD to create their new users. Please advise if you have any ideas. Thanks

[Magnus Ohm]

Hi Steve

Findme should not have an impact on this and the TMS / VCS synch comes with a delay as it is not a live update but the VCS polls the TMS for new information. Does he know for sure that the VCS had performed a polling before he tried to login and it was not just a coincidence that after he enabled findme again the VCS had performed a poll and he would have been able to login anyway?

Is the customer using FindMe? Do they have the FindMe optionkey on the VCS?

This bug occurs only when the Video Address pattern and the Device address pattern is equal. {username}@domain.com -VAP

{username}@domain.com - DAP

If using Findme the DAP (device address pattern) should be: {username}.{device.model}@domain.com and the VAP should not have changed. If this is the case and the client is using findme then they should set it up like this. By disabling findme does not stop the User polling as these services are separate. So I have a hard time beleiving this

/Magnus