-
1. Re: Multiple Issues with Interceptor.
clebert.suconic Oct 29, 2010 9:54 AM (in response to rahul_gsg)The ConsumerID should be based on a counter started at the client. Starting at 0. Maybe it's 0 because you only have a single consumer.
-
2. Re: Multiple Issues with Interceptor.
rahul_gsg Oct 29, 2010 12:52 PM (in response to clebert.suconic)Hi Clebert,
When I started multiple subscribers using REST for a single topic, I saw the same IDs getting printed through the interceptors for all the subscriptions in SessionCreateConsumerMessage, However the chennelId was getting incremented always. [So this means if the remote address is same , the consumerId will kept same always?]
Problem I am facing is , if I have two topics with one subsriber for each and when the subscribers call unsubscribe or if they idle time out , I will get SessionConsumerCloseMessage event from both . In this case consumerid and channelid will be 0 for both unsubscriptions .
How would I differentiate for which topic these unscriptions belong to in the interceptor as SessionConsumerCloseMessage doesn't have any info about queue/topic they belonged to?
-
3. Re: Multiple Issues with Interceptor.
rahul_gsg Oct 29, 2010 12:57 PM (in response to rahul_gsg)thought of using SessionDeleteQueueMessage , But this event is not generated if the subscriber times out.
-
4. Re: Multiple Issues with Interceptor.
clebert.suconic Oct 29, 2010 4:13 PM (in response to rahul_gsg)The Consumer is unique with ChannelD + consumerID
A channel can have multiple consumers, each consumer will start with 0 on a given ChannelID.
-
5. Re: Multiple Issues with Interceptor.
rahul_gsg Oct 30, 2010 1:13 AM (in response to clebert.suconic)Hi Clebert ,
With REST pull subscriptions for a Topic, I see the CosumerID always shown as 0 in the interceptors. However as you said the combination of ChannelD + consumerID is always unique {ChannelD is always unique} . Once a particular subscription is closed , I see the HornetQ making use of the same channelID again for new subscriptions.
I have checked this with multiple subscriptions from different IPAddress each.
With this can I safely assume that at a given point of time , I can uniquely identify an un-subscription based on only ChannelD + consumerID across the topics/queues in the system?