- 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
‎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
‎09-25-2019 07:25 AM
Go to the config.xml and check the format of mid.proxy.host parameter. If it begins with http://, then you have to remove it.
I was puzzled by this error message for quite some time. Then after upgrading to Madrid, AMB started giving me some hints how to solve it. There was an exception with following error message:
Expected closing bracket for IPv6 address at index 13: http://[http://myproxyserver.example.com]:8080
After I have removed "http://" part from proxy configuration of the MID server (file config.xml), then it connects just fine.
MID server itself can work with both versions but AMB can't.