Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-5799

Cluster messages not redistributed after node hard kill

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Critical
    • EAP 5.1.0 Post Release
    • EAP 5.1.0 Post Release
    • HornetQ
    • None

    • Windows, Integrated with jboss5.1

    • Hide

      Get two jboss5.1 servers running with hornetQ integrated
      Have one queue clustered across the two
      Have one Message Driven Bean pulling from the Q
      Have a client send messages to the cluster
      -Notice the cluster round robins the requests properly
      Kill one of there servers I used Kill -9 on the process
      send some more messages to the cluster
      -Notice every other one is received and processed by the surviving node and every other one is queued up on the bridge but there isn't any server to consume the messages any more.

      Show
      Get two jboss5.1 servers running with hornetQ integrated Have one queue clustered across the two Have one Message Driven Bean pulling from the Q Have a client send messages to the cluster -Notice the cluster round robins the requests properly Kill one of there servers I used Kill -9 on the process send some more messages to the cluster -Notice every other one is received and processed by the surviving node and every other one is queued up on the bridge but there isn't any server to consume the messages any more.

    Description

      Cluster messages not redistributed after node hard kill.

      So we have a cluster going with 2 nodes using hornetQ integrated with Jboss5. We bring the two nodes up and they discover each other fine. I bring a client up and start sending messages to a queue that is clustered across the nodes. Everything will work great for a while the messages get load balanced and all is happy. Then I can get in a strange state in a couple of different ways, but the easiest way is if I go to one of the server nodes and just kill the server process. The one server appears to detect the other node went down and adjusts its cluster view but after this happens every other message I send to the server doesn't get processed. It looks like the message is placed on the bridge queue that was connecting the two nodes. The consumer count on the bridge queue is one but the other server is dead and so it never gets picked up by anything. I would like it if the other node dies that the node that is still running would grab the messages and start running them. In this case I can restart the other node and it starts picking the messages up when it comes back up but there are other situations where this same sort of thing will happen but even after a restart of the one server it never starts grabbing messages off the brigde any more. In that case I have to restart the entire cluster

      Attachments

        Activity

          People

            rhn-support-jawilson Jimmy Wilson
            parmstrong_jira Phil Armstrong (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: