Author |
Message
|
ldtluxury |
Posted: Sun Aug 30, 2015 11:49 pm Post subject: EG and application start control |
|
|
 Apprentice
Joined: 22 Oct 2014 Posts: 29
|
Hello everyone!
Could you please assist with these 2 questions?
Is it possible and how to start integration node with stopped all integration servers (eg)?
Is it possible and how to start integration server (eg) with stopped all applications? |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Aug 31, 2015 4:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Yes, to both. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Aug 31, 2015 4:57 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
And the how is more then likely defailed in the documentation and at least one thread in this forum _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
ldtluxury |
Posted: Thu Sep 03, 2015 1:42 am Post subject: |
|
|
 Apprentice
Joined: 22 Oct 2014 Posts: 29
|
mqjeff wrote: |
Yes, to both. |
But how? The problem is to stop application on stopped broker/eg.
This is useful when an application is in infinity loop. |
|
Back to top |
|
 |
smdavies99 |
Posted: Thu Sep 03, 2015 3:14 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
ldtluxury wrote: |
mqjeff wrote: |
Yes, to both. |
But how? The problem is to stop application on stopped broker/eg.
This is useful when an application is in infinity loop. |
The EG will restart. If the message transport is MQ then get inhibit the queue and the looping won't start.
Obviously if you get this in Production then you have far bigger issues. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
ldtluxury |
Posted: Thu Sep 03, 2015 4:35 am Post subject: |
|
|
 Apprentice
Joined: 22 Oct 2014 Posts: 29
|
smdavies99 wrote: |
ldtluxury wrote: |
mqjeff wrote: |
Yes, to both. |
But how? The problem is to stop application on stopped broker/eg.
This is useful when an application is in infinity loop. |
The EG will restart. If the message transport is MQ then get inhibit the queue and the looping won't start.
Obviously if you get this in Production then you have far bigger issues. |
Well, is it possible to do something, that flow will not start after EG restart? |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Sep 03, 2015 4:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
There are commands to change the starting state of EGs and message flows. This would be an excellent place to start finding out how to do the things you want to do.
When I said "Yes to both.", you had not yet said "The EG/broker is stopped".
So my answer might not apply to that situation. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
ldtluxury |
Posted: Thu Sep 03, 2015 5:02 am Post subject: |
|
|
 Apprentice
Joined: 22 Oct 2014 Posts: 29
|
mqjeff wrote: |
There are commands to change the starting state of EGs and message flows. This would be an excellent place to start finding out how to do the things you want to do.
When I said "Yes to both.", you had not yet said "The EG/broker is stopped".
So my answer might not apply to that situation. |
Yes, sorry.
Could you please give examples of these commands? |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Sep 03, 2015 5:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
ldtluxury wrote: |
mqjeff wrote: |
There are commands to change the starting state of EGs and message flows. This would be an excellent place to start finding out how to do the things you want to do.
When I said "Yes to both.", you had not yet said "The EG/broker is stopped".
So my answer might not apply to that situation. |
Yes, sorry.
Could you please give examples of these commands? |
I'm sure the Knowledge Center has better examples than I could give. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
zpat |
Posted: Thu Sep 03, 2015 6:54 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
The EG won't respond to stop commands when a flow is looping or in a wait state (mid transaction that is).
Aside from sacking any developer who can't code properly - you will have to kill the EG process, or stop the broker with -i option. _________________ Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 03, 2015 7:03 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
zpat wrote: |
The EG won't respond to stop commands when a flow is looping or in a wait state (mid transaction that is).
Aside from sacking any developer who can't code properly - you will have to kill the EG process, or stop the broker with -i option. |
Under IIBv9 or later, you might get some joy from the ProcessingTimeoutSec attribute of a workload management policy. I've not tested it with a looping flow (so many issues, so little time) and I can envisage that such a flow might ignore this at it ignores an mqsistopmsgflow. But it may be that if the broker does something more, shall we say assertive, in it's position as the parent thread.
Works a treat on flows deadlocked against databases, or with SQL queries table scanning 1M rows. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
zpat |
Posted: Thu Sep 03, 2015 7:33 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Interesting, we are starting to look at using WLM - although I did notice a recent APAR which causes Abends when WLM is used.
------
processingTimeoutAction
The only option for this seems to be "Restart Execution Group" - what happens if this value is not set? _________________ Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
Back to top |
|
 |
smdavies99 |
Posted: Thu Sep 03, 2015 8:24 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
ldtluxury wrote: |
Well, is it possible to do something, that flow will not start after EG restart? |
The EG will restart and once initialised it will start all the flows that are configured to run.
However there is a window where you can stop the flow if you are fairly quick.
Or as I said, if the Message Transport is MQ GET Inhibit the Queue that the flow uses. Then even if it starts it won't be able to read a message and possibly return to a looping state.
But as has been suggested, all the commands you need to use are documented. Experienced IIB Administrators will know these commands and use them as needed. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 03, 2015 8:55 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
zpat wrote: |
The only option for this seems to be "Restart Execution Group" - what happens if this value is not set? |
The execution group restarts.
It's a placeholder for more options coming shortly. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
ldtluxury |
Posted: Thu Sep 03, 2015 11:41 pm Post subject: |
|
|
 Apprentice
Joined: 22 Oct 2014 Posts: 29
|
smdavies99 wrote: |
ldtluxury wrote: |
Well, is it possible to do something, that flow will not start after EG restart? |
The EG will restart and once initialised it will start all the flows that are configured to run.
However there is a window where you can stop the flow if you are fairly quick.
Or as I said, if the Message Transport is MQ GET Inhibit the Queue that the flow uses. Then even if it starts it won't be able to read a message and possibly return to a looping state.
But as has been suggested, all the commands you need to use are documented. Experienced IIB Administrators will know these commands and use them as needed. |
Could you please give a link to article in Knowledge Center? I can't find it.  |
|
Back to top |
|
 |
|