Go to the Subscription Status workspace and check if the
subscription that uses the queue that triggered the situation is
durable. If it is a non-durable subscription, you can increase the
maximum depth of the subscription's destination queue.
If it is a durable subscription, right-click the row in the
Subscription Status workspace that represents the subscription and
link to the Application Connections workspace. If the Application
Connections workspace contains no data, the application is stopped
and messages sent to the queue by the publisher are not being
removed from the queue. Start the applicatoin to resolve the
problem. If the Application Connections workspace contains data,
then messages are probably not being processed fast enough by the
subscribing application. To resolve this problem, increase the
maximum depth of the subscription's destination queue.
|