Pausing and Resuming Consumption at Boot-time Pausing and Resuming Consumption at Runtime

Troubleshooting WebLogic JMS 10-15

10.5.3.3 Insertion Pause and Resume and Distributed Destination

If a member destination is paused for insertion, that member destination will not be considered for message forwarding. Messages will be steered away to other member destinations that are available for insertion.

10.5.3.4 Insertion Pause and Resume and JMS Connection StopStart

Stopping or starting a JMS Connection has no effect on the insertion pause or insertion resume state of a destination.

10.5.4 Consumption Pause and Consumption Resume

When a JMS destination is paused for consumption, messages on that destination are not available for consumption. When the destination is resumed from consumption pause, both new and existing consumers attached to that destination are allowed to consume messages on the destination again. When the destination is paused for consumption, the destinations state is marked as consumption paused and all new, synchronous receive operations will block until consumption is resumed and there are messages available for consumption. All synchronous receive with blocking time-out operations will block for the specified length of time. Messages will not be delivered to synchronous consumers attached to that destination while the destination is paused for consumption. After a successful consumption pause operation, the user has to explicitly resume the destination to allow consume operations on that destination.

10.5.4.1 Pausing and Resuming Consumption at Boot-time

You can pause or resume consumption effective at boot-time for all the destinations on a JMS server, for a group of destinations that point to the same JMS template, or for individual destinations. If you configure consumption-paused-at-startup, the next time you boot the server, message consumption activities will be disallowed on the specified destinations until you explicitly change the state to consumption enabled for that destination. If you configure consumption to resume, the next time you boot the server, message consumption activities will be allowed on the specified destinations until the state is explicitly changed to consumption paused for that destination. For more information about pausing and resuming consumption at boot-time, see the following sources in the Oracle WebLogic Server Administration Console Help: ■ Pause JMS server message operations on restart ■ Pause topic message operations on server restart ■ Pause queue message operations on server restart ■ Pause JMS template message operations on server restart ■ Uniform distributed topics - pause message operations on server restart ■ Uniform distributed queues - pause message operations on server restart

10.5.4.2 Pausing and Resuming Consumption at Runtime

You can pause or resume consumption during runtime for all the destinations on a JMS server, for a group of destinations that point to the same JMS template, or for individual destinations. The most recent configuration change always take precedence, regardless of the level at which it is made JMS Server level, JMS Template level, or destination level. 10-16 Configuring and Managing JMS for Oracle WebLogic Server For more information about pausing and resuming consumption at runtime, see the following sources in the Oracle WebLogic Server Administration Console Help: ■ Pause JMS server message operations at runtime ■ Pause topic message operations at runtime ■ Pause queue message operations at runtime

10.5.4.3 Consumption Pause and Resume and Queue Browsers