WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage messaging with the default messaging provider > Configure resources for the default messaging provider

Enable a provider to stream messages to cloned durable subscriptions

Use this task to enable a provider to stream messages to consumers ahead of their message requests. This is most often used by publish/subscribe consumers to provide a performance enhancement. To indicate that a provider must stream messages to consumers, we can set the Read ahead property to Enabled. This property can be set on a connection factory to specify the behavior for all connections created using that connection factory. The property can also be set on JMS topics, to enable different behavior when sending messages to different JMS topics from the same connection.

You are recommended to leave this property set to Default, which enables the messaging provider to decide whether it should stream messages to consumers. The messaging provider makes this decision based on the environment in which the durable subscriber is running. You should only set this property to enable message streaming if you are sure that a durable subscription is used by only one consumer at a time.

Messages that are streamed to the consumer but are not consumed before the consumer disconnects are unlocked when the consumer closes. Only then do those messages become available for consumption by other consumers.

To force the messaging provider to stream messages to cloned durable subscriptions, use the dmgr console to complete the following steps to change the connection factory:

  1. Display the JMS connection factory; for example, as described in Configure a unified connection factory for the default messaging provider. All clones of a durable subscriber use the same JMS connection factory.

  2. Set the Read ahead property to Enabled.

  3. Click OK.

  4. Save your changes to the master configuration.


+

Search Tips   |   Advanced Search