Administering 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.
About this task
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.
- clientID
- The client identifier used to associate a connection and its objects with the messages maintained for applications (as clients of the JMS provider). You should use a naming convention that helps you identify the applications, in case you 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.