QueueMetrics forum

QueueMetrics => Running QueueMetrics => Topic started by: mrothrock on December 17, 2014, 21:19:05

Title: Recent slowness when pulling up call details
Post by: mrothrock on December 17, 2014, 21:19:05

I noticed that in the last month when clicking on the magnify glass on any call to get call details it is now taking about 5 seconds on average for this window to load, in the past it was maybe 1 second max, not sure what could have happened lately to cause this slowness.  We have about 11 months worth of usage with Queuemetrics.  Queuemetrics service has been restarted in the last couple days, so I know it isn't related to that.  Any ideas?

Thanks,

Mike

Title: Re: Recent slowness when pulling up call details
Post by: mirkox on December 18, 2014, 16:35:25

Hi Mike,

that's weird, even 1 second is too much in my opinion (if QM is on the same network).

Did you already give the Java process that runs QueueMetrics more memory? (You'll find a JAVA_OPTS variable in /etc/init.d/qm-tomcat6; change that to, maybe 512M 512M   and restart queuemetrics with '/etc/init.d/queuemetrics restart').

Kind Regards
Mirko

Title: Re: Recent slowness when pulling up call details
Post by: mrothrock on December 19, 2014, 19:39:11

Hi Mirko,

Gave it a look, we have this:

export JAVA_OPTS="-Xms4096M -Xmx4096M -server -XX:+UseParallelGC -XX:PermSize=512M -XX:MaxPermSize=512M"

Asterisk + QMetrics are all on the same box, it doesn't matter if I pull up call details at 2AM with the server doing nothing (zero load/cpu), or during normal hours, it is always taking 4-5 seconds.  I have plenty of free RAM available.

Title: Re: Recent slowness when pulling up call details
Post by: mrothrock on December 19, 2014, 19:47:14

I did notice in the subfolder tomcat/logs/ I have a catalina.out file that just keeps to keep growing forever, it is currently over 13GB in size, could this be doing something?

Also what is this file, is there anyway I can just turn it off?

Title: Re: Recent slowness when pulling up call details
Post by: mirkox on January 05, 2015, 11:06:16

Hi Mike,

sorry for the late reply, actually is not normal the that file increases in that way, dod you see any recurring error in it?

Mirko

Title: Re: Recent slowness when pulling up call details
Post by: mrothrock on January 15, 2015, 23:33:58

Hi again,

Here is a snippet of what the log is full of:

SEVERE: [433F3C5ADB14C1AD076B8974D421A1C0] All sent. Content length: 1245164 bytes
Jan 15, 2015 2:09:06 PM it.loway.tpf.transaction.servlets.LowayTransactionController myLogErr
SEVERE: [CF6436EFB3444E95AFFE6CAD36BCD6A4] User not found: 'agent2029'
Jan 15, 2015 2:16:19 PM it.loway.tpf.transaction.servlets.LowayBinaryStreamer myLog
SEVERE: [F29D1ED01C4375A80D5E1C3311BC48CB] Sending file: '/var/spool/asterisk/monitor/2015/01/15/q-8006-7573554421-20150115-115436-1421351660.2431287.wav' - Under the name: 'q-8006-7573554421-20150115-115436-1421351660.2431287.wav' - Filtered with: ''
Jan 15, 2015 2:16:19 PM it.loway.tpf.transaction.servlets.LowayBinaryStreamer myLog
SEVERE: [F29D1ED01C4375A80D5E1C3311BC48CB] Now sending: Mime: 'audio/wav'
Jan 15, 2015 2:16:20 PM it.loway.tpf.transaction.servlets.LowayBinaryStreamer myLog
SEVERE: [F29D1ED01C4375A80D5E1C3311BC48CB] All sent. Content length: 2318124 bytes

Jan 15, 2015 2:33:28 PM it.loway.tpf.transaction.servlets.LowayBinaryStreamer myLog
SEVERE: [C6510699C0A974C6A78356DE6E21C240] Sending file: '/var/spool/asterisk/monitor/2015/01/15/q-8002-5624791362-20150115-140301-1421359376.2435408.wav' - Under the name: 'q-8002-5624791362-20150115-140301-1421359376.2435408.wav' - Filtered with: ''
Jan 15, 2015 2:33:28 PM it.loway.tpf.transaction.servlets.LowayBinaryStreamer myLog
SEVERE: [C6510699C0A974C6A78356DE6E21C240] Now sending: Mime: 'audio/wav'
Jan 15, 2015 2:33:28 PM it.loway.tpf.transaction.servlets.LowayBinaryStreamer myLog
SEVERE: [C6510699C0A974C6A78356DE6E21C240] All sent. Content length: 741164 bytes

Title: Re: Recent slowness when pulling up call details
Post by: mirkox on January 16, 2015, 11:02:03

Hello Mike,

actually this kind of logs will be removed with the next version of QueueMetrics, so the file will increase much more slowly, in the meantime you can disable the logging in tomcat.

Mirko