What version of UCM are you on? If it’s 11.5 SU3 check informix ccm.log for something like this: 23:13:59 SCHAPI: last statement aus_refresh_stats(integer,integer) 23:13:59 SCHAPI: [Auto Update Statistics Refresh 43-2] Error -217 Column (aus_cmd_dbs_priority) not found in any table in the query (or SLV is undefined).
This is CSCva78144. I ask because I’m pretty sure one of those last two numbers is the time taken to process the request, and neither of those are a good number. -Ryan On Apr 13, 2018, at 2:22 PM, ROZA, Ariel <[email protected]<mailto:[email protected]>> wrote: Hi, guys and gals. I am trying to troubleshoot a High CPU Alarm on a CUCM Subscriber: I ran the “utils diagnose test” command and got warnings on the tomcat_sessions module. gathered all the tomcats logs around the time of the event and found lots of GET /cucm-uds/users HTTP/1.1 200 1383 1611 queries. In the Bug Search tool I found several bugs for old jabber versions regarding this, one enhancement request but no fixes. I was wondering if it is possible to load balance the UDS queries around the cluster using several DNS SRV records for _cisco-uds._tcp<domain> with the same priority /weight to load balance the queries, or if this breaks functionality, somehow. The only examples I found are ones with different weight/priority. Regards, Ariel Roza Collaboration Support Engineer t: +54 11 5282-0458 c: +54 9 11 5017-4417 webex: http://logicalis-la.webex.com/join/ariel.roza Av. Belgrano 955 – Piso 20 – CABA – Argentina – C1092AAJ www.la.logicalis.com<http://www.la.logicalis.com/> _________________________________________________ Business and technology working as one <image001.png> <image002.png> <image004.jpg><image005.png><http://twitter.com/LogicalisLatam> <image006.png><http://es-es.facebook.com/pages/Logicalis-Latam/234648439078> <image007.png><http://www.youtube.com/logicalislatam> Logicalis Argentina S.A. solo puede ser obligado por sus representantes legales conforme los límites establecidos en el acto constitutivo y la legislación en vigor. El contenido del presente correo electrónico e inclusive sus anexos contienen información confidencial. El mismo no puede ser divulgado y/o utilizado por cualquiera otro distinto al destinatario, ni puede ser copiado de cualquier forma. _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
