2053 = Queue full

-Will

At 11:02 AM 5/31/2002 +0530, Vivek Vhatkar wrote:

>Hi ,
>I am facing the following error.
>I am not able to understand it.
>Could u pls. help me with the Reason 2053.
>
>Thanks,
>Vivek.
>
>Event Type: Warning
>Event Source: MQSeries
>Event Category: None
>Event ID: 5858
>Date:  5/30/2002
>Time:  2:46:59 PM
>User:  N/A
>Computer: MQSERVER
>Description:
>Broker could not send publication to subscriber queue.
>
>A failure has occurred sending a publication to subscriber queue
>(SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE                ) at queue manager
>(CashinQManager                                  ) for reason 2053. The
>broker configuration options prevent it from recovering from this failure
>by discarding the publication or by sending it to the dead-letter queue.
>Instead the broker will back out the unit of work under which the
>publication is being sent and retry the failing command message a fixed
>number of times.  If the problem still persists, the broker will then
>attempt to recover by failing the command message with a negative reply
>message.  If the issuer of the command did not request negative replies,
>the broker will either discard or send to the dead-letter queue the
>failing command message.  If the broker configuration options prevent
>this, the broker will restart the affected stream, which will reprocess
>the failing command message again.  This behavior will be repeated until
>such time as the failure is resolved.  During this time the stream will be
>unable to process further publications or subscriptions.
>
>Usually the failure will be due to a transient resource problem, for
>example, the subscriber queue, or an intermediate transmission queue,
>becoming full. Use reason code 2053 to determine what remedial action is
>required.  If the problem persists for a long time, you will notice the
>stream being continually restarted by the broker.  Evidence of this
>occurring will be a large number of AMQ5820 messages, indicating stream
>restart, being written to the error logs. In such circumstances, manual
>intervention will be required to allow the broker to dispose of the
>failing publication.  To do this, you will need to end the broker using
>the endmqbrk command and restart it with appropriate disposition options.
>This will allow the publication to be sent to the rest of the subscribers,
>while allowing the broker to discard or send to the dead-letter queue the
>publication that could not be sent.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Reply via email to