Administer non-durable subscriptions
Use the following tasks to display the non-durable subscriptions that exist, to enable a subscription to be changed, or to delete a subscription.
The default messaging provider supports the use of non-durable subscriptions to topics. This enables a subscriber to receive a copy of all messages published to a topic, even messages published during periods of time when the subscriber is not connected to the server.
If an application creates a non-durable subscription, it is added to the list that administrators can display and act upon using the administrative console. Each non-durable subscription is created with a unique subscription identifier, _NON_DURABLE_NON_SHARED<number>. Each shared non-durable subscription is created with a unique subscription identifier, clientID##subName where:
- clientID
- The client identifier used to associate a connection and its objects with the messages maintained for applications (as clients of the JMS provider). We should use a naming convention that helps you identify the applications, in case we have to relate non-durable subscriptions to the associated applications for runtime administration. For more information about client identifiers, see section 6.1.2 of the JMS 2.0 specification.
- subName
- The JMS non-durable subscription name is used to uniquely identify a non-durable subscription within a given client identifier. For more information about JMS non-durable subscription names, see section 8.3.1 and 8.3.2 of the JMS 2.0 specification.
For non-durable subscriptions created by message-driven beans, the subscription name value is set on the JMS activation specification. For other non-durable subscriptions, the value is set by the administrator on the JMS connection factory and by the JMS application on the createSubscriber operation for non-durable and createSharedConsumer for shared non-durable.
Subtopics
- List non-durable subscriptions
Use this task to list the non-durable subscriptions that exist at runtime for a topic space.- Stopping active subscribers for non-durable subscriptions
Use this task to stop active non-durable subscribers. For stopping active non-durable subscribers created by a standalone application or MDB, we need to stop the application. Once the subscription application is stopped, the non-durable subscription is removed automatically.- Delete non-durable subscriptions
Use this task to delete a non-durable subscription.
List non-durable subscriptions Stopping active subscribers for non-durable subscriptions Deleting non-durable subscriptions