Author |
Message
|
ashetty |
Posted: Thu Apr 24, 2014 12:56 am Post subject: Status of Message Flow After Broker Restart |
|
|
Newbie
Joined: 17 Oct 2013 Posts: 3
|
Hello All,
We are using MB 8.0.0.1.
We have monitoring events configured in message flows of all interfaces.
We deploy by keeping the bar file with Start Mode as "Manual" for Application and once we deploy we turn on the flowmonitoring and then we start the Application.
Recently broker was stopped abruptly due to some environmental issues and when the broker was brought up, we saw that message flows were running with flowmonitoring down.
We were hoping that all the Interfaces will be in stopped state after Broker restart as we had kept StartMode as Manual but that wasn't the case.
I'd appreciate if someone can tell me how to keep the message flow in stopped state whenever there is a broker restart?
Thanks |
|
Back to top |
|
 |
Esa |
Posted: Thu Apr 24, 2014 2:31 am Post subject: Re: Status of Message Flow After Broker Restart |
|
|
 Grand Master
Joined: 22 May 2008 Posts: 1387 Location: Finland
|
ashetty wrote: |
Recently broker was stopped abruptly due to some environmental issues and when the broker was brought up, we saw that message flows were running with flowmonitoring down.
|
Funny, usually the problem is exactly the opposite! You deploy the flows with start mode 'Manual' and then you have to run a little java CMP program that (assigns the monitoring profile to the flows and) changes start mode to 'Maintained' (and starts the flows), otherwise the flows would not start again if the broker or eg is restarted.
I think the key to the problem is that you set the start mode of the application and not the individual flows within the application.
The flows shouldn't drop monitoring when the broker is restarted. I think the problem here may have the same cause: you assigned the monitoring profile to the application, not the individual flows.
I think the application object doesn't act exactly the way it should, yet. It's safer to set up these things on message flow level, at least for now. |
|
Back to top |
|
 |
ashetty |
Posted: Mon Apr 28, 2014 5:30 am Post subject: |
|
|
Newbie
Joined: 17 Oct 2013 Posts: 3
|
Thanks Esa for the response.
After doing a test in local broker, I noticed that the Application appeared to be in started state after broker restart but when I did a refresh on execution group, Application turned into a stopped state. |
|
Back to top |
|
 |
Esa |
Posted: Mon Apr 28, 2014 6:34 am Post subject: Re: Status of Message Flow After Broker Restart |
|
|
 Grand Master
Joined: 22 May 2008 Posts: 1387 Location: Finland
|
ashetty wrote: |
We are using MB 8.0.0.1.
|
Upgrade to the latest fix pack and test again. |
|
Back to top |
|
 |
paustin_ours |
Posted: Wed Jul 16, 2014 3:11 pm Post subject: |
|
|
Yatiri
Joined: 19 May 2004 Posts: 667 Location: columbus,oh
|
Quote: |
you have to run a little java CMP program that (assigns the monitoring profile to the flows and) changes start mode to 'Maintained' (and starts the flows), otherwise the flows would not start again if the broker or eg is restarted.
|
I thought the monitoring profile was to collect motoring events, can it be used to change the start mode of the flows? |
|
Back to top |
|
 |
Simbu |
Posted: Wed Jul 16, 2014 4:19 pm Post subject: |
|
|
 Master
Joined: 17 Jun 2011 Posts: 289 Location: Tamil Nadu, India
|
paustin_ours wrote: |
Quote: |
you have to run a little java CMP program that (assigns the monitoring profile to the flows and) changes start mode to 'Maintained' (and starts the flows), otherwise the flows would not start again if the broker or eg is restarted.
|
I thought the monitoring profile was to collect motoring events, can it be used to change the start mode of the flows? |
No. If I'm correct, the idea was to run a CMP program to do both assign the monitoring profile to the flows and change start mode to 'Maintained' . |
|
Back to top |
|
 |
paustin_ours |
Posted: Wed Jul 16, 2014 5:41 pm Post subject: |
|
|
Yatiri
Joined: 19 May 2004 Posts: 667 Location: columbus,oh
|
That's right. I read it too fast. Thx |
|
Back to top |
|
 |
|