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.
Pourquoi et quand exécuter cette tâche
The default messaging provider supports the use of non-durable subscriptions to topics. Un abonné peut ainsi recevoir une copie de tous les messages publiés dans un sujet, et même des messages publiés lorsqu'il est déconnecté du serveur.
If an application creates a non-durable subscription, it is added to the list that administrators
can display and act upon by 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
- Identificateur du client permettant d'associer une connexion et ses objets aux messages gérés pour les applications (comme clients du fournisseur JMS). 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.
- NomAbon
- 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.