| Author |
Message
|
| mattfarney |
 Posted: Mon Oct 03, 2011 3:12 pm Post subject: Cluster DLQ behavior |
 |
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
Observed something that has me worried. I have a pair on intersecting clusters, some of which are my machines, and some are not.
My machines are Alpha, Beta, Gamma, Delta, and Epsilon where Alpha and Beta are full respositiories in the Greek cluster.
Alpha and Beta are also satellite QMs in another cluster consisting of Purple and Black, both of which are full repositories in the Colors cluster. There are probably more QMs here but I can't see them (nor do I need to).
Here's my what I saw:
Either Alpha or Beta generated a message destined for a local queue on Delta. There is only one copy of the this queue shared in the Greek cluster (and none in the Colors cluster).
We had some volume issues on the Delta and Epsilon QMs (same machine). When I was looking for outstanding issues and stranded traffic, I found the message showed up in the Dead Letter Queue.....on Purple.  [Technically, an email from their MQ contact told me.]
I cannot think of a single reason this could have occurred, that doesn't involve a problem inside MQ. 
-mf |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Mon Oct 03, 2011 3:34 pm Post subject: Re: Cluster DLQ behavior |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| mattfarney wrote: |
I cannot think of a single reason this could have occurred, that doesn't involve a problem inside MQ. |
What does the DLH tell you as to why the message is in the dead-letter queue?
From the DLH, what is/was the destination queue name? The destination queue manager name?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mattfarney |
| Posted: Mon Oct 03, 2011 4:35 pm Post subject: |
|
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
All I have is hex dump from the other system.
| Code: |
| 44 4C 48 20 01 00 00 00 27 08 |
Assuming I'm reading it correctly (Windows), the error is 2087 (0827) (RC2087): MQRC_UNKNOWN_REMOTE_Q_MGR.
This result makes sense for the Purple QM. It does not recognize Delta nor have anyway to get to him. The problem is the message should never have been delivered to Purple. There is absolutely no way Purple could have generated this traffic originally.
-mf |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Oct 03, 2011 5:59 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The DLH structure format is well-documented in the APR manual.
I repeat my request: From the DLH, what is/was the destination queue name? The destination queue manager name? Post the entire DLH here - all of it, not just the first few bytes.
You might want to look on ALPHA and BETA for definitions for the queue name in question. DISPLAY QCLUSTER. Post the queue definition here.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Oct 04, 2011 5:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Does the OP sound like a certification test question to anyone else?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 04, 2011 5:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| Does the OP sound like a certification test question to anyone else? |
Well yes (who has queue managers called that?) but there is that fragment of DLH.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Oct 04, 2011 6:16 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Yes, a fragment of a DLH - with no useful information, like destination queue and qmgr names.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 04, 2011 6:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| Yes, a fragment of a DLH - with no useful information, like destination queue and qmgr names. |
Well quite. My point was it does seem to be live data, the OP's been in here a while so has left certification late if so, and gives location as "Ohio" which means "obviously trustworthy".
Good queue manager names though. Perhaps that's a spin-off thread - "Interesting Queue Manager / Server Names I've Seen"...
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 04, 2011 6:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| Good queue manager names though. |
I suspect the names have been changed to protect the innocent from horrible naming standards. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 04, 2011 6:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Vitor wrote: |
| Good queue manager names though. |
I suspect the names have been changed to protect the innocent from horrible naming standards. |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 04, 2011 7:03 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| mqjeff wrote: |
| Vitor wrote: |
| Good queue manager names though. |
I suspect the names have been changed to protect the innocent from horrible naming standards. |
|
"My machines are XP4812TLM1, XP4957TLD1 and P48321N81809". |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Oct 04, 2011 7:35 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I'm fond of queue manager names taken from moons of Saturn.
The OP has provided no useful information to do meaningful problem determination. Amusing information perhaps, but not useful.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mattfarney |
| Posted: Tue Oct 04, 2011 9:04 am Post subject: |
|
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
I tried to generalize my names because my specific layout and object names aren't important to the discussion.
I'll have some time later today to post additional information. Sorry for the delay.
-mf |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 04, 2011 9:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mattfarney wrote: |
| I tried to generalize my names because my specific layout and object names aren't important to the discussion. |
I suspect your specific layout will be key to the discussion. Especially if (as I further suspect) it's not exactly what you think it is...
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Oct 04, 2011 9:40 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| mattfarney wrote: |
I tried to generalize my names because my specific layout and object names aren't important to the discussion.
I'll have some time later today to post additional information. Sorry for the delay.
-mf |
If you believe that technical and specific details are not important, then research the WMQ Intercommunications manual, and here, for a more general answer to the question: why would a message end up in a dead-letter queue?
A general layout is of little use in diagnosing exactly (not generally) why a specific message ended up in a specific dead-letter queue of a specific qmgr.
The ReasonCode, name of your queue and queue manager (from DLH) are exactly the data needed to begin problem determination. The definition that the creating application MQOPENed may provide other valuable clues.
Yes, the r/c 2085 is a clue. "My car won't start" is equally a clue, but provides no useful information for doing meaningful p-d. The usual response for both would be: what have you tried (looked at, tested, evaluated)? what were the results?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
