You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by nicolasfranck <ni...@ugent.be> on 2014/07/27 18:37:21 UTC
preconfigure subscription names for durable topics
For durable topics, the subscriber needs to send its client-id
and subscriptionName. That way, when the subscriber stops, and restarts,
activemq will not only send the new messages, but also those messages
it missed during its absence.
But that requires an initial subscription with its client-id!
Is it possible to add those named subscriptions upon
startup? That way activemq has knowledge of future
subscriptions.
e.g. the messages are tasks, meant to be executed in order.
when not acknowledged, they need to be re-executed.
one cannot assume that the subscribers are up prior before
the messages are sent.
--
View this message in context: http://activemq.2283324.n4.nabble.com/preconfigure-subscription-names-for-durable-topics-tp4683721.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: preconfigure subscription names for durable topics
Posted by Timothy Bish <ta...@gmail.com>.
On 07/27/2014 12:37 PM, nicolasfranck wrote:
> For durable topics, the subscriber needs to send its client-id
> and subscriptionName. That way, when the subscriber stops, and restarts,
> activemq will not only send the new messages, but also those messages
> it missed during its absence.
>
> But that requires an initial subscription with its client-id!
> Is it possible to add those named subscriptions upon
> startup? That way activemq has knowledge of future
> subscriptions.
>
> e.g. the messages are tasks, meant to be executed in order.
> when not acknowledged, they need to be re-executed.
>
> one cannot assume that the subscribers are up prior before
> the messages are sent.
>
>
>
>
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/preconfigure-subscription-names-for-durable-topics-tp4683721.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
You could try using Virtual Topics and static configured destinations to
ensure the right queues are created on startup if not already present
from a previous run.
http://activemq.apache.org/virtual-destinations.html
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/