10-12 Configuring and Managing JMS for Oracle WebLogic Server
■
Section 10.5.6, Order of Precedence for Boot-time Pause and Resume of Message Operations
■
Section 10.5.7, Security
10.5.1 Definition of Message Production, Insertion, and Consumption
There are several operations performed on messages on a destination:
■
Messages are produced when a producer creates and sends a new message to that destination.
■
Messages are inserted as a result of in-flight work completion, as when a message is made available upon commitment of a transaction or when a message scheduled
to be made available after a delay is made available on a destination.
■
Messages are consumed when they are removed from the destination. You can pause and resume any or all of these operations either at boot time or during
runtime, as described in the sections below.
10.5.1.1 Pause and Resume Logging
When message production, insertion, or consumption on a destination is successfully paused or resumed either at boot time or at runtime, a message is added to the
server log to indicate the same. In the event of failure to pause or resume message production, insertion, or consumption on a destination, the appropriate
errorexceptions are logged.
10.5.2 Production Pause and Production Resume
When a JMS destination is paused for production, new and existing producers attached to that destination are unable to produce new messages for that destination.
A producer that attempts to send a message to a paused destination receives an exception that indicates that the destination is paused. When a destination is resumed
from production pause, production of new messages is allowed again. Pausing message production does not prevent the insertion of messages that are the result
in-flight work.
10.5.2.1 Pausing and Resuming Production at Boot-time
You can pause or resume production 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 production-paused-at-startup, the next time you boot the server, message production activities will be disallowed for the
specified destinations until you explicitly change the state to production enabled for that destination. If you configure production to resume, the next time you boot the
server, message production activities will be allowed on the specified destinations until the state is explicitly changed to production paused for that destination.
For more information about pausing and resuming message production at boot-time using the Administration console, see the following sources in the Oracle WebLogic
Server Administration Console Help:
■
Pause JMS server message operations on restart
Note: For an explanation of what constitutes in-flight work, see
Section 10.5.5, Definition of In-Flight Work.
Troubleshooting WebLogic JMS 10-13
■
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.2.2 Pausing and Resuming Production at Runtime
You can pause or resume production during runtime for all the destinations targeted 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.
For more information about pausing and resuming production 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.2.3 Production Pause and Resume and Distributed Destinations
