|  | 
 
  
    | RSS Feed - WebSphere MQ Support | RSS Feed - Message Broker Support |  
 
  
	|    |  |  
  
	| Will the expired message, trigger application? | « View previous topic :: View next topic » |  
  	| 
		
		
		  | Author | Message |  
		  | nethaji | 
			  
				|  Posted: Wed Jul 25, 2001 6:07 am    Post subject: |   |  |  
		  |  Apprentice
 
 
 Joined: 23 Jul 2001Posts: 26
 Location: Virginia
 
 | 
			  
				| HI all, 
 I am issueing a mqput with expiry (for 3 minute) on a remote queue. This particular messgae has to trigger an application once it reaches there by time. My doubt is
 1. if it gets expired inbetween will it go reach the destination queue??
 2. if it reaches (after the expiry time) will it trigger the application.
 
 I am asking this because I read somewhere that the expired message will be discarded only at the time of mqget???
 
 The Quote from MQseries redbook:
 1.After a message’s expiry time has elapsed, it becomes eligible to be discarded by
 the queue manager. In the current implementations, the message is discarded when a browse or nonbrowse MQGET call occurs that would have returned the message
 had it not already expired.
 
 Regards,
 subash
 
 [ This Message was edited by: nethaji on 2001-07-25 07:09 ]
 |  |  
		  | Back to top |  |  
		  |  |  
		  | kolban | 
			  
				|  Posted: Wed Jul 25, 2001 11:10 am    Post subject: |   |  |  
		  |  Grand Master
 
 
 Joined: 22 May 2001Posts: 1072
 Location: Fort Worth, TX, USA
 
 | 
			  
				| If a message is put to a remote queue through a local queue manager, it transiently sits on the local queue manager's transmission queue waiting its turn to be sent down the channel.  If it expires while on the transmission queue, it will never be sent to the remote system and hence never arrive or cause a trigger. |  |  
		  | Back to top |  |  
		  |  |  
		  | bduncan | 
			  
				|  Posted: Wed Jul 25, 2001 11:36 am    Post subject: |   |  |  
		  | Padawan
 
 
 Joined: 11 Apr 2001Posts: 1554
 Location: Silicon Valley
 
 | 
			  
				| That is correct, and to add to what you said, the time a message spends actually in transit across the network does not count towards its expiry. The only way it will get sent across the channel is if it hasn't expired, and once it arrives at the destination queue manager, it still cannot be expired.
 Therefore your trigger should always occur, and it will only occur if the message has not yet expired.
 Of course there is no guarantee that by the time the trigger monitor launches your triggered application that the message will still be unexpired, so you might do a MQGET and not get anything, even though the application was triggered...
 
 
 _________________
 Brandon Duncan
 IBM Certified MQSeries Specialist
 MQSeries.net forum moderator
 |  |  
		  | 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
 
 |  |  |  |