Valid points all.
 How much worse is that than sending messages to the wrong queue and having that application destroy them as  unrecognized spam?

                                                             


"Christopher Fryett" <[EMAIL PROTECTED]>
Sent by: "MQSeries List" <[email protected]>

05/20/2005 03:47 PM
Please respond to "MQSeries List"

       
        To:        [email protected]
        cc:        
        Subject:        Re: 'Black Hole' queue




One of the problems you encounter with "black hole" philosophies is it is a
dumping ground for the unused and worthless items hanging around.  Then
again sometimes the "black hole" will suck up something you never intended
to occur either.  Having such a feature or capability can create more
problems then a simple trigger program or fallout queue, because the
unskilled or even the skilled could configure a queue or queues incorrectly
and then who is to blame.  Not IBM, but I sense if the problem occurred
where it wiped out a reasonably number of $$$$ messages someone will be
screaming at IBM along with the person who accidentially configured the
queue(s).

If the application team must dump messages and they are not to stick around
then put the expiry time on it.  Even if it is for 'x' number of hours that
should provide enough time to recover them if someone should realize they
made a mistake.  Personally if they made the mistake there are bigger issues
then dumping a valid message.

If a "black hole" queue exist could it affect the logging of messages?  If
it is not a performance issue is there criterias for placing messages there.
 Who's fault is it if the queue is not created correctly, and when someone
says "MQ lost my message".  Did the "black hole" queue lose it or should it
be stated the application lost it ultimitaly because they pointed to the
"black hole" queue instead of the "make me money" queue.

Although there are a lot of skilled people out there putting in place an
"abyss of death" capability will only add to the problem not the solution.
Someone will make a mistake major or minor and if it is large enough IBM
will ultimately be publically hit.  Plus if you need a "black hole"
functionality have an application redirect the data to /dev/null or its
comparison.

Chris




>From: [EMAIL PROTECTED]
>Reply-To: MQSeries List <[email protected]>
>To: [email protected]
>Subject: 'Black Hole' queue
>Date: Thu, 19 May 2005 14:38:06 -0400
>
>If IBM could provide in WMQ a special type of queue, sort of a 'black
>hole' queue where messages can be sent for discard, would there be support
>for such an object out in the community? A possible use for such a queue
>would be a destination for test messages when the pickup process is not
>ready.
>The information contained in this message may be CONFIDENTIAL and is for
>the
>intended addressee only.  Any unauthorized use, dissemination of the
>information, or copying of this message is prohibited.  If you are not the
>intended addressee, please notify the sender immediately and delete this
>message.
>
>Instructions for managing your mailing list subscription are provided in
>the Listserv General Users Guide available at http://www.lsoft.com
>Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html




The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message.

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Reply via email to