| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Inbound messages not reaching the queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| LouML |
 Posted: Thu Oct 06, 2011 4:50 am Post subject: Inbound messages not reaching the queue |
 |
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
We're running MQ Server 7.0.1.6 on a Solaris 10 Sparc server.
We have a Sender/Receiver pair of channels between us and an external company.
Our App PUTS a message to a QRemote that points to the QLocal on their end. They GET that message and PUT a Reply to a QRemote that PUTS the message to a QLocal on our end. Up until yesterday morning around 11:00 AM, this was working. Now, the App owner says he is not getting the replies.
I had the app owner try this while I monitor the channel. When he sends a message, I see our SDR channel start, followed quickly by our RCVR channel start. On the RCVR channel, I see the CURSEQNO and LSTSEQNO values increment. I also see the LSTMSGTI update.
However, no message appears on the QLocal, nor does anything go to the Dead Letter queue. No error log entries at all.
A Queue Status on the QLocal, shows no values at all. I even tried deleting the QLocal, to see if the Sender would receive an error, but we get the same result.
Anyone have any ideas where to look?
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Oct 06, 2011 4:57 am Post subject: Re: Inbound messages not reaching the queue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| LouML wrote: |
| Anyone have any ideas where to look? |
Get inhibit the reply queue. The app owner should get the relevant error when he tries to read the reply and you should see a message sitting there.
Check with the external company to see if any changes have been made to their app recently (i.e. about the time this started happening).
Check for any changes the external company have made regarding the expiry of their messages, code or configuration. See if anyone's changed the expiry time on the reply messages and thinks the value is represented in seconds (so they've set a 15 second expiry by moving 15 to the MQMD.Expiry field). This would mean it's all working fine, but the reply messages are expiring before they can be read off.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| LouML |
| Posted: Thu Oct 06, 2011 5:03 am Post subject: Re: Inbound messages not reaching the queue |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| Vitor wrote: |
| LouML wrote: |
| Anyone have any ideas where to look? |
Get inhibit the reply queue. The app owner should get the relevant error when he tries to read the reply and you should see a message sitting there.
Check with the external company to see if any changes have been made to their app recently (i.e. about the time this started happening).
Check for any changes the external company have made regarding the expiry of their messages, code or configuration. See if anyone's changed the expiry time on the reply messages and thinks the value is represented in seconds (so they've set a 15 second expiry by moving 15 to the MQMD.Expiry field). This would mean it's all working fine, but the reply messages are expiring before they can be read off. |
The QSTATUS of the QLocal on our end shows 0 for IPPROCS and OPPROCS, and QSTATUS TYPE(HANDLE) shows nothing, so I don't think anything is being consumed before I can check.
The app owner checked with the other side yesterday and they said no changes were made. I have a call in to them to confirm this.
Also, the fact that I deleted my QLocal and they don't get an error on a MQPUT to their QRemote is confusing.
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 06, 2011 5:08 am Post subject: Re: Inbound messages not reaching the queue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| LouML wrote: |
| Also, the fact that I deleted my QLocal and they don't get an error on a MQPUT to their QRemote is confusing. |
But tied with your other evidence does imply that they've changed something so that the messages are still being routed to your queue manager but are arriving on an unexpected queue.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Oct 06, 2011 5:18 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| LouML wrote: |
| ...Also, the fact that I deleted my QLocal and they don't get an error on a MQPUT to their QRemote is confusing... |
Why would you expect them to?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| LouML |
| Posted: Thu Oct 06, 2011 5:28 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| exerk wrote: |
| LouML wrote: |
| ...Also, the fact that I deleted my QLocal and they don't get an error on a MQPUT to their QRemote is confusing... |
Why would you expect them to? |
I thought they would get a 2085 Reason Code if the queue did not exist
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Oct 06, 2011 5:30 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| LouML wrote: |
| exerk wrote: |
| LouML wrote: |
| ...Also, the fact that I deleted my QLocal and they don't get an error on a MQPUT to their QRemote is confusing... |
Why would you expect them to? |
I thought they would get a 2085 Reason Code if the queue did not exist |
Their queue manager will have no sight of what's in your queue manager. Their QR is an address label as far as they are concerned, and will have no idea that the 'address' no longer exists. 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 06, 2011 5:36 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| LouML wrote: |
| I thought they would get a 2085 Reason Code if the queue did not exist |
No, their queue exists - it's the transmission queue the sender channel services that they're (indirectly) putting to and you didn't delete that.
You should have got a message in your queue manager's DLQ with a 2085 in it's header when the target queue doesn't exist your end.
WMQ 101 - see the loosely coupled architecture dance and spin.
_________________
Honesty is the best policy.
Insanity is the best defence.
Last edited by Vitor on Thu Oct 06, 2011 5:36 am; edited 1 time in total |
|
| Back to top |
|
|
| LouML |
| Posted: Thu Oct 06, 2011 5:36 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| exerk wrote: |
| LouML wrote: |
| exerk wrote: |
| LouML wrote: |
| ...Also, the fact that I deleted my QLocal and they don't get an error on a MQPUT to their QRemote is confusing... |
Why would you expect them to? |
I thought they would get a 2085 Reason Code if the queue did not exist |
Their queue manager will have no sight of what's in your queue manager. Their QR is an address label as far as they are concerned, and will have no idea that the 'address' no longer exists. |
Right, so it gets sent to my QM and if the QLocal is not found, gets put to my DEAD.LETTER queue. They have no knowledge of it. Still, my dead letter queue is empty
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Oct 06, 2011 5:49 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| LouML wrote: |
| Right, so it gets sent to my QM and if the QLocal is not found, gets put to my DEAD.LETTER queue. They have no knowledge of it. Still, my dead letter queue is empty |
As Vitor has stated, maybe expiry is being set now when it wasn't previously. What's the NPMSPEED on your RCVR channel? Does the MCAUSER in that channel not have authority to the DLQ and the destination queue exists and is full? Which assumes that the conditions for non-persistent message discard are met.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Oct 06, 2011 5:51 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Did you look at the error logs? Anything relevant there?
_________________
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 |
|
|
| LouML |
| Posted: Thu Oct 06, 2011 6:10 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
Hold on folks, this is another in a long series of app owner caused wild goose chases.
Now the app owner realizes that he is not using the QLocal in question, but in fact another. He said that this was setup by someone else.
After getting him to look at the correct queue, we tried another test. I confirmed that the messages are reaching the proper queue. The LGETTIME and LPUTTIME are correct. He still does not know what is happening with his messages, but at least I know he is consuming them.
Still waiting for an answer to my questions
1 - What made you think this was working before yesterday?
2 – Are you SURE you’ve not made any changes yesterday?
It’s in his court (where it should have been two days ago)
Thanks for the help and apologies for wasting everyone’s time. These people make me think I’m crazy. It’s tough being the only MQ Admin in a firm of over 5000.
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Oct 06, 2011 6:14 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| LouML wrote: |
| ...Thanks for the help and apologies for wasting everyone’s time... |
Not a waste of my time, it keeps my brain active.
| LouML wrote: |
| ...These people make me think I’m crazy... |
Surely you don't need them for that?
| LouML wrote: |
| ...It’s tough being the only MQ Admin in a firm of over 5000. |
In the land of the blind...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| LouML |
| Posted: Thu Oct 06, 2011 6:15 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| LouML wrote: |
Hold on folks, this is another in a long series of app owner caused wild goose chases.
Now the app owner realizes that he is not using the QLocal in question, but in fact another. He said that this was setup by someone else.
After getting him to look at the correct queue, we tried another test. I confirmed that the messages are reaching the proper queue. The LGETTIME and LPUTTIME are correct. He still does not know what is happening with his messages, but at least I know he is consuming them.
Still waiting for an answer to my questions
1 - What made you think this was working before yesterday?
2 – Are you SURE you’ve not made any changes yesterday?
It’s in his court (where it should have been two days ago)
Thanks for the help and apologies for wasting everyone’s time. These people make me think I’m crazy. It’s tough being the only MQ Admin in a firm of over 5000. |
UPDATE: App owner mentions a new deployment. I bet you can't guess when THAT took place.
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Oct 06, 2011 6:15 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| LouML wrote: |
| UPDATE: App owner mentions a new deployment. I bet you can't guess when THAT took place. |
So how is the trout fishing in Jersey these days? |
|
| Back to top |
|
|
|
|
|
  |
Goto page 1, 2 Next |
Page 1 of 2 |
|
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
|
|
|
|
