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 » WebSphere Message Broker (ACE) Support » Message Exipry - timer nodes

Post new topic  Reply to topic
 Message Exipry - timer nodes « View previous topic :: View next topic » 
Author Message
ANILK
PostPosted: Tue Jun 28, 2016 3:32 am    Post subject: Message Exipry - timer nodes Reply with quote

Acolyte

Joined: 01 May 2014
Posts: 61

Hi Friends,

I am developing a Retry mechanism flow with the help of Timeout control node.
we are reading messages from a Queue, and before we send those messages to another process , each message need to be put on sleep for 1 minute. with the help of TimeoutConrol node we can acheive this .

We need to Process all messages from the input Queue at the earliest , and After reading messages each message should wait only 1 minute before sending to another process .We will be having heavy message traffic to the input Queue

If we use Timeout control node in the flow, will it create performance issue , like it will read only 1 message and then wait for 1 minute to read another message from the Queue ? .message flow will be hanged for 1 minute ? or is it based on the additional instance which we configure for the flow.

-------------

2) We also consider to use Queue expiry property to have a expiry in the message level .


Which one is better option ? MQ level message expiry or Timeout control node .

Kindly share your advises .

Anil
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Jun 28, 2016 3:59 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

You need to reconsider this design.

Sleeping a full second for every message, regardless of whether it happens serially or paralellly, is an extreme performance impact in and of itself.

Particularly for 'heavy message traffic to the input queue".

Whatever the issue with the process you are calling, you need to fix that.

If you are attempting to write this flow as a patch for a problem with the downstream problem "until it can be fixed", then you need to raise this to as high a level of management as you can. " Until it can be fixed" never comes without a very large amount of pressure.

http://www.ibm.com/developerworks/websphere/library/techarticles/0603_schutz/0603_schutz.html
_________________
chmod -R ugo-wx /
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 » WebSphere Message Broker (ACE) Support » Message Exipry - timer nodes
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.