| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message Backlogs in MQ 6.0.2 with Cluster Manager |
« View previous topic :: View next topic » |
| Author |
Message
|
| rahoor |
 Posted: Mon Aug 13, 2007 11:35 am Post subject: Message Backlogs in MQ 6.0.2 with Cluster Manager |
 |
|
Apprentice
Joined: 21 Jul 2003
Posts: 34
|
I sure hope you can shed some light on this. It has been ongoing for quite some time. We have been pursuing several other probe IDs, but this one appears to be unique to the host having the issue:
| Quote: |
SunOS myServer 5.8 Generic_117350-29 sun4u sparc SUNW,Sun-Fire-V490
Name: WebSphere MQ
Version: 6.0.2.0
CMVC level: p600-200-060921
BuildType: IKAP - (Production) |
We periodically get an FDC which leads to a backlog of messages in our clustered queues.
This only occurs on MQ 6.0 queue managers and not MQ 5.3 CSD13 queue managers. This probe ID shows up as being patched in 5.3 via IY92711. And I do not see this patch in MQ 6.0, so I assume it became a part of the 6.0 release.
Has anyone else run into this issue and what other steps if any, other than opening a PMR do we have to diagnose further?
With Many thanks...
| Quote: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Friday August 10 14:13:11 EDT 2007 |
| Host Name :- myServer (SunOS 5. |
| PIDS :- 5724H7203 |
| LVLS :- 6.0.2.0 |
| Product Long Name :- WebSphere MQ for Solaris (SPARC platform) |
| Vendor :- IBM |
| Probe Id :- RM220005 |
| Application Name :- MQM |
| Component :- rrmRepository |
| SCCS Info :- cmd/remote/amqrrmfa.c, 1.414.1.19 |
| Line Number :- 2821 |
| Build Date :- Sep 21 2006 |
| CMVC level :- p600-200-060921 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000103 (pdsunmq) |
| Program Name :- amqrrmfa |
| Addressing mode :- 64-bit |
| Process :- 8747 |
| Thread :- 1 |
| QueueManager :- ******** |
| ConnId(1) IPCC :- 6 |
| ConnId(2) QM :- 10 |
| Major Errorcode :- rrcE_MQGET_FAILED |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9510 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9510: Messages cannot be retrieved from a queue. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+ |
Last edited by rahoor on Mon Aug 13, 2007 12:39 pm; edited 1 time in total |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Aug 13, 2007 11:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There should be a corresponding AMQ9510 message in AMQERR01.LOG that coincides with the FDC being thrown.
This should tell you which queue, and what the reason code was.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rahoor |
| Posted: Mon Aug 13, 2007 11:56 am Post subject: |
|
|
Apprentice
Joined: 21 Jul 2003
Posts: 34
|
| jefflowrey wrote: |
There should be a corresponding AMQ9510 message in AMQERR01.LOG that coincides with the FDC being thrown.
This should tell you which queue, and what the reason code was. |
I did not find any close to the time the error occurred, the latest occurs 10 hours earlier. I did not mention, this is a linear logging system and periodically the un needed log files are zipped. I have verified that the ones needed according to log not being zipped.
| Quote: |
----- amqphrea.c : 80 ---------------------------------------------------------
08/10/07 02:13:05 PM - Process(8751.1) User(sunmq) Program(runmqchi)
AMQ9510: Messages cannot be retrieved from a queue.
EXPLANATION:
The attempt to get messages from queue 'SYSTEM.CHANNEL.INITQ' on queue manager
'MYAPP01' failed with reason code 2195.
ACTION:
If the reason code indicates a conversion problem, for example
MQRC_SOURCE_CCSID_ERROR, remove the message(s) from the queue. Otherwise,
ensure that the required queue is available and operational.
----- amqrrmfa.c : 33109 ------------------------------------------------------
08/10/07 02:13:11 PM - Process(8747.1) User(sunmq) Program(amqrrmfa)
AMQ9510: Messages cannot be retrieved from a queue.
EXPLANATION:
The attempt to get messages from queue 'SYSTEM.CLUSTER.REPOSITORY.QUEUE' on
queue manager 'MYAPP01' failed with reason code 2009.
ACTION:
If the reason code indicates a conversion problem, for example
MQRC_SOURCE_CCSID_ERROR, remove the message(s) from the queue. Otherwise,
ensure that the required queue is available and operational. |
MQRC_UNEXPECTED_ERROR 2195 and
2009 is MQRC_CONNECTION_BROKEN.
Last edited by rahoor on Mon Aug 13, 2007 12:43 pm; edited 1 time in total |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Aug 13, 2007 12:02 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
AMQERR logs should not be affected by linear or circular logging... they're error logs, not transaction logs.
Also, they're circular in nature and there are only ever three of them.
That 2195 is disturbing. One wouldn't expect that to occur on that queue. The same, actually, with 2009.
I would open a PMR.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rahoor |
| Posted: Mon Aug 13, 2007 12:15 pm Post subject: |
|
|
Apprentice
Joined: 21 Jul 2003
Posts: 34
|
| Thanks, I will and update all on outcome here. |
|
| Back to top |
|
|
| rahoor |
| Posted: Tue Aug 14, 2007 11:02 am Post subject: |
|
|
Apprentice
Joined: 21 Jul 2003
Posts: 34
|
| rahoor wrote: |
| Thanks, I will and update all on outcome here. |
Here is an update...
As it turns out, the following probe IDS happen together, on the Sun Solaris OS with this issue:
AT040010
RM220005
*XC130003
*XC130004
*XC267011
XC338001
*XY017001
*ZL000028
ZL043050
ZL043105
ZT012001
ZX005025
ZX092016
ZX103020
So the one probe ID that appears to be unique, is actually a member of a set of FDCs generated when something goes wrong and is usually among the first few to occur. The ones referenced with an asterix in front are reportedly fixed.
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27007069
So we are going to see if the update to 6.0.2.2 is going to remedy most or all of these, in the near future. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
