AMBClientProvider WARNING *** WARNING *** Unable to subscribe to AMB channel

[smahdi]

Hello,

We keep having this WARNING on the mid server logs.

12/07/18 14:54:42 (659) ECCQueueMonitor.40 WARNING *** WARNING *** Reconnecting AMB channel..
12/07/18 14:54:42 (659) Worker-Interactive:HeartbeatProbe-c3a4ca20dbde2f0090fd199f2996192d Worker starting: HeartbeatProbe
12/07/18 14:54:42 (659) Worker-Interactive:HeartbeatProbe-c3a4ca20dbde2f0090fd199f2996192d Probing heartbeatprobe
12/07/18 14:54:42 (659) ECCQueueMonitor.40 Initializing AMB client...
12/07/18 14:54:42 (659) Worker-Interactive:HeartbeatProbe-c3a4ca20dbde2f0090fd199f2996192d Finished firing the heartbeatprobe
12/07/18 14:54:42 (661) Worker-Interactive:HeartbeatProbe-c3a4ca20dbde2f0090fd199f2996192d Enqueuing: /appli/spice/bin/mid.prod_ldap/agent/work/monitors/ECCSender/output_0/ecc_queue.c3a4ca20dbde2f0090fd199f2996192d.xml
12/07/18 14:54:42 (661) Worker-Interactive:HeartbeatProbe-c3a4ca20dbde2f0090fd199f2996192d Worker completed: HeartbeatProbe time: 0:00:00.001
12/07/18 14:54:42 (661) AMBClientProvider Connecting AMB client to instance...
12/07/18 14:54:42 (679) AMBClientProvider WARNING *** WARNING *** Unable to subscribe to AMB channel: /mid/server/a2b45db2db9c0b008713fbc61d96193a
12/07/18 14:54:43 (087) ECCSender.1 Sending ecc_queue.c3a4ca20dbde2f0090fd199f2996192d.xml
12/07/18 14:55:36 (051) LogStatusMonitor.60 stats threads: 2274, memory max: 3641.0mb, allocated: 194.0mb, used: 32.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes
12/07/18 14:56:36 (056) LogStatusMonitor.60 stats threads: 2274, memory max: 3641.0mb, allocated: 194.0mb, used: 32.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes

We are using the "kingston-10-17-2017__patch10-hotfix2-11-01-2018_11-02-2018_1054" version.

any thoughts on how we can fix this warning ?

Thanks for your help.

Mahdi SAIDANE.

[rahulpandey · Accepted solution]

Hi,

Similar issue has been documented here

https://hi.service-now.com/kb_view.do?sysparm_article=KB0621950

[Chris M3]

You mentioned your on Kingston, the accepted solution though is listed fixed with initial Jakarta release.  Did something in the article actually resolve the issue?  We are seeing this also on our Kingston instance.  In fact, the fix seems to only prevent the memory leak issue, which I don't believe we are seeing.