« previous next »
Pages: [1]

Author Topic: Communication error on wallboard  (Read 7687 times)

Richarddb

  • Jr. Member
  • **
  • Posts: 57
  • Karma: 0
    • View Profile
Communication error on wallboard
« on: January 11, 2011, 07:25:31 »
Hi,

Since a few days our wallboard gives an error around 5 PM with the following error code:

Communication error: RPC server did not send response before timeout

What does it mean and how can we solve this?
Logged

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Communication error on wallboard
« Reply #1 on: January 11, 2011, 14:33:49 »
You should be looking at the QM logs and see if there is an error there as well, or it is just the processing of data that takes too long.
 
Logged

Richarddb

  • Jr. Member
  • **
  • Posts: 57
  • Karma: 0
    • View Profile
Re: Communication error on wallboard
« Reply #2 on: January 13, 2011, 09:42:09 »
Since 2 months it happens and always on the same time around 5, we didn't change anything. Around 5 pm there are almost no callers.
In which log could there be information?

When the screen refreshes, it's working again so it's a quit strange error.
« Last Edit: January 13, 2011, 10:33:12 by Richarddb »
Logged

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Communication error on wallboard
« Reply #3 on: January 13, 2011, 11:04:56 »
Try looking under /usr/local/queuemetrics/tomcat/logs if you see anything generated.
Logged

Richarddb

  • Jr. Member
  • **
  • Posts: 57
  • Karma: 0
    • View Profile
Re: Communication error on wallboard
« Reply #4 on: January 13, 2011, 11:29:50 »
There are some localhost_log files which are around 2GB each
Logged

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Communication error on wallboard
« Reply #5 on: January 14, 2011, 09:51:58 »
Likely on catalina.out as well.
Try and delete all files, restart QM and wait until the error happens.
Logged

Richarddb

  • Jr. Member
  • **
  • Posts: 57
  • Karma: 0
    • View Profile
Re: Communication error on wallboard
« Reply #6 on: January 14, 2011, 12:04:08 »
Probably this is the code of the time when the error came... do you know if there is anything wrong here?

