activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] Commented: (AMQ-3001) Ghost durable topic subscribers
Date Wed, 27 Oct 2010 09:14:00 GMT


Gary Tully commented on AMQ-3001:

When a durable is forwarded through a network a well known durable subscriber needs to be
created that can out live the original, so if there is a partition, there will be no loss
of messages for the networked durable.
They use the prefix,NC-DS, (network connector durable sub) prefix comprised of the the local
broker and destination physical name, see

The expectation is that the connection associated with the durable sub will change when the
same durable again subscribes, the point being that the nc-ds can outlive the new connection.

The dynamicOnly property of a network connector can controll whether the nc-ds is activated
on startup, when true, the NC-DS will only be activated when the original durable sub again
(dynamically) reconnects. With dynamicOnly=true, it is possible to miss messages when disconnected,
so it defaults to false.

The NC-DS-xx will only be deleted when the original durable sub unsubscribes.

> Ghost durable topic subscribers
> -------------------------------
>                 Key: AMQ-3001
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.1
>         Environment: Ubuntu 9.10
>            Reporter: James Green
>            Priority: Minor
> Listed on the Durable Topic Subscribers within the web interface I now have:
> Client ID: NC_ubuntu_inbound_blofeld
> Subscription Name: NC-DS_blofeld_Account.Requests
> Connection ID: ID:blofeld-37576-1288168498890-3:1
> I did have a subscription however it lacked a Client-ID, so it disconnected and I restarted
ActiveMQ. The result is shown above. There are allegedly no such connections listed on the
Connections page.
> No idea what NC or NC-DS mean! This is confusing at best.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message