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 » timeoutcontrol fileout and persistence

Post new topic  Reply to topic
 timeoutcontrol fileout and persistence « View previous topic :: View next topic » 
Author Message
paustin_ours
PostPosted: Fri May 24, 2013 6:50 pm    Post subject: timeoutcontrol fileout and persistence Reply with quote

Yatiri

Joined: 19 May 2004
Posts: 667
Location: columbus,oh
I will try to explain my scenario to the best i can.

first msg comes in i open a file and put the msg in the file and keep it open. Simutaneously i put a timeout control msg to triggger once at midhnight. So the file will be closed at midnight

only for first msg i send timeout i store filename in a queue which i get using mqget. timeout is count -1 and interval set to 1 day. Now the timeout triggers eeryday.

i set timeout to persistent and filename msg to persistent to avoid files stuck in mqsitransit directory.

it all works ok. But if i amke code change and re-deploy i want a brand new timeout message to kick off but this doesnt happen becuase i chcek filename queue and decide its not the first msg and i dont send new timeout.

is there a way i can send new timeouts only in the case of re-deploys and not in the case of broker/flow/eg stop/starts.?
Back to top
View user's profile Send private message Yahoo Messenger
kash3338
PostPosted: Fri May 24, 2013 10:20 pm    Post subject: Re: timeoutcontrol fileout and persistence Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
Firstly, its a bit not clear on your flow design. It would be better if you can explain us the skeleton of your message flow and then the functionality. But based on what I understood,

paustin_ours wrote:
But if i amke code change and re-deploy i want a brand new timeout message to kick off but this doesnt happen becuase i chcek filename queue and decide its not the first msg and i dont send new timeout.


Cant your clear the MQ Queue when you make changes to your code and re-deploy? When you change the code and re-deploy, it becomes a new release and hence you should be having the access to empty the old queue.

paustin_ours wrote:
is there a way i can send new timeouts only in the case of re-deploys and not in the case of broker/flow/eg stop/starts.?


Why do you want to send new timeouts only in case of re-deploy and why not in FLOW/EG/BROKER restart?

Anyways, you can achieve this by using a combination of a EXTERNAL variable and SHARED variable by storing the value of Deployment Time in your EXTERNAL variable at the time of deployment.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » timeoutcontrol fileout and persistence
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.