Uploaded image for project: 'HornetQ'
  1. HornetQ
  2. HORNETQ-382

Core Bridge loses messages when paging

    Details

    • Steps to Reproduce:
      Hide

      The test method we've been using is:

      1. Set up both machines (as below).
      2. Run "sudo ifdown eth0" to disable the network on machine B.
      3. On machine A, inject messages using the Main program attached.
      4. Run "sudo ifup eth0" on machine B.
      5. Use jconsole to monitor the number of messages in each JMS queue, and file explorer to monitor the size of the page file(s).

      Show
      The test method we've been using is: 1. Set up both machines (as below). 2. Run "sudo ifdown eth0" to disable the network on machine B. 3. On machine A, inject messages using the Main program attached. 4. Run "sudo ifup eth0" on machine B. 5. Use jconsole to monitor the number of messages in each JMS queue, and file explorer to monitor the size of the page file(s).

      Description

      Using Hornetq-2.0.0.GA, it appears that JMS messages are being lost when sending them across a core bridge, if the network is down when the messages are sent. The messages that should be paged to disk on the receiving side are never received.

      We have only been able to reproduce this on HornetQ under JBoss 5, not using a stand-alone HornetQ server.

      We can't easily make a unit test case for this, because we've only found it when the network connection is down, which means running the test across two machines that don't always have a network connection.

      It would appear that, after sending queued messages on the bridge after the network starts, the first message that should be paged causes the page file to be created with size 0, and it any any subsequent messages are silently discarded. This is only a problem on machine B, not machine A (in which the messages are correctly paged). It also holds around 20 more messages in memory on B than it does on A.

      We have also tried attaching a consumer to the queue on B, and it does not appear to process all the incoming messages.

      Main program (basic message sender), and our configuration files for HornetQ (copy of hornetq.sar) are attached.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jmesnil Jeff Mesnil
                Reporter:
                robertjlee Robert Lee
              • Votes:
                3 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: