Client recovery not working

[mohitanchlia]

I have 2 node cluster and I am currently performing recovery test. I have network interval set to 1 sec, but actual recovery is taking around 1 mt.

    factory.setAutomaticRecoveryEnabled(true);
    factory.setNetworkRecoveryInterval(1000);

Steps

1. Create a mirror queue
2. Start producing and consuming
3. Shutdown one of the rabbitmq-server
4. Look at the logs. Logs show following message for about 1 mt and then recovers:

com.rabbitmq.client.AlreadyClosedException: connection is already closed due to connection error; protocol method: #method<connection.close>(reply-code=320, reply-text=CONNECTION_FORCED - broker forced connection closure with reason 'shutdown', class-id=0, method-id=0)

[michaelklishin]

CONNECTION_FORCED means a connection was closed via rabbitmqctl or management's UI Close button. Please ask questions on rabbitmq-users.

[mohitanchlia]

It appears to be a bug since I expected connections to recover in few secs
but it didn't.
On Tue, Oct 28, 2014 at 11:42 PM, Michael Klishin notifications@github.com
wrote:

CONNECTION_FORCED means a connection was closed via rabbitmqctl or
management's UI Close button. Please ask questions on rabbitmq-users.

—
Reply to this email directly or view it on GitHub
#22 (comment)
.

[michaelklishin]

There is not a lot of evidence suggesting that. If TCP connection takes a long time for whatever reason, RabbitMQ connection cannot possibly succeed earlier, for example.