Home > Help Desk > Knowledge Base > Data API > DAPI Knowledge Base > Debug Log - HoldRequest failed with /meta/connect msgs

Debug Log - HoldRequest failed with /meta/connect msgs

Table of contents
No headers

A normal hold request looks like this in the debug log:

 

-*- 2015-01-14 01:24:03 | phoney: (state: online) sending 'holdRequest line=line1 info=yes$$

-*- 2015-01-14 01:24:03 | locket: Publishing message:holdRequest line=line1 info=yes

 

-*- 2015-01-14 01:24:03 | locket: Handling meta message channel: /service/liveops/agent/qdck3gxnuo12in81lvrv4m1lpdaz

-*- 2015-01-14 01:24:03 | locket: Agent subscriber heard message:

-*- 2015-01-14 01:24:03 | locket: + data (object) [object Object]

| + payload (string) 'hold:yes'

| + clientId (string) 'com.liveops.cometd.gateway.GatewayServiceLocal_2xypqcgwhp160h1s50rbqup9w'

+ channel (string) '/service/liveops/agent/qdck3gxnuo12in81lvrv4m1lpdaz'

-*- 2015-01-14 01:24:03 | locket: Agent subscriber heard message:

-*- 2015-01-14 01:24:03 | locket: + data (object) [object Object]

| + payload (string) 'holdStatus line=line1 info=yes'

| + clientId (string) 'com.liveops.cometd.gateway.GatewayServiceLocal_2xypqcgwhp160h1s50rbqup9w'

| *

+ channel (string) '/service/liveops/agent/qdck3gxnuo12in81lvrv4m1lpdaz'

 

However, the hold request I see in customer's debug log looks like this:

 

-*- 2015-01-13 21:33:04 | phoney: (state: online) sending 'holdRequest line=line1 info=yes$$

-*- 2015-01-13 21:33:04 | locket: Publishing message: holdRequest line=line1 info=yes

 

-*- 2015-01-13 21:33:04 | locket: Handling meta message channel: /service/liveops/agent/71tr9r7jzrvbwdb6ju0uvagdx17j

-*- 2015-01-13 21:33:14 | locket: Handling meta message channel: /meta/connect

-*- 2015-01-13 21:33:29 | locket: Handling meta message channel: /meta/connect

-*- 2015-01-13 21:33:34 | locket: Agent subscriber heard message:

-*- 2015-01-13 21:33:34 | locket: + data (object) [object Object]

| + payload (string) 'ping'

| + clientId (string) 'com.liveops.cometd.gateway.GatewayServiceLocal_211p4macy0rdnd1f2a4bjdmtk2k'

| *

+ channel (string) '/service/liveops/agent/71tr9r7jzrvbwdb6ju0uvagdx17j'

-*- 2015-01-13 21:33:34 | locket: Handling meta message channel: /meta/connect

-*- 2015-01-13 21:33:34 | phoney: raw data: ping

-*- 2015-01-13 21:33:34 | phoney: parsed data: ping,

-*- 2015-01-13 21:33:34 | phoney: (state: online) sending 'pong $$

-*- 2015-01-13 21:33:34 | locket: Publishing message: pong

 

The lines in yellow provide a clue – apparently there was a network failure of some type, because there is a 10-second gap from 21:33:04 to 21:33:14, then another 5-second gap.

 

Finally, 30 seconds after the original holdRequest, the payload is reported as just a ‘ping,’ instead of ‘hold:yes’.

 

I would suggest running the traceroute instructions from an affected workstation if this occurs again.

You must to post a comment.
Last modified
17:52, 13 Jan 2015

Tags

Classifications

This page has no classifications.