Use this task to enable applications to change a cloned durable
subscription. This task enables applications to connect to an existing cloned
durable subscription, and to specify parameters that differ from those that
were used to create the existing subscription.
About this task
When an application connects to an existing durable subscription,
but specifies parameters that differ from those that were used to create the
existing subscription, the subscription is deleted then recreated with
the new parameters. A durable subscription can be changed in this way
only when it has no active consumers.
Note: 傳訊服務利用 WAS_HOME/temp 目錄中的 server_name-durableSubscriptions.ser 檔來追蹤訊息驅動 Bean 的可延續訂閱。
如果您解除安裝包含訊息驅動 Bean 的應用程式,則使用這個檔案來取消訂閱可延續的訂閱。如果您必須刪除 WAS_HOME/temp 目錄或其中的其他檔案,請務必保留這個檔案。
To
stop active subscribers for one or more durable subscriptions, complete the
following steps:
Procedure
- Use the administrative console to list the durable subscriptions
- From the list, identify the client identifier of the durable subscription. The name column lists the unique subscription name for each durable
subscription, in the form clientID##subName where:
- clientID
- The client identifier used to associate a connection and its objects with
the messages maintained for the client by the JMS provider.
- subName
- The name used to uniquely identify a durable subscription within a given
client identifier.
- Use your client identifier naming convention to identify the application
assigned to the client identifier.
- List the applications that have active consumers for the durable
subscription. In the navigation pane of the administrative console,
click .
- In the console pane, select the check box next to the name of each
application that you want to stop.
- Click Stop
Results
This stops the active consumers created by the applications, so applications
can reconnect to the durable subscriptions with different parameters from
those that were used to create the previous subscriptions.