| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Using Timer node in Active-Active Environemt |
« View previous topic :: View next topic » |
| Author |
Message
|
| orman |
 Posted: Wed Feb 18, 2015 10:11 am Post subject: Using Timer node in Active-Active Environemt |
 |
|
Apprentice
Joined: 08 Aug 2013
Posts: 40
|
Hello all
What is the best practice for using Time nodes when I have more than one instance on run-time and I don't want just 1 instance to work at the time,
but in case of failure I want that will be a backup Broker that will work
What do use think ?
Last edited by orman on Fri Feb 20, 2015 2:09 am; edited 2 times in total |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Feb 18, 2015 10:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| orman |
| Posted: Wed Feb 18, 2015 11:02 pm Post subject: |
|
|
Apprentice
Joined: 08 Aug 2013
Posts: 40
|
| mqjeff wrote: |
| http://www.ibm.com/developerworks/websphere/library/techarticles/0603_schutz/0603_schutz.html |
Hey thanks that looks interesting!
I read this article but no for my case - using timer in some broker parallel, what mean all the brokers have to know which broker is going to take the control and let him do it.
After I read this one scenario 5 let me think about using db or gc for shared space between brokers, every timer as it unique name and any broker too, so every broker runs the timer and check if it as to run it, if any broker took control it delays to the next run(by datetime or interval )
So, all broker run timers, if one is down so the others have to backup it
What so you think? |
|
| Back to top |
|
|
| adubya |
| Posted: Thu Feb 19, 2015 3:10 am Post subject: |
|
|
Partisan
Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK
|
Design for the situation where you can get duplicate timer events, which will be the norm if you have the same timer flow deployed to two active-active brokers. I don't think broker is going to help you here, you need to come up with the design pattern.
It's a tricky one I'll give you that  |
|
| Back to top |
|
|
| nelson |
| Posted: Thu Feb 19, 2015 7:04 am Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| In an active-active environment your integration nodes (brokers) work independently. In addition, timer nodes use queues to store the timeout information (SYSTEM.BROKER.TIMEOUT.QUEUE, by default), so I don´t think you can handle this kind of failure event, I don´t think yo can tell a broker to take the control of a timeout of another broker.. |
|
| Back to top |
|
|
| orman |
| Posted: Fri Feb 20, 2015 2:00 am Post subject: |
|
|
Apprentice
Joined: 08 Aug 2013
Posts: 40
|
| adubya wrote: |
Design for the situation where you can get duplicate timer events, which will be the norm if you have the same timer flow deployed to two active-active brokers. I don't think broker is going to help you here, you need to come up with the design pattern.
It's a tricky one I'll give you that |
| nelson wrote: |
| In an active-active environment your integration nodes (brokers) work independently. In addition, timer nodes use queues to store the timeout information (SYSTEM.BROKER.TIMEOUT.QUEUE, by default), so I don´t think you can handle this kind of failure event, I don´t think yo can tell a broker to take the control of a timeout of another broker.. |
Firstly thanks for comments
So no one as any suggestion for this case?
Well, in my opinion those Timers as to be use for in-house work in the broker, so any broker will work independently.
Such as , filling a cache node, alerts or something like that.
But sometimes we use those for send message the applications and we don't want to do it duplicate each time .. |
|
| Back to top |
|
|
| nelson |
| Posted: Sun Feb 22, 2015 6:37 pm Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| orman wrote: |
Well, in my opinion those Timers as to be use for in-house work in the broker, so any broker will work independently.
Such as , filling a cache node, alerts or something like that.
But sometimes we use those for send message the applications and we don't want to do it duplicate each time .. |
If you want to store the state of a transaction between the two integration nodes you should use a database or global cache. So.. if I don´t misunderstand you, you should check if after a Timeout flow is triggered, someone (the other flow, in the remote integration node) already has executed the action, and if so, discard the message. |
|
| 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
|
|
|
|
