I do not know why they classify as an ERROR. This is good for information
purposes; it is not an error.
Go ahead and telnet to your broker using your brokers port. Then do
nothing. You will generate this error after the timeout. This error is
caused by many different possibilities:
Your
Do you have failover and reconnect logic? It might not be a problem for you
if you have this logic. Your client will keep trying to connect and once
connected, will send the message. new connections are not super reliable
(in my opinion). if the listening socket is busy i have seen new
On the client, how do i set up the connection priority for the broker URI?
failover:(tcp://x.x.x.x:xx,tcp://y.y.y.y:yy)
currently, the client will randomly pick an IP and try to connect to it.
This works fine, but i do not want random.
I would like to have a list of 4 or more brokers and
