Stopping active subscribers for non-durable subscriptions

Use this task to stop active non-durable subscribers. For stopping active non-durable subscribers created by a standalone application or MDB, we need to stop the application. Once the subscription application is stopped, the non-durable subscription is removed automatically.

Tasks

1. Start the administrative console to list the non-durable subscriptions.

2. 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.

3. Use the client identifier naming convention to identify the application assigned to the client identifier.
4. List the applications that have active consumers for the shared non-durable subscription. In the navigation pane of the administrative console, click...

           Applications -> Application Types -> WebSphere enterprise applications.

5. In the console pane, select the check box next to the name of each application to stop.

6. Click Stop.

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.