2 Replies Latest reply on Jan 2, 2002 5:05 PM by Mark Speich

    Multiple connections with durable subscriptions for same use

    Mark Speich Newbie

      I have a question about configuring durable subscriptions.

      Currently, users are required to define an 'Id' child element of the 'User' element in the jbossmq-state.xml file if they want that user to be able to create durable subscriptions. Defining the 'Id' element causes any connections made by that user to be assigned that Id as the connection's client ID. This prevents the user from being able to connect to the JBossMQ server from another JVM since connections must have unique client ID's.

      I don't understand why the 'Id' element is necessary for creating durable subscriptions. Why can't the durable subscriptions be mapped to the user's name instead?

        • 1. Re: Multiple connections with durable subscriptions for same
          Hiram Chirino Expert

          It's part of the JMS spec. Well at least how I interpreted it. If you think we made an error in the interpretation, let me know.

          Regards,
          Hiram

          • 2. Re: Multiple connections with durable subscriptions for same
            Mark Speich Newbie

            I looked at the JMS spec again, and it looks like it specifies a relationship between a connection's client ID and a durable subscriber. I couldn't find anything about a relationship between a connection's client ID and a user. So, does it then make sense to have a durable subscriber list that is independent of the user list? The jbossmq-state.xml file in this scenario might look something like this:



            ....
            ........john
            ........needle
            ....
            ....
            ........Client1
            ........
            ............Subscriber1
            ............testTopic
            ........
            ....


            The 'User' element could still have an 'Id' child element, but it wouldn't be required. That would allow the user to have multiple connections to the message server.