sole
>
> --
> James
> ---
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fusesource.com/
>
>
--
View this message in context:
http://www.nabble.com/Are-durable-topic-subscriptions-destroyed--tp22344211p22411405.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
2009/3/5 akuhtz :
>
> There is currently no code to unsubscribe a durable subscriber as Camel uses
> the XXMessageListenerContainer classes from the spring framework and inside
> the spring code there is no unsubscribe code. I solved this yesterday by
> making a copy of the (in my case) SimpleMessa
; need
>>>> to
>>>> specify both clientId and durableSubscriberName."
>>>> durableSubscriberName
>>>> does not work. The table below has the correct property:
>>>> durableSubscriptionName.
>>> Thanks for spotting this. Fixed the typo.
tml). The first paragraph
>>> under
>>> "Notes" states "If you wish to use durable topic subscriptions, you need
>>> to
>>> specify both clientId and durableSubscriberName." durableSubscriberName
>>> does not work. The table b
h clientId and durableSubscriberName." durableSubscriberName
>> does not work. The table below has the correct property:
>> durableSubscriptionName.
> Thanks for spotting this. Fixed the typo.
>
>
>> --
>> View this message in context:
>> ht
e." durableSubscriberName
> does not work. The table below has the correct property:
> durableSubscriptionName.
Thanks for spotting this. Fixed the typo.
> --
> View this message in context:
> http://www.nabble.com/Are-durable-topic-subscriptions-destroyed--tp22344211p22344211
to use durable topic subscriptions, you need to
specify both clientId and durableSubscriberName." durableSubscriberName
does not work. The table below has the correct property:
durableSubscriptionName.
--
View this message in context:
http://www.nabble.com/Are-durable-topic-subscriptions-d
