MID server unable to subscribe to AMB channel

mark69 · ‎10-12-2016

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.

mark69 · ‎07-05-2017

This finally got solved in Istanbul patch 6. The warnings remain, but the thread and memory usage is stable.

View solution in original post

klopmas · ‎10-16-2016

You may be blocking the ports the AMB channel is using to communicate.

I see this message when running my MIDs via a proxy while blocking most of

the ports.

mark69 · ‎10-19-2016

Hi Sam,

Thank you for you reaction.

Do you have any idea what ports this could be? I cannot find any information about this in the documentation. All it says is that port 443 is used to communicate with the instance. But that is outbound traffic. Nothing is said about inbound traffic.

And the whole idea of having a MID server is that you can make your network reachable without having to open up all kinds of ports, isn't it?

Regards,

Mark

klopmas · ‎10-19-2016

Hello Mark,

I am not sure the exact port but we are still looking into this.

I can say we are seeing this issue when the MID is configured

to go through a proxy, we see the http thread count go up

until the MID fails with a 'java.lang.OutOfMemoryError: unable to create new native thread'.

I set up a proxy and blocked all ports except 443 but if the proxy is

blocking packet based on the protocols (SOAP) you could potentially

run into this issue.

Can you please open a ticket with Support so they have a record

of this issue.

mark69 · ‎10-20-2016

Hi Sam,

We do connect through a proxy, so that could be the problem.

A ticket has been logged. I will post the outcome of that here later.