Use this task to stop active non-durable subscribers. For stopping active non-durable
subscribers created by a standalone application or MDB, you need to stop the application. Once the
subscription application is stopped, the non-durable subscription is removed automatically.
Procedure
- Use the administrative console to list the
non-durable subscriptions.
- From the list, identify the client identifier of the shared non-durable subscription. The name column lists the unique subscription name for each shared non-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 shared non-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 shared non-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 non-durable subscriptions with different parameters from those that were used to create the
previous subscriptions.