ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » poison messages

Post new topic  Reply to topic
 poison messages « View previous topic :: View next topic » 
Author Message
Mangesh1187
PostPosted: Wed Apr 03, 2013 10:17 am    Post subject: poison messages Reply with quote

Centurion

Joined: 23 Mar 2013
Posts: 116

Hi All,

Can any body give tell me some basic things about poision messages.
I heard the term , but dont know exactly how we can say , from many messagges, perticular message is poeion and rest of the messages are good.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Apr 03, 2013 11:29 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

A poison message is a message which can't be processed and because of insufficient handling by whatever's reading it is just allowed to roll back onto the queue is was read from. Because WMQ supplies messages FIFO this message then becomes the next available message to be read off where it fails again for the same reason it failed the first time. The cycle repeats over and over until someone takes manual action to prevent it.

If you have a single threaded application & a queue with pure FIFO then this message will stop the reading application as all other messages will stack up behind it, hence the term "poison" because it kills your system. If you have many reading threads other messages may manage to slip past it, or a queue based on priority may see higher priority messages skip above it.

It's still a bad thing as in the best possible case you have a thread spinning round and round burning CPU and getting nowhere.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Wed Apr 03, 2013 12:02 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

And its usually the content of the message that has something wrong with it that prevents your app from processing it and moving on to the next one. Since the bogus content of the message stays the same, you spin on the message trying over and over.

If you kept MQGETing a message and rolling it back simply because your app's backend database was not available, the behavior would look the same, but you typically wouldn't refer to that message as a 'poison' message.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
bruce2359
PostPosted: Wed Apr 03, 2013 12:08 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

A poison message is a message has been consumed from a queue inside a Unit of Work, but cannot be successfully processed by the consuming application; and, as a result, is MQBACKed out back into the same queue.

An example of a poison message would be an inventory inquiry request message arriving in a payroll time-card queue. The payroll application will not be able to process the (inventory) message.

Hope this helps.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
gbaddeley
PostPosted: Wed Apr 03, 2013 2:40 pm    Post subject: Reply with quote

Jedi Knight

Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia

Poisoned messages can be handled using the backout count and backout queue features of MQ. When the consumer app detects that a backout count has exceeded a certain threshold, it puts the message to a backout queue and commits. This effectively removes the poisoned message from the incoming message stream. An app or human can take remedial action on the messages in the backout queue at a future time.
_________________
Glenn
Back to top
View user's profile Send private message
Mangesh1187
PostPosted: Wed Apr 03, 2013 11:16 pm    Post subject: Reply with quote

Centurion

Joined: 23 Mar 2013
Posts: 116

Hi All,

Thanks for your replies.
It has really given me some insight about poison messages.

I will explore more on this base knowledge.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » poison messages
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.