n***@corporatefallout.com
2003-05-12 20:43:43 UTC
Hello,
I read in the JMS API that, "Only one session at a time can have a
TopicSubscriber for a particular durable subscription.".
However, is there a way to do this besides defining the subscribers
individually under the administered topic in the config file?
I can see how the server might have trouble keeping track of the
subscribers, but I wasn't sure if there was some sort of ID generated
internally that the servers uses to keep track of the subscribers.
I'd like to be able to have multiple topics, each with a group of durable
clients. Having to edit the config file might become a pain when the
number of clients grealy increases.
Any help or advice is greatly appreciated.
Thanks,
Troy
I read in the JMS API that, "Only one session at a time can have a
TopicSubscriber for a particular durable subscription.".
However, is there a way to do this besides defining the subscribers
individually under the administered topic in the config file?
I can see how the server might have trouble keeping track of the
subscribers, but I wasn't sure if there was some sort of ID generated
internally that the servers uses to keep track of the subscribers.
I'd like to be able to have multiple topics, each with a group of durable
clients. Having to edit the config file might become a pain when the
number of clients grealy increases.
Any help or advice is greatly appreciated.
Thanks,
Troy