4 Replies Latest reply on Apr 2, 2013 8:51 AM by Dennis Buttery

    Non-Clustered listener subscribing to Clustered Topic?

    Dennis Buttery Newbie

      Hi all,

       

          Is this even possible?

       

          If a Topic is being clustered across mulitple nodes, can a non-clustered ESB subscribe to the topic and receive its messages?

       

      Thanks,

      -Dennis

        • 1. Re: Non-Clustered listener subscribing to Clustered Topic?
          Tom Cunningham Master

          Yes, you should be able to have a clustered topic and standalone ESB listener.     Are you having issues trying to set this up?

          • 2. Re: Non-Clustered listener subscribing to Clustered Topic?
            Dennis Buttery Newbie

            I have an ESB (publisher) that is deployed clustered across two nodes. That ESB establishes a JMS topic.

             

            I have a subscriber ESB that is non-clustered and wants to receive the messages from the publisher.

             

            The subscriber ESB will not deploy.  It complains about not being able to see the clustered topic.  "There is no administratively defined...."

             

            The topic is created via mbean in the publisher with the "Clustered" attribute set to true.

             

            The subscriber ESB has a provider defined in its jboss-esb.xml to listen to that topic.

             

            Is there a config piece that I'm overlooking?

             

            Thanks,

            -Dennis

            • 3. Re: Non-Clustered listener subscribing to Clustered Topic?
              Tom Cunningham Master

              Can you post your deployment.xml?

              • 4. Re: Non-Clustered listener subscribing to Clustered Topic?
                Dennis Buttery Newbie

                Publisher's deployment.xml

                 

                <?xml version="1.0" encoding="UTF-8"?>

                <jbossesb-deployment>

                <depends>xip.properties:module=S0029_PersonBulkPublisherESB,name=Properties,type=JNDI</depends>

                <depends>jboss.messaging.connectionfactory:service=S0029_Common.JBM.CF</depends>

                <depends>jboss.messaging.destination:module=S0029_PersonBulkPublisherESB,service=Queue,name=S0029_PersonBulkPublisher.JMS.Queue</depends>

                <depends>jboss.messaging.destination:module=S0029_PersonBulkPublisherESB,service=Queue,name=S0029_PersonBulkPublisher.ESB.Queue</depends>

                <depends>jboss.messaging.destination:module=S0029_PersonBulkPublisherESB,service=Queue,name=S0029_PersonBulkPublisher.PublishToTopic.ESB.Queue</depends>

                <depends>jboss.messaging.destination:module=S0029_PersonBulkPublisherESB,service=Topic,name=S0029_PersonBulkPublisher.Person.Topic</depends>

                </jbossesb-deployment>

                 

                Subscriber's deployment.xml

                 

                <?xml version="1.0" encoding="UTF-8"?>

                <jbossesb-deployment>

                <depends>xip.properties:module=S0274_CdmAbcPersonESB,name=Properties,type=JNDI</depends>

                <depends>jboss.messaging.connectionfactory:service=S0274_Common.JBM.CF</depends>

                <depends>jboss.messaging.destination:module=S0274_CdmAbcPersonESB,service=Queue,name=S0274_CdmAbcPerson.JMS.Queue</depends>

                <depends>jboss.messaging.destination:module=S0274_CdmAbcPersonESB,service=Queue,name=S0274_CdmAbcPerson.ESB.Queue</depends>

                </jbossesb-deployment>