Class: it.loway.app.queuemetrics.autenticazione.preparaParametriReport
Class: it.loway.app.queuemetrics.validazione.logon
Class: it.loway.app.queuemetrics.autenticazione.effettuaLogOn
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 684 ms
4.JSON In esecuzione:Tue Jan 11 17:06:48 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 48 ms
4.JSON In esecuzione:Tue Jan 11 17:06:49 CET 2011
[75BF2C3D004397A5AC4410F8BEBC37BA] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 51 ms
4.JSON In esecuzione:Tue Jan 11 17:06:50 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 78 ms
4.JSON In esecuzione:Tue Jan 11 17:06:52 CET 2011
LoadAttivitaAgente - modo file - Agente 'Agent/2387' - lookback:65000 bytes
Unknown verb: ''
[E277F52D2481F4F014A8A9D318840B33] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 47 ms
4.JSON In esecuzione:Tue Jan 11 17:06:54 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 43 ms
4.JSON In esecuzione:Tue Jan 11 17:06:57 CET 2011
LoadAttivitaAgente - modo file - Agente 'Agent/2438' - lookback:65000 bytes
Unknown verb: ''
[E277F52D2481F4F014A8A9D318840B33] 201101111706 Tempo totale esecuzione verbo 'qm_realtime2_ds': 39 ms
4.JSON In esecuzione:Tue Jan 11 17:06:59 CET 2011
LoadAttivitaAgente - modo file - Agente 'Agent/2689' - lookback:65000 bytes
Unknown verb: ''
[75BF2C3D004397A5AC4410F8BEBC37BA] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 49 ms
4.JSON In esecuzione:Tue Jan 11 17:07:00 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 46 ms
4.JSON In esecuzione:Tue Jan 11 17:07:02 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 48 ms
4.JSON In esecuzione:Tue Jan 11 17:07:04 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 47 ms
4.JSON In esecuzione:Tue Jan 11 17:07:07 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 147 ms
4.JSON In esecuzione:Tue Jan 11 17:07:10 CET 2011
[75BF2C3D004397A5AC4410F8BEBC37BA] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 47 ms
4.JSON In esecuzione:Tue Jan 11 17:07:10 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 45 ms
4.JSON In esecuzione:Tue Jan 11 17:07:12 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 45 ms
4.JSON In esecuzione:Tue Jan 11 17:07:14 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 52 ms
4.JSON In esecuzione:Tue Jan 11 17:07:17 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 45 ms
4.JSON In esecuzione:Tue Jan 11 17:07:19 CET 2011
[75BF2C3D004397A5AC4410F8BEBC37BA] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 49 ms
4.JSON In esecuzione:Tue Jan 11 17:07:20 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 51 ms
4.JSON In esecuzione:Tue Jan 11 17:07:22 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 49 ms
4.JSON In esecuzione:Tue Jan 11 17:07:24 CET 2011
LoadAttivitaAgente - modo file - Agente 'Agent/2394' - lookback:65000 bytes
Unknown verb: ''
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 55 ms
4.JSON In esecuzione:Tue Jan 11 17:07:27 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 59 ms
4.JSON In esecuzione:Tue Jan 11 17:07:29 CET 2011
[75BF2C3D004397A5AC4410F8BEBC37BA] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 44 ms
4.JSON In esecuzione:Tue Jan 11 17:07:30 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 49 ms
4.JSON In esecuzione:Tue Jan 11 17:07:32 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 48 ms
4.JSON In esecuzione:Tue Jan 11 17:07:34 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 44 ms
4.JSON In esecuzione:Tue Jan 11 17:07:37 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 45 ms
4.JSON In esecuzione:Tue Jan 11 17:07:39 CET 2011
[75BF2C3D004397A5AC4410F8BEBC37BA] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 45 ms
4.JSON In esecuzione:Tue Jan 11 17:07:40 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 52 ms
4.JSON In esecuzione:Tue Jan 11 17:07:42 CET 2011
[E277F52D2481F4F014A8A9D318840B33] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 40 ms
4.JSON In esecuzione:Tue Jan 11 17:07:44 CET 2011
[3CAF9104F22CDBAE3B36BC7570E4D854] 201101111707 Tempo totale esecuzione verbo 'qm_realtime2_ds': 55 ms
4.JSON In esecuzione:Tue Jan 11 17:07:47 CET 2011
*** DBVER:19
*** Esce 3
REQUEST:
Logged

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Communication error on wallboard
« Reply #7 on: January 18, 2011, 15:55:39 »
Quote from: Richarddb on January 14, 2011, 12:04:08
Probably this is the code of the time when the error came... do you know if there is anything wrong here?

Class: it.loway.app.queuemetrics.autenticazione.preparaParametriReport
Class: it.loway.app.queuemetrics.validazione.logon

Nothing wrong, a Java Stack trace would be quite long and visible.
The system seems pretty snappy - it reloads all data for the realtime report in 40 to 60 msec.
Logged

Richarddb

  • Jr. Member
  • **
  • Posts: 57
  • Karma: 0
    • View Profile
Re: Communication error on wallboard
« Reply #8 on: January 19, 2011, 12:03:09 »
But is there something we can do to not get the Communication error anymore?
Logged

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Communication error on wallboard
« Reply #9 on: January 20, 2011, 09:59:30 »
I really should see the error - you sure there is none?
Logged

Richarddb

  • Jr. Member
  • **
  • Posts: 57
  • Karma: 0
    • View Profile
Re: Communication error on wallboard
« Reply #10 on: January 20, 2011, 14:00:03 »
I could send/show you a daily log? Because it happens every day between 17.00 PM and 17.10 PM.
It's a catalina.out log of 3.4 MB
« Last Edit: January 27, 2011, 16:51:13 by Richarddb »
Logged

Richarddb

  • Jr. Member
  • **
  • Posts: 57
  • Karma: 0
    • View Profile
Re: Communication error on wallboard
« Reply #11 on: January 27, 2011, 16:51:20 »
Is this an option?
Logged

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Communication error on wallboard
« Reply #12 on: January 28, 2011, 09:37:22 »
Yes - please upload it somewhere for inspection and send us by email the link.
Logged

Richarddb

  • Jr. Member
  • **
  • Posts: 57
  • Karma: 0
    • View Profile
Re: Communication error on wallboard
« Reply #13 on: January 31, 2011, 11:43:22 »
I sent you a message with the link.
Logged

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Communication error on wallboard
« Reply #14 on: February 01, 2011, 16:56:36 »
I did check and there is nothing like an error on the log.
I suspect that for some reason (maybe a cron job) the server is very loaded at that moment so the client times out.....

Logged
Pages: [1]
« previous next »