Pausing and Resuming Insertion at Boot Time Pausing and Resuming Insertion at Runtime

10-14 Configuring and Managing JMS for Oracle WebLogic Server The insertion pause operation supersedes the production pause operation. In other words, if the destination is currently in the production paused state, you can change it to the insertion paused state. You must explicitly resume a destination for message insertion to allow in-flight messages to appear on that destination. Successful completion of the insertion resume operation will change the state of the destination to insertion enabled and all the invisible in-flight messages will be made available.

10.5.3.1 Pausing and Resuming Insertion at Boot Time

You can pause or resume insertion 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 insertion-paused-at-startup, the next time you boot the server, message insertion and production activities will be disallowed on the specified destinations until you explicitly change the state to insertion enabled for that destination. If you configure insertion to resume, the next time you boot the server, message insertion activities will be allowed on the specified destinations until the state is explicitly changed to insertion paused for that destination. For more information about pausing and resuming message insertion 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.3.2 Pausing and Resuming Insertion at Runtime

You can pause or resume insertion 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. For more information about pausing and resuming insertion 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 Note: Because it is possible that this operation may be configured differently at each level i.e., the JMS Server level, the JMS template level, and the destination level, there is an established order of precedence. For more information, see Section 10.5.6, Order of Precedence for Boot-time Pause and Resume of Message Operations. Troubleshooting WebLogic JMS 10-15

10.5.3.3 Insertion Pause and Resume and Distributed Destination