Consumption Pause and Resume and Queue Browsers Consumption Pause and Resume and Distributed Destination Consumption Pause and Resume and Message-Driven Beans Consumption Pause and Resume and JMS Connection StopStart

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

Queue Browsers are special type of consumers that are only allowed to peek into queue destinations. A browse operation on a destination paused for consumption is perfectly legitimate and is allowed.

10.5.4.4 Consumption Pause and Resume and Distributed Destination

Member destinations that are currently paused for consumption are not considered by the consumer load balancing algorithm.

10.5.4.5 Consumption Pause and Resume and Message-Driven Beans

Pausing a destination for consumption will prevent a message-driven bean MDB from getting any messages from its associated destination. This feature gives you more flexible control over the delivery of messages delivery to MDBs from the individual destination level as opposed to using connection startstop. In other words, if you use the consumption pauseresume feature, you can share the JMS connection among the multiple MDBs and still be able to prevent message delivery to selected MDBs by pausing the associated destination for consumption. For more information on using MDBs, see Configuring Suspension of Message Delivery During JMS Resource Outages inProgramming Message-Driven Beans for Oracle WebLogic Server.

10.5.4.6 Consumption Pause and Resume and JMS Connection StopStart

The JMS connection stopstart feature determines whether a consumer can successfully invoke the receive APIs or not. The consumption pauseresume feature on a destination determines whether the receive call will get any messages from the destination or not. Stopping or starting a consumers connection does not have any impact on the destinations consumption pause state. If the consumers connection is started from the stopped state, synchronous receive operations might block or time-out if the destination is currently paused for consumption. Asynchronous consumers will not receive any messages if the associated destination is in consumption paused state.

10.5.5 Definition of In-Flight Work