3 Replies Latest reply on Jul 7, 2009 9:41 AM by Jerry Jacob

    EnableOrderingGroup attribute in JBM 1.4.1

    Jerry Jacob Newbie

      Hi,

      JBoss 5.0.1 GA
      JBoss Messaging 1.4.1 GA.

      I have an ActiveMQ queue which is the Producer and a JBoss Messaging queue (local) which is consuming messages through a Message Bridge. My requirement is that the messages should be consumed in the same order in which they are sent.

      For this I have set a Message groupd ID (JMSXGroupID) from the Producer (ActiveMQ) on the messages when I send them. But still I could not get the messages in the same order in which they were sent. After going through the JBM docs, it was understood that the ordering needs to be enabled at the consumer side also. But when I add this attributes to the connection0-factories-service.xml, I am getting the following exception

      
      6:53:29,375 INFO [ServiceConfigurator] Problem configuring service jboss.messaging.connectionfactory:service=ConnectionFactory
      rg.jboss.deployment.DeploymentException: No Attribute found with name: enableOrderingGroup
       at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:318)
       at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:466)
       at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
      
      


      Which version of JBM supports this attribute? Even if I manage to set this attribute, can the messages be consumed at JBM side in the same order in which they are sent from ActiveMQ?

      Thanks

        • 1. Re: EnableOrderingGroup attribute in JBM 1.4.1
          Yong Hao Gao Master

          Hi,
          So far only JBM 1.4.4.GA (or 1.4.0.sp3-cp08 for EAP) supports that attribute. For AS 5.x you need to wait for the next release for it.

          • 2. Re: EnableOrderingGroup attribute in JBM 1.4.1
            Tim Fox Master

            The JMS spec guarantees that messages sent from a particular producer are delivered in order to a single consumer in the absence of failures.

            You don't need order grouping for that.

            If you're not seeing that, please add a test case that demonstrates it and someone will investigate it since it would imply there is a bug.

            • 3. Re: EnableOrderingGroup attribute in JBM 1.4.1
              Jerry Jacob Newbie

              Thanks for the quick response.

              If there is only one consumer, the messages are coming in order. For e.g, if I use singleton MDB to consume the messages they are coming in order.

              Since our requirement is to process bulk amount of messages, we are thinking of concurrently processing the messages. To achieve that, we are using multiple instances of the MDB's (using maxSession) to process the messages. Another approach which we followed was to create multiple bridges which consumes messages from the same queue. But we did not get the correct ordering in either of these approaches.

              Is there a beta version of JBM available with 'EnableOrderingGroup' attribute which we can use for our testing?

              Thanks again for the quick response