4 Replies Latest reply on Aug 29, 2002 5:22 AM by authjavauser

    More than one durable subscriber

    authjavauser


      Hi

      Can i have more than one durable subsriber for diffrent topics. For example i want to have durable subscription for topics topic/Tone , topic/Ttwo , with the same client ID and running simultanously ?

      Is it possible?

      AuthJavaUser

        • 1. Re: More than one durable subscriber
          larsinge

          I don't see why you can't.

          You (that is: your client) can even have multiple subscriptions on the same topic. A client can use different message selectors.

          A durable subscription must be identified by its own name. A topic name and a Client ID is not sufficient.

          • 2. Re: More than one durable subscriber
            authjavauser

            Hi

            Thanks for your response, actually when i start my second durable subscriber on different topic i get "Client Id error"
            my Jbossmqstate.xml looks like this

            john
            needle
            myexampleid
            anotherid


            i use "myexampleid" for first durable subscriber and "anotherid" for the second, but still it gives the same problem.
            I guess i am not setting jbossmqstate.xml properly
            Should it be done in some different way.
            I want to have multiple durable subscribtion for user john.

            Thanks for your help
            AuthJavaUser

            • 3. Re: More than one durable subscriber
              larsinge

              It could be a threading problem.

              A session can not have more than one thread. The main app is one thread and the onMessage is an other thread (managed by the JMS-server).

              Maybe you are trying to use multiple threads on one session. Make two sessions.

              • 4. Re: More than one durable subscriber
                authjavauser

                Hi

                Thanks for your reply. That means the Jbossmqstate.xml
                which I have written is right ?
                If so then i have to assume how many durable connections client is going to open and mention so many "ids" in jbossmqstate.xml before hand ?
                Cant i create an "id" for user dynamically?

                Regards
                AuthJavaUser