WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

The consequences of changing durable subscriptions

This topic describes the consequences of applications that connect to an existing cloned durable subscription, but specify parameters that differ from those that were used to create the existing subscription.

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. In the basic case, there is only one active consumer at any time, so the application can change the durable subscription without affecting other subscribers. However, the situation is more complicated for cloned subscriptions.

A cloned durable subscription has multiple active subscribers, which are usually clones of a particular application.
Related tasks
Administering durable subscriptions
Listing subscriptions
Stopping active subscribers for durable subscriptions
Deleting durable subscriptions

Concept topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\concepts\cjo0012_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)