Knowlege base

Process Performance Warning by SvSasService and High CPU usage on CUCM

Article ID: 674
Last updated: 23 Dec, 2021
Applies from Application Suite 201x (any version)
to version Application Suite 201x (any version)


  • CUCM CPU Overload, in particular due to Tomcat process.
  • Monitoring Event (Overlimit Thread)
    Process Performance Warning: SvSasService(ApplicationSuite.Core.Service.exe)


StoneLock is performing lots of HTTP push to every IP Phones and, for some reason, those push are failing.

As every push can last more than 1 second and IAS is performing push to different devices, this cause Imagicle Service Host service to use many threads, even over the default threshold. Hence, the warning. 

Moreover, all IP Phones receiving the push request authorization to CUCM, causing a huge CPU usage by Tomcat process on CUCM.

So, usually, this issue occur when:

  1. >1000 users configured in our Application
  2. AuthenticationURL not properly configured in CUCM
  3. Stonelock in Evaluation but not yet configured

How To Diagnose

In log files \StonevoiceAS\Var\Log\ApplicationSuite.Core.Service\ApplicationSuite.log:

DEBUG {182} [PhoneSendAgent] Pushing request 'CiscoIPPhoneExecute' to device SEP00562BB45040 with IP address
DEBUG {132} [AxlRequester] GetXmlResponse( Response received in 1160 ms (req sent in 0 ms):
<CiscoIPPhoneError Number="4" />
ERROR {132} [PhoneSendAgent] Error while pushing to device SEP00562BB45040 ( in 1179 ms:
System.Security.Authentication.InvalidCredentialException: Error number 4 occurred while sending a request to the phone.
   at ApplicationSuite.Base.Library.Connectors.Axl.SvAxlPhoneRequester.PostRequest(XElement request)

In Notepad++ or BartailPro:

Using this Regex  0326 01.+Error while pushing to device  you can see many errors (Error while pushing to device)

Another symptom:
The high CPU usage of CUCM can be caused by incorrect configuration.

When this occured: Every night at 1.00 a.m after Users Synchronization  Stonelock application has refreshed information about users and has executed one push for every user.


Article ID: 674
Last updated: 23 Dec, 2021
Revision: 4
Views: 718
Print Export to PDF Subscribe Share
This article was:  
Prev   Next
Imagicle ApplicationSuite 2019.Spring.1.H1 known problems     Imagicle ApplicationSuite 2019.Spring.1.H3 setup error message...