- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-12-2016 05:50 AM
We use a MID server, but the MID server log keeps giving these warnings:
ECCQueueMonitor.40 WARNING *** WARNING *** Reconnecting AMB channel..
ECCQueueMonitor.40 WARNING *** WARNING *** Unable to subscribe to AMB channel: /mid/server/77a7ba104fed1200b92af1728110c7dd
From the documentation I can understand the function of the AMB channel, but I cannot find any info on what could be causing connection to the channel to fail.
We use another MID server connected to a customers instance, and this one does not produce these warnings.
Both are hosted from the same machine, so the problem seems to be instance related.
Also, the MID server producing these warnings has a memory leak, and will eventually die with an out of memory message even though it is not actively used.
The other MID server has no memory leakage problems.
Both are fresh installs.
Any ideas?
The instances are different versions by the way. Helsinki for the one producing the warnings, Fuji for the other one.
Solved! Go to Solution.
- Labels:
-
Integrations
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-05-2017 02:43 AM
This finally got solved in Istanbul patch 6. The warnings remain, but the thread and memory usage is stable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-15-2016 04:29 PM
Ah ok. We've got a HI case open, but we'll see how it goes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-03-2017 08:54 AM
Hi Mark,
We are facing similar issue. Did you find any solution for this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-03-2017 10:46 PM
Hi Sanjiv,
The HI issue is still open and we have not had feedback in a while. I am trying to get confirmation that this issue will be fixed in the next Istanbul and Helsinki patches like Sam Polk said elsewhere in this thread.
Regards,
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-04-2017 05:09 AM
I upgraded my test environments to Helsinki patch 8 and it works fine now.
Regards,
Sanjiv Meher
M: +1 4702739015
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-04-2017 08:51 AM
PRB717454 is now closed with fixes in Helsinki Patch 7, Helsinki Patch 8 and Istanbul Patch 1