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:
The
server_name-durableSubscriptions.ser file in the
WAS_HOME/temp directory is used by the messaging service to keep track of durable subscriptions for message-driven beans. If you uninstall an application that contains a message-driven bean, this file is used to unsubscribe the durable subscription. If you have to delete the
WAS_HOME/temp directory or other files in it, ensure that you preserve this file.
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.