USE_NEXT_MESSAGE_TO_DEQUEUE

Message and Mbox Processing Configuration

Note: This attribute value is only of benefit when there is a large buildup of messages in the Oracle AQs, for example, when a large number of messages are injected as part of a batch. If there is no buildup of messages in the Oracle AQs, there is no benefit to this setting.

Summary

This attribute defines the ways to purge vast quantities of cases in the Oracle AQs.

Applies To

This attribute can be set for the BG process.

Permissible Values

The attribute value must be one of the following:

Value

Meaning

0

To purge a large quantity of cases, the subsequent dequeue operations need to perform new queries for each message rather than to fetch the messages that are currently in the queue.

1

A large quantity of cases would be purged effectively by dequeuing messages, which are currently in the queue.

Default Value

This attribute is not defined automatically when you install or upgrade iProcess Engine. To use this attribute, you must explicitly assign a value to it.

Notes

When the value of the USE_NEXT_MESSAGE_TO_DEQUEUE attribute is set to 1, the dequeuing process loads all messages that are currently in the queue, and iterates through them as a single result set. In this way, it avoids performing any new queries for each message.

Any other messages outside the result set, even with higher internal message queue priorities, will not be picked up until all the messages in the result set have been dequeued.

See Also

None.