-
1. Re: JMS Problem
adrian.brock Sep 22, 2003 2:47 PM (in response to vincentchun)Are you using a durable subscription?
It is not physic, it won't hold messages for subscriptions
that have been not created yet.
Regards,
Adrian -
2. Re: JMS Problem
vincentchun Sep 22, 2003 11:45 PM (in response to vincentchun)Thanks for Adrian first.
I have used the Durable Subscriber.
And part of my code as follow:
String username = "Vincent";
TopicSubscriber sub = session.createDurableSubscriber(topic, username, "user = '" + username + "'", false);
Except durable subscriber, is there any extra setting need? -
3. Re: JMS Problem
vincentchun Sep 23, 2003 12:19 AM (in response to vincentchun)I mean, is there any method (or any setting) which can make a message stay in server?
Thanks for your help! -
4. Re: JMS Problem
adrian.brock Sep 23, 2003 8:52 AM (in response to vincentchun)Check jbossmq-state.xml
Do you see ID: in your durable subscriptions?
Use connection.setClientID()
Regards,
Adrian -
5. Re: JMS Problem
vincentchun Sep 23, 2003 1:47 PM (in response to vincentchun)Yes, I can see the ID as follow:
ID:102
Vincent
TestTopic
user = 'Vincent'
What is the meaning of "Use connection.setClientID()"?
Thanks for your help! -
6. Re: JMS Problem
adrian.brock Sep 23, 2003 4:42 PM (in response to vincentchun)A durable subscription is a product of the connection's
clientID and the subscription name.
You can either setClientID on the connection or configure
the user with a client id in jbossmq-state.xml
(see john/needle in the default config for the latter).
Regards,
Adrian -
7. Re: JMS Problem
adrian.brock Sep 23, 2003 4:42 PM (in response to vincentchun)ID:102 means you did neither so the connection has
an "anonymous" clientID
Regards,
Adrian