| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Sporadic Appearance of "!" Character in MQMD Field |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Mon Jul 07, 2003 8:32 am Post subject: |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
It cant hurt to recreate the QRemote. But I doubt that will fix it. If it was the problem, 100% of the messages would be screwed up.
If only 80% are hosed, then to me it points to something in the application putting the messages. Probably some conditional code that gets executed 80% of the time.
I gotta think if it was something wrong in the MQ infrastructure,
A. More of us would have seen the problem.
B. 100% of your messages going thru the particular queues and channels would be in error.
If you don't have some sort of monitoring tool in place that can capture all the MQMD info as it goes from queue to queue, than you will have to get creative and try and stop the message each step of the way to ID exactly where it is getting screwed up. Is this happening in production and or your test environment? If in test, change the qremote to a qlocal and have the app dump messages there. If all are good, then on to the next step. Put back the qremote, and stop the sender channel, so you can see the messages in the XMIT queue. And on and on till you find the problem.
Pain in the arse, but what else is there to do? I bet you find the problem in the app that puts the message.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| mcmags34 |
| Posted: Mon Jul 07, 2003 8:47 am Post subject: |
|
|
Novice
Joined: 02 May 2002
Posts: 14
Location: Philadelphia, PA
|
Great suggestions. I appreciate your insight.
The main reason why I have not taken your good advice to date is because this problem is happening from every application we run at our company, not just one or two (we're talking web site, IVR, internal customer service, EVERYTHING - and there's virtually nothing in common between them other than the queue manager they're using).
Also, the fields that are most often messed up are the DestQMgr and DestQ, neither of which can be supplied by an application since they're properties within the remote qdef.
One thing I do think I'll do is stop the channel on our development qmgr, which has the same problem. I'll let some messages build up and then see if any of them has the bad character in there.
Thanks again!  |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jul 07, 2003 8:55 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Wow, all apps, huh? So what is the common factor?
All the apps that put messages from QM1 to QM2?
Or are there some channels and/or Queue Remotes between the 2 QMs that never show the problem?
Do the messages going from QM1 to QM3 for instance have the same problem?
Or all the messages from all the apps on this server have issues?
Is it happening in DEV , QA, TEST and PRODUCTION?
If you log onto the box and use amqsput, does it get the same problem?
Did the problem just start? Was there an upgrade?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
