Re: When (if) the dead letter queue gets full
Bill This has been on the list many times in different forms. If your channels have NPMSPEED (non-persistent message) set to fast and you are passing non-persistent messages with the below conditions, then they are gone. On the distributed side, you can set MRRTY and MRTMR to slow down the discard rate. Hope this helps you Frank -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Bill Anderson Sent: Monday, October 25, 2004 4:39 PM To: [EMAIL PROTECTED] Subject: When (if) the dead letter queue gets full I was asked the question what happens to messages when the dead letter queue fills up. So, I did some testing, and it seams that they are lost. Of course, with a max depth of 9 if you fill that sucker up, you have bigger problems on your hands than what happens next ;)~ To test, I set a local queue's max depth to 5, and set the max depth on the dead letter queue (on the same queue manager) to 5. From a remote queue manager I sent 15 messages across a sender channel. 5 messages were on the remote local queue as expected 5 messages were on the remote dead letter queue as expected. 5 messages could not be accounted for. The remote system logged the full queue condition for both the local and dead letter queues, but no hint was given as to what the qmgr did with the message. The local (sending) system logged the fact that the message could not be delivered to the remote and that an attempt was made to put it on the remote dead letter queue. However, when the remote dead letter queue filled up, no more errors relating to the problem were recorded. So, do the messages in such an (unlikely scenario) truly get tossed away? This e-mail contains information which is SITA - Company Confidential All sita.int addresses have changed to sita.aero [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive - This e-mail message and any attachments contain confidential information from Medco. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: When (if) the dead letter queue gets full
The thing is that you should not allow your dead letter queue to get so full, and yes the messages would get lost (based on my experience). if they are unable to put them somewhere else. Karla E. Kirkpatrick MQSeries, System Administrator for Special Events Phone: (919) 486-2213 e-mail: [EMAIL PROTECTED] Bill Anderson [EMAIL PROTECTED] Bill Anderson [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 10/25/2004 04:38 PM Please respond to MQSeries List To [EMAIL PROTECTED] cc Subject When (if) the dead letter queue gets full I was asked the question what happens to messages when the dead letter queue fills up. So, I did some testing, and it seams that they are lost. Of course, with a max depth of 9 if you fill that sucker up, you have bigger problems on your hands than what happens next ;)~ To test, I set a local queue's max depth to 5, and set the max depth on the dead letter queue (on the same queue manager) to 5. From a remote queue manager I sent 15 messages across a sender channel. 5 messages were on the remote local queue as expected 5 messages were on the remote dead letter queue as expected. 5 messages could not be accounted for. The remote system logged the full queue condition for both the local and dead letter queues, but no hint was given as to what the qmgr did with the message. The local (sending) system logged the fact that the message could not be delivered to the remote and that an attempt was made to put it on the remote dead letter queue. However, when the remote dead letter queue filled up, no more errors relating to the problem were recorded. So, do the messages in such an (unlikely scenario) truly get tossed away? This e-mail contains information which is SITA - Company Confidential All sita.int addresses have changed to sita.aero [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive inline: graycol.gifinline: pic10337.gifinline: ecblank.gif
Re: When (if) the dead letter queue gets full
If they are persistent messages, they won't get thrown away. They will stay on the transmission queue of the remote queue manager. If that fills up then you will get a queue-full condition when you try to put the message from your remote queue manager. - Bruce Giordano Bill Anderson [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Sent by: MQSeries List Subject: When (if) the dead letter queue gets full [EMAIL PROTECTED] Monday October 25, 2004 04:38 PM Please respond to MQSeries List I was asked the question what happens to messages when the dead letter queue fills up. So, I did some testing, and it seams that they are lost. Of course, with a max depth of 9 if you fill that sucker up, you have bigger problems on your hands than what happens next ;)~ To test, I set a local queue's max depth to 5, and set the max depth on the dead letter queue (on the same queue manager) to 5. From a remote queue manager I sent 15 messages across a sender channel. 5 messages were on the remote local queue as expected 5 messages were on the remote dead letter queue as expected. 5 messages could not be accounted for. The remote system logged the full queue condition for both the local and dead letter queues, but no hint was given as to what the qmgr did with the message. The local (sending) system logged the fact that the message could not be delivered to the remote and that an attempt was made to put it on the remote dead letter queue. However, when the remote dead letter queue filled up, no more errors relating to the problem were recorded. So, do the messages in such an (unlikely scenario) truly get tossed away? This e-mail contains information which is SITA - Company Confidential All sita.int addresses have changed to sita.aero [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: When (if) the dead letter queue gets full
The channel should have stopped, and the messages should still be sitting on the transmit queue. Bill Anderson [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 10/25/2004 03:38 PM Please respond to MQSeries List [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject When (if) the dead letter queue gets full I was asked the question what happens to messages when the dead letter queue fills up. So, I did some testing, and it seams that they are lost. Of course, with a max depth of 9 if you fill that sucker up, you have bigger problems on your hands than what happens next ;)~ To test, I set a local queue's max depth to 5, and set the max depth on the dead letter queue (on the same queue manager) to 5. From a remote queue manager I sent 15 messages across a sender channel. 5 messages were on the remote local queue as expected 5 messages were on the remote dead letter queue as expected. 5 messages could not be accounted for. The remote system logged the full queue condition for both the local and dead letter queues, but no hint was given as to what the qmgr did with the message. The local (sending) system logged the fact that the message could not be delivered to the remote and that an attempt was made to put it on the remote dead letter queue. However, when the remote dead letter queue filled up, no more errors relating to the problem were recorded. So, do the messages in such an (unlikely scenario) truly get tossed away? This e-mail contains information which is SITA - Company Confidential All sita.int addresses have changed to sita.aero [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: When (if) the dead letter queue gets full
Bill, What you really need to ask is, What happens when the page set that the DLQ is on fills up? Yes, they are really thrown away. Ò¿Ó Bob Juch Citigroup MQ Mainframe Support Team Weehawken, NJ 201-974-2147 mailto:[EMAIL PROTECTED] -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Bill Anderson Sent: Monday, October 25, 2004 4:39 PM To: [EMAIL PROTECTED] Subject: When (if) the dead letter queue gets full I was asked the question what happens to messages when the dead letter queue fills up. So, I did some testing, and it seams that they are lost. Of course, with a max depth of 9 if you fill that sucker up, you have bigger problems on your hands than what happens next ;)~ To test, I set a local queue's max depth to 5, and set the max depth on the dead letter queue (on the same queue manager) to 5. From a remote queue manager I sent 15 messages across a sender channel. 5 messages were on the remote local queue as expected 5 messages were on the remote dead letter queue as expected. 5 messages could not be accounted for. The remote system logged the full queue condition for both the local and dead letter queues, but no hint was given as to what the qmgr did with the message. The local (sending) system logged the fact that the message could not be delivered to the remote and that an attempt was made to put it on the remote dead letter queue. However, when the remote dead letter queue filled up, no more errors relating to the problem were recorded. So, do the messages in such an (unlikely scenario) truly get tossed away? This e-mail contains information which is SITA - Company Confidential All sita.int addresses have changed to sita.aero [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: When (if) the dead letter queue gets full
Bill, From your description, I'd assume the messages must be non-persistent. If the messages are non-persistent, and the channel parm NPMSPEED is set to FAST (the default) then the messages *are* thrown away. Note that if NPMSPEED is FAST and the messages are non-persistent, that a failure by the channel, or any problem with the DLQ (full, not defined, pageset is full, channel is not permitted to put to it, etc.) will cause the messages to be lost. If NPMSPEED is FAST, the channel gets the messages out of syncpoint, and once they have been gotten from the xmitq, they are gone. If the messages are persistent, or if NPMSPEED for the channel is NORMAL, then the messages are gotten in syncpoint, as part of a channel batch. If the receiving channel is unable to put them, the channel should stop and the messages should be returned to the xmitq. This is documented in the Intercommunication manual, though perhaps not as starkly as I've described it here.See the heading Fast, nonpersistent message in the Intercommunication manual. -Tom -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tom Schneider / IBM Global Services - MQSeries ASC (513) 274-4037 [EMAIL PROTECTED] -=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Bill Anderson [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 10/25/2004 04:38 PM Please respond to MQSeries List To [EMAIL PROTECTED] cc Subject When (if) the dead letter queue gets full I was asked the question what happens to messages when the dead letter queue fills up. So, I did some testing, and it seams that they are lost. Of course, with a max depth of 9 if you fill that sucker up, you have bigger problems on your hands than what happens next ;)~ To test, I set a local queue's max depth to 5, and set the max depth on the dead letter queue (on the same queue manager) to 5. From a remote queue manager I sent 15 messages across a sender channel. 5 messages were on the remote local queue as expected 5 messages were on the remote dead letter queue as expected. 5 messages could not be accounted for. The remote system logged the full queue condition for both the local and dead letter queues, but no hint was given as to what the qmgr did with the message. The local (sending) system logged the fact that the message could not be delivered to the remote and that an attempt was made to put it on the remote dead letter queue. However, when the remote dead letter queue filled up, no more errors relating to the problem were recorded. So, do the messages in such an (unlikely scenario) truly get tossed away? This e-mail contains information which is SITA - Company Confidential All sita.int addresses have changed to sita.aero [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: When (if) the dead letter queue gets full
Following this thread, I don't quite agree with anyone. I believe that: The disposition of the messages will depend on the value of NPMSPEED. If your channels are built with the default value of FAST, and you send non-persistent messages, then they will be discarded. If you send persistent messages, or if your channels are running with NPMSPEED(NORMAL) then your channel will go INDOUBT, and your messages will be in limbo. Your channels could stop and go to RETRY as well. The messages will not be discarded, and if you fix the problems they will show up on either the target queue or the DLQ. If you stop the channel and RESOLVE(BACKOUT) they will show up back on the tranmsission queue. Of course, I haven't actually built a test rig to confirm these beliefs, so I could be wrong. Regards, Neil Casey National Australia Bank Southern Star Technology WebSphere MQ Support 1/122 Lewis Rd Wantirna South office. +61 3 9886 2375 (x82375) mobile. +61 414 615 334 Juch, Robert [EMAIL PROTECTED] GROUP.COM To Sent by: MQSeries [EMAIL PROTECTED] List cc [EMAIL PROTECTED] n.AC.AT Subject Re: When (if) the dead letter queue gets full 26/10/2004 06:51 Please respond to MQSeries List [EMAIL PROTECTED] n.AC.AT Bill, What you really need to ask is, What happens when the page set that the DLQ is on fills up? Yes, they are really thrown away. Ò¿Ó Bob Juch Citigroup MQ Mainframe Support Team Weehawken, NJ 201-974-2147 mailto:[EMAIL PROTECTED] -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Bill Anderson Sent: Monday, October 25, 2004 4:39 PM To: [EMAIL PROTECTED] Subject: When (if) the dead letter queue gets full I was asked the question what happens to messages when the dead letter queue fills up. So, I did some testing, and it seams that they are lost. Of course, with a max depth of 9 if you fill that sucker up, you have bigger problems on your hands than what happens next ;)~ To test, I set a local queue's max depth to 5, and set the max depth on the dead letter queue (on the same queue manager) to 5. From a remote queue manager I sent 15 messages across a sender channel. 5 messages were on the remote local queue as expected 5 messages were on the remote dead letter queue as expected. 5 messages could not be accounted for. The remote system logged the full queue condition for both the local and dead letter queues, but no hint was given as to what the qmgr did with the message. The local (sending) system logged the fact that the message could not be delivered to the remote and that an attempt was made to put it on the remote dead letter queue. However, when the remote dead letter queue filled up, no more errors relating to the problem were recorded. So, do the messages in such an (unlikely scenario) truly get tossed away? This e-mail contains information which is SITA - Company Confidential All sita.int addresses have changed to sita.aero [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
