ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Is it Prob? SYSTEM.ADMIN.ACCOUNTI reached to MAXDEPTH

Post new topic  Reply to topic
 Is it Prob? SYSTEM.ADMIN.ACCOUNTI reached to MAXDEPTH « View previous topic :: View next topic » 
Author Message
asudhakar
PostPosted: Thu Feb 18, 2010 11:15 am    Post subject: Is it Prob? SYSTEM.ADMIN.ACCOUNTI reached to MAXDEPTH Reply with quote

Centurion

Joined: 12 May 2007
Posts: 116
Location: Bangalore

Hi All,

Pls find below information about System queue full..

___________________

My doubt : Is it issue ?. How can we proceed to reduce the depth of the queue.

Pls share your thoughts....
___________________

Observed system queue is full, pls find below information and suggest.

1. Log talking about SYSTEM.ADMIN.ACCOUNTING.QUEUE

---- amqkacca.c : 798 --------------------------------------------------------
02/17/10 19:06:04 - Process(9155.4054) User(mqm) Program(amqzlaa0_nd)
AMQ7315: Failed to put message to accounting queue. Reason(2)

EXPLANATION:
The attempt to put a messsage containing accounting data to the queue
SYSTEM.ADMIN.ACCOUNTING.QUEUE failed with reason code 2. The
message data has been discarded.
This error message will be written only once for attempts to put a message to
the queue as part of the same operation which fail for the same reason.
ACTION:
Ensure that the queue SYSTEM.ADMIN.ACCOUNTING.QUEUE is
available and operational.
----- amqkacca.c : 1657 -------------------------------------------------------
mqm@tsth5002:/var/mqm/qmgrs/TSTH5002/errors $ hostname



2. Verified the queue SYSTEM.ADMIN.ACCOUNTING.QUEUE it reached to maximum depth,

dis ql(SYSTEM.ADMIN.ACCOUNTING.QUEUE) curdepth maxdepth
1 : dis ql(SYSTEM.ADMIN.ACCOUNTING.QUEUE) curdepth maxdepth
AMQ8409: Display Queue details.
QUEUE(SYSTEM.ADMIN.ACCOUNTING.QUEUE) TYPE(QLOCAL)
CURDEPTH(3000) MAXDEPTH(3000)

3. Can find some messages in dlq. I am not sure. These messages belongs to App team

dis ql(QL.WMT.TSTH5002.DEAD.LETTER.QUEUE) curdepth maxdepth
5 : dis ql(QL.WMT.TSTH5002.DEAD.LETTER.QUEUE) curdepth maxdepth
AMQ8409: Display Queue details.
QUEUE(QL.WMT.TSTH5002.DEAD.LETTER.QUEUE)
TYPE(QLOCAL) CURDEPTH(9091)
MAXDEPTH(640000)

4. Some information about SYSTEM.ADMIN.ACCOUNTING.QUEUE ibm url

Additional information
The SYSTEM.ADMIN.ACCOUNTING.QUEUE and SYSTEM.ADMIN.STATISTICS.QUEUE are used by the monitoring feature introduced in WebSphere MQ V6. If monitoring is enabled, then accounting and statistics messages are placed on these queues. These messages occur at the end queue manager accounting and statistics interval, and also when the reset queue manager statistics command is issued.

The sample monitoring utility "amqsmon" can be used to get the messages from the queues and display the information contained in the messages.

If you notice that there are messages on these queues, that indicates that the queue manager accounting or the statistics monitoring feature of MQ has been enabled.

You can disable the queue manager accounting or the statistics monitoring features using MQSC commands. Example: ALTER QMGR ACCTQ(OFF)

Can I delete messages from the SYSTEM.ADMIN.ACCOUNTING.QUEUE and SYSTEM.ADMIN.STATISTICS.QUEUE?
Answer In general, you should not delete messages from any of the WebSphere MQ SYSTEM.* queues.

---
ACCTQ prop for QM :
dis qmgr acctq qmname
7 : dis qmgr acctq qmname
AMQ8408: Display Queue Manager details.
QMNAME(QMN) ACCTQ(ON)
_________________
WebSphere MQ, MB Support and Admin
Back to top
View user's profile Send private message Send e-mail
Vitor
PostPosted: Thu Feb 18, 2010 12:38 pm    Post subject: Re: Is it Prob? SYSTEM.ADMIN.ACCOUNTI reached to MAXDEPTH Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

asudhakar wrote:
My doubt : Is it issue ?. How can we proceed to reduce the depth of the queue.

Pls share your thoughts....


Well the obvious way to reduce the depth of the queue is to actually use the messages. It's pointless enabling these events if you're just going to let them pile up. AFAIK these events are disabled by default so someone on your site has deliberately enabled them, and we must presume to use the information for something. So in the short term increase maxdepth on that queue, in the medium term find out what should be reading them off but isn't.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Is it Prob? SYSTEM.ADMIN.ACCOUNTI reached to MAXDEPTH
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.