3 Replies Latest reply on Feb 9, 2012 4:01 AM by hushen.savani
      • 1. Re: Non-clustered queue in clustered environment
        ataylor

        as i have said you cant. But you can use a message selector and make sure your consumer uses this

        • 2. Re: Non-clustered queue in clustered environment
          hushen.savani

          Hi Andy,

           

               Thanks. But message selector will not help in my case because, I deploy same application ear on both the nodes. So, there will be the same sort of consumers on both the nodes. However, I have read a workaround posted on this thread. I have tried using it as following:

           

          Queues defined in hornetq-jms.xml:

                   <!-- Clustered Queues -->

                  <queue name="clustered.mocmMasterQueue">

                          <entry name="/queue/clustered.mocmMasterQueue"/>

                  </queue>

           

                  <queue name="clustered.mocmProcessingQueue">

                          <entry name="/queue/clustered.mocmProcessingQueue"/>

                  </queue>

           

                    <queue name="clustered.mocmSuccessQueue">

                          <entry name="/queue/clustered.mocmSuccessQueue"/>

                  </queue>

           

                  <queue name="clustered.mocmFailureQueue">

                          <entry name="/queue/clustered.mocmFailureQueue"/>

                  </queue>

           

                   <!-- Non-Clustered Queue -->
                  <queue name="nonclustered.mocmManagementQueue">

                          <entry name="/queue/nonclustered.mocmManagementQueue"/>

                  </queue>

           

          Address Configured in Clusted Connection in hornetq-configuration.xml:

          <cluster-connections>

                <cluster-connection name="mocm-cluster">

                 <address>jms.queue.clustered.#</address>

                   <connector-ref>netty-connector</connector-ref>

                   <retry-interval>500</retry-interval>

                   <use-duplicate-detection>true</use-duplicate-detection>

                   <forward-when-no-consumers>true</forward-when-no-consumers>

                   <max-hops>1</max-hops>

                   <discovery-group-ref discovery-group-name="mocm-discovery-group"/>

                </cluster-connection>

             </cluster-connections>

           

               Now, with this configurations, all the queues has gone non-clustered in clustered environment. Messages are not being round-robined. Can you please suggest what could've gone wrong here?

           

               Thanks.

           

          Best Regards,

          Hushen Savani

          • 3. Re: Non-clustered queue in clustered environment
            hushen.savani

            Continuing related discussion on this thread:

                

                 https://community.jboss.org/message/715231    

            1 of 1 people found this helpful