JBoss Developer: Message List - HornetQ Stuck Scenario: Messages routed to dead nodesMost recent forum messageshttps://developer.jboss.org/community/hornetq?view=discussionsJive Engage2011-06-13T14:33:05Z2011-06-13T14:33:05ZenRe: HornetQ Stuck Scenario: Messages routed to dead nodesClebert Suconic/people/clebert.suconicdo-not-reply@jboss.com2011-06-13T14:33:05Z2011-06-13T14:33:05Z<!-- [DocumentBodyStart:f3f6304e-d927-4868-93b9-00dd804ac79c] --><div class="jive-rendered-content"><p><a class="jive-link-external-small" href="https://issues.jboss.org/browse/HORNETQ-716" rel="nofollow">https://issues.jboss.org/browse/HORNETQ-716</a></p></div><!-- [DocumentBodyEnd:f3f6304e-d927-4868-93b9-00dd804ac79c] --><img src='/beacon?t=1425408674236' />2011-06-13T14:33:05Z3 years 9 months ago0Re: HornetQ Stuck Scenario: Messages routed to dead nodesClebert Suconic/people/clebert.suconicdo-not-reply@jboss.com2011-06-13T14:26:15Z2011-06-13T14:26:15Z<!-- [DocumentBodyStart:854e1e07-5d4f-4a46-868f-8767b8d70a8c] --><div class="jive-rendered-content"><p>This is what we are working on right not. I have created a branch to do some cleanup on clustering for this.</p></div><!-- [DocumentBodyEnd:854e1e07-5d4f-4a46-868f-8767b8d70a8c] -->2011-06-13T14:26:15Z3 years 9 months ago10HornetQ Stuck Scenario: Messages routed to dead nodesRichard Kennard/people/kennardconsultingdo-not-reply@jboss.com2011-06-13T14:16:29Z2011-06-13T14:16:29Z<!-- [DocumentBodyStart:c9898657-962d-4e4c-9756-f265ab9bb74e] --><div class="jive-rendered-content"><p>Hi guys,</p><p style="min-height: 8pt; height: 8pt; padding: 0px;">&nbsp;</p><p>I am trying to upgrade our JBoss Messaging application to use HornetQ. I am experiencing my MDBs getting 'stuck' and I have managed to untangle a few different scenarios that cause this. I will try and put together test cases, but I would appreciate your help as to where to look.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;">&nbsp;</p><p>We have a cluster of 2 nodes. One of these nodes is responsible for picking up some FTP files, parsing them, and sending messages to the queue. Because the nodes are varying speeds, I have set ConsumerWindowSize to 0. What I am seeing is that if both nodes are up, everything is fine.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;">&nbsp;</p><p>But if I take 1 node down, wait for a few minutes, and then try sending some messages to the queue, exactly 1/2 of the messages get processed. If I look in my logs it is a very clean split - like every odd number gets processed and every even numbered message disappears. It's almost as if HornetQ is still routing the messages to the dead node?</p><p style="min-height: 8pt; height: 8pt; padding: 0px;">&nbsp;</p><p>Is this possible, is there routing code that is meant to detect whether a node is dead and, if so, could if still be accidentally routing messages there?</p><p style="min-height: 8pt; height: 8pt; padding: 0px;">&nbsp;</p><p>Regards,</p><p style="min-height: 8pt; height: 8pt; padding: 0px;">&nbsp;</p><p>Richard.</p></div><!-- [DocumentBodyEnd:c9898657-962d-4e4c-9756-f265ab9bb74e] -->2011-06-13T14:16:29Z3 years 9 months ago20