|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
XML Files are missing |
« View previous topic :: View next topic » |
Author |
Message
|
regonda |
Posted: Thu Feb 16, 2012 4:00 am Post subject: XML Files are missing |
|
|
 Apprentice
Joined: 08 Apr 2008 Posts: 43
|
Hello All,
we are running on WMB V6 for quite a long time now.
But recently, there seems to be an issue with one of the input queues.
All the XML files put in one input queue are missing, not sure where exactly they are going.. checked DLQ as well but didnt get any there..
We have about 10 input queue in our queue manager and all other input queue are working fine but the problem is only with one input queue..
P.S it was working fine earlier and no changes were made of late...
So not sure what exactly could be the reason for this...
Please let me know what could be the issue here...
Harish |
|
Back to top |
|
 |
Vitor |
Posted: Thu Feb 16, 2012 5:09 am Post subject: Re: XML Files are missing |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
regonda wrote: |
Please let me know what could be the issue here... |
Something (presumably a WMB flow) is consuming these messages, not producing the output for some reason (presumably code related) and not throwing any errors or diagnostic information (presumably for code reasons).
I'm assuming here that you've already satisfied yourself that the messages are being successfully put to the queue in question and that's they're not in a transmission queue somewhere.
When you say here have been no recent changes do you mean to all components in this design? Including the non-WMB, non-WMQ application that's generating this XML? Which could be generating subtly different XML that's not going through the flow correctly? Or not correctly trapping an error from the put? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
regonda |
Posted: Thu Feb 16, 2012 5:16 am Post subject: |
|
|
 Apprentice
Joined: 08 Apr 2008 Posts: 43
|
Hi Vitor,
I don't think this is due to Code errors as it was working fine earlier and also can confirm that the same code is working fine in other instances (i.e., development instance).
Yes, I mean no changes to ALL components...
Harish |
|
Back to top |
|
 |
regonda |
Posted: Thu Feb 16, 2012 5:24 am Post subject: |
|
|
 Apprentice
Joined: 08 Apr 2008 Posts: 43
|
Hi Vitor,
Not sure if the below helps you in identifying the issue, but would like to share this info with you..
when I'm giving the command 'ps -ef|grep' at command prompt, I'm getting the below
> ps -ef|grep <EG Name>
DataFlowEngine <Dev Broker> 99efbd75-1201-0000-0080-cb474e278af0 <EG Name> 0
DataFlowEngine <UAT Broker> 06d82fa0-1201-0000-0080-c2ed6b40560c <EG Name> 1
Here we will be able to see that Dev Broker's EG's status is showing as "0" (zero), but the UAT Broker's EG's status is shoing as "1"
So, could there be any problem with the EG??
Harish |
|
Back to top |
|
 |
Vitor |
Posted: Thu Feb 16, 2012 5:42 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
regonda wrote: |
Yes, I mean no changes to ALL components... |
Well clearly something's changed!
This is sounding more & more like a traditional game of "hunt the message". You've established they're being put, you've established they're not in the traget queue, you've established they're not in the DLQ. So now you need to grind through all the possible places they could go on their journey, with all the traditional steps. I start with these myself:
- If they're being put locally, use a trace to see the zero return code from the MQPUT call. If they're being put remotely, stop the channel to see the messages in the queue & examine the XMIT header to see where they're addressed to.
- Stop whatever's supposed to be reading the queue and make sure the IPPROCS count drops to zero. If it's not, something else is eating your messages & you can obtain the process id.
Other steps are equally valid & may be better. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
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
|
|
|
|