Bad Failover Behaviour

[SarcasmMonster]

If I run start consuming messages from a queue using receive and then manually close the broker (with another thousand messages left in the queue) I get a warning that the failover is attempting to reconnect. Once I reboot ActiveMQ then I am notified that the failover reconnected. However, I will not receive any more messages. It doesn't do anything. But once I send just 1 more message to the queue, then the consumer will start receiving the rest of the messages.

Why does it take publishing another message before the failover unblocks?

Using ActiveMQ 5.1

[rajdavies]

Hi SarcasmMonster,

that is strange!  - though it does sound familiar - (i.e. known  
issue). Have you tried with the latest 5.2-SNAPSHOT ?

thanks,

Rob

On 7 Oct 2008, at 21:19, SarcasmMonster wrote:

>
> If I run start consuming messages from a queue using receive and then
> manually close the broker (with another thousand messages left in  
> the queue)
> I get a warning that the failover is attempting to reconnect. Once I  
> reboot
> ActiveMQ then I am notified that the failover reconnected. However,  
> I will
> not receive any more messages. It doesn't do anything. But once I  
> send just
> 1 more message to the queue, then the consumer will start receiving  
> the rest
> of the messages.
>
> Why does it take publishing another message before the failover  
> unblocks?
>
> Using ActiveMQ 5.1
> --
> View this message in context: http://www.nabble.com/Bad-Failover-Behaviour-tp19866385p19866385.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

[SarcasmMonster]

I haven't tried the lastest snapshot, but it's not too big of an issue in my case where things are constantly being published. I just couldn't find any mentions of it and was wondering if it was something I was doing wrong.