Administering durable subscriptions
Use the following tasks to display the 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 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 durable subscription, it is added to the
list that administrators can display and act upon by using the administrative
console. Each 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). You should use a naming convention that helps you identify the applications, in case you have to relate durable subscriptions to the associated applications for runtime administration. For more information about client identifiers, see section 4.3.2 of the JMS 1.1 specification.
- subName
- The JMS durable subscription name used to uniquely identify a durable subscription within a given client identifier. For more information about JMS durable subscription names, see section 6.11.1 of the JMS 1.1 specification.
For durable subscriptions created by message-driven beans, the subscription name value is set on the JMS activation specification. For other durable subscriptions, the value is set by the administrator on the JMS connection factory and by the JMS application on the createDurableSubscriber operation.
Note: 傳訊服務利用 WAS_HOME/temp 目錄中的 server_name-durableSubscriptions.ser 檔來追蹤訊息驅動 Bean 的可延續訂閱。
如果您解除安裝包含訊息驅動 Bean 的應用程式,則使用這個檔案來取消訂閱可延續的訂閱。如果您必須刪除 WAS_HOME/temp 目錄或其中的其他檔案,請務必保留這個檔案。