When an event queue is unavailable

If an event occurs when the event queue is not available, the event message is lost. For example, if you do not define an event queue for a category of event, all event messages for that category will be lost. The event messages are not, for example, saved on the dead-letter (undelivered-message) queue.

However, we can define the event queue as a remote queue. Then, if there is a problem on the remote system putting messages to the resolved queue, the event message will appear on the remote system's dead-letter queue.

An event queue might be unavailable for many different reasons including:

• The queue has not been defined.

• The queue has been deleted.

• The queue is full.

• The queue has been put-inhibited.

The absence of an event queue does not prevent the event from occurring. For example, after a performance event, the queue manager changes the queue attributes and resets the queue statistics. This happens whether the event message is put on the performance event queue or not.

In the case of configuration and command events the same is true again. In the absence of an event queue, an event message is not generated, however the command or call is executed regardless.