MQSeries.net :: View topic - How big can the MQ log file system can be?

rxm8778 · Posted: Thu Mar 26, 2009 6:12 am Post subject:

Bummer....

Evertime I get to troubleshoot something in MQ, it always feel I am like looking for a lost child at Disney World during peak hours. (millions of square feet, millions of children....) GGGrrrrrr....

With that said I think I may have a lead ....Please share your thoughts....

When I to take a look at my accounting and statistics data that stack up on SYSTEM.ADMIN.ACCOUNTING.QUEUE and SYSTEM.ADMIN.STATISTICS.QUEUE I would see the following on my accounting queue:

MonitoringType: QueueAccounting
QueueManager: 'XXXXXXX'
IntervalStartDate: '2009-03-14'
IntervalStartTime: '23.53.25'
IntervalEndDate: '2009-03-15'
IntervalEndTime: '00.23.29'
CommandLevel: 600
ConnectionId: x'414d51434d513734503030312020202049a63d1a2001b201'
SeqNumber: 811
ApplicationName: 'WebSphere MQ Client for Java'
ApplicationPid: 917748
ApplicationTid: 43
UserId: 'xxxxxxx'
ObjectCount: 1
QueueAccounting: 0
QueueName: 'XXXXXXX'
CreateDate: '2008-03-22'
CreateTime: '03.58.11'
QueueType: Predefined
QueueDefinitionType: Local
OpenCount: 0
OpenDate: '2009-02-26'
OpenTime:
OpenTime: '00.58.29'
CloseCount: 0
PutCount: [0, 0]
PutFailCount: 0
Put1Count: [0, 0]
Put1FailCount: 0
PutBytes: [0, 0]
PutMinBytes: [0, 0]
PutMaxBytes: [0, 0]
GetCount: [0, 0]
GetFailCount: 989
GetBytes: [0, 0]
GetMinBytes: [0, 0]
GetMaxBytes: [0, 0]
BrowseCount: [0, 454]
BrowseFailCount: 0
BrowseBytes: [0, 2741264]
BrowseMinBytes: [0, 0]
BrowseMaxBytes: [0, 37318]
GeneratedMsgCount: 0

I am guessing PutFailCount, Put1FailCount, GetFailCount would be some interesting metrics to look at and their count would increase if I am having issues... such as log file being full.
(note that the data above is not for the timeframe when I had the AMQ error)

What do you all think?

Any of you used these metrics to troubleshoot such issues? What are those fail metrics telling me and what causes their count to rise?