| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Dead Letter Handling |
« View previous topic :: View next topic » |
| Author |
Message
|
| sidhusaju |
 Posted: Wed May 16, 2007 2:54 am Post subject: Dead Letter Handling |
 |
|
Apprentice
Joined: 03 May 2007
Posts: 27
|
Hi,
Ur Questions are
On what conditions are you getting a bad message, are they specific to your application? And what do you want to do with bad message once the problem is resolved - throw it away, or re-process it?
As per my vb.net application, I want to keep the message in the DLQ if there is any exception (any type of MQexception thrown from vb.net appln)and wants the application to continue with the other message in the Queue. At the end of the Day I want to send these messages(messages in DLQ) as one .txt file each to the client through an email.
My requirements are
1) I Want to put the Message in to the original Queue when there is no exception and want to put the message to the Dead letter Queue when there is an exception(any kind of exception).
2) At the end of the day, I want to send all the messages in the DLQ to the respective clients.
Any help would be appreciated,
Regards,
Sajayan |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed May 16, 2007 3:03 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
No need to reinvent the wheel.
That's why there is a DLQ handler program.
The application should never post to the DLQ. Only the qmgr does.
If you need the app to post somewhere and require a DLQ like functionality have the app post to some Q that is not the qmgr's DLQ and add a DLQ header to the message it (the app) posts there.
You can then use the DLQ handler to process them, even if it is not the qmgr's DLQ....
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 16, 2007 3:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Do NOT start a new thread for each new question! It's almost as irritating as when you posted the same question in every forum! 
As you have already been advised (twice), if you want to keep unprocessable messages you need to define a queue, code your application to put them there in the event of any exception, then process them as you see fit at a later point - in your example email them to someone.
This is a straightforward "how do I" question adequately covered in the documentation. What have you tried to date? What happened when you tried it? What problems did you encounter (aside from finding the "post reply" button in this forum  )? What did you try to resolve them?
Write some code. Experiment. If you hit problems, try to fix them. If you can't, post. In a single forum if you'd be so good.
We're not designing and building your application. At least I'm not. Without a purchase order.
_________________
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
|
|
|
|
