Uploaded image for project: 'Hibernate Search'
  1. HSEARCH-1922

JMS backend should set the JMS message header JMSXGroupID

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.4.0.CR1
    • Component/s: backend, directory provider
    • Labels:
      None

      Description

      When trying to setup a failover safe master/slave setup for Search using JMS, it is important that index updates for a given index are only processed by a single consumer (message driven bean). In case there are multiple beans listening to the same JMS queue as part of the failover strategy, without so called message grouping, index updates could be applied out of order, since the queue consumer work independently. Message grouping ensures that all messages for the same group get consumed by the same consumer (while it is alive).

      The key for message grouping is to set the standard JMS header JMSXGroupID. This is a per-condition for ActiveMQ as well as HornetQ.

        Attachments

          Activity

            People

            • Assignee:
              hardy.ferentschik Hardy Ferentschik
              Reporter:
              hardy.ferentschik Hardy Ferentschik
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: