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.
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
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
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.
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?