When a queue becomes full, exceptions are returned when
you attempt to produce a message to that queue. The most probable
reason for a queue filling up is that the producing application is
producing messages faster than they can be consumed by the consuming
application, although causes can also include broken communication
links or errors in the consuming application.
About this task
To investigate why a queue on a service integration bus is
full, complete the following steps:
Procedure
- Click ,
then click the name of the queue that is full.
-
Click [Related Items] Application resources topology,
then use the Application resources for this destination panel
to inspect the configuration of the applications and JMS resources
that are using the destination.
This panel can help you find the cause of the
problem by giving you a high level view of many relevant resources.
- Click ,
then on the Runtime tab review the value of
the Current message depth. If this value increases
steadily, the producing application is outpacing the consumer.
Note: If the destination has multiple queue points, or is mediated,
complete the following checks for each message point the message might
have been sent to or consumed from.
- Determine
which messaging engines the producing and consuming applications are
connected to.
- If the producing and consuming applications are connected
to different messaging engines, the messages are being routed through
a remote queue point. On the producer messaging engine, click Remote
queue points and then click the queue point that represents
the consumer queue point. Review the number of current outbound
messages. If the number of current messages is low, the problem does
not lie with the remote queue point; check that the consuming application
is started and is consuming messages without error. If the number
of current messages is approaching the high message threshold, complete
the following checks: