| Author |
Message
|
| kotha |
 Posted: Thu Sep 13, 2007 5:58 am Post subject: Stopping the Broker from the broker flow |
 |
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
The requirement is to stop the broker flow by itself in case of any error.
One option is: useing the trigger mechanism. We are implementing this one in our prod but looking for another options.
Is it possible to use JAVA API in a node so that it will stop the broker to receive any messages off the queue?
Please share your ideas.
Your help is greatly appriciated. Thanks,
Last edited by kotha on Thu Sep 13, 2007 8:33 pm; edited 1 time in total |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Sep 13, 2007 6:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I'm assuming here you've no access to monitoring software or any of the more traditional system level error resolution strategies?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 13, 2007 6:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So what you're saying is, if some minor problem occurs in one flow in one execution group, you want to stop the entire broker?
What a horrible horrible idea.
Please don't do this.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 13, 2007 6:33 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
| So what you're saying is, if some minor problem occurs in one flow in one execution group, you want to stop the entire broker? |
It's a bit extreme, but maybe the ops manager is paranoid, or excessively hands on.
Or the ops have a really, really good call out package. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 13, 2007 6:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes, because the ops manager wants his paranoia to be responsible for the monthly payroll process not getting completed, and thus the CEO's paycheck not getting deposited automatically on the day expected.
I repeat - allowing any individual flow in Broker to have the ability to stop the entire system is a horrible horrible idea.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 13, 2007 6:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
| Yes, because the ops manager wants his paranoia to be responsible for the monthly payroll process not getting completed, and thus the CEO's paycheck not getting deposited automatically on the day expected |
I never said his paranoia was correctly focused.... 
I have known people who'd stop the overnight batch process because some of the user reporting hadn't finished. But they're not normally allowed positions of authority. For long. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kotha |
| Posted: Thu Sep 13, 2007 8:32 pm Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
| no. I want that purticular flow to stop itself by itself (using one of its nodes). I hope I made it clear now. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu Sep 13, 2007 9:46 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi kotha,
| kotha wrote: |
| no. I want that purticular flow to stop itself by itself (using one of its nodes). I hope I made it clear now. |
Issue PCF Msg from flow - Sample
Regards. |
|
| Back to top |
|
|
| kotha |
| Posted: Fri Sep 14, 2007 4:56 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
|
| Back to top |
|
|
|
|
