| Author |
Message
|
| ravi_ishere |
 Posted: Thu Feb 14, 2008 6:02 pm Post subject: How to run MB v6.0 command console commands from ESQL |
 |
|
Apprentice
Joined: 20 Jan 2008
Posts: 29
|
Hi All,
Can anyone know how to pass and run the WBI Broker 'Command Console' commands from ESQL.
Thanks,
R[/i] |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Feb 14, 2008 6:37 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
ESQL provides no access to OS level functions of any kind.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| AJStar |
| Posted: Thu Feb 14, 2008 8:01 pm Post subject: |
|
|
Acolyte
Joined: 27 Jun 2007
Posts: 64
|
Just curious to know the reason behind that requirement!! 
Or is it just that you wanted to know if it is possible or not??
_________________
Regards
AJ |
|
| Back to top |
|
|
| rsmile |
| Posted: Fri Feb 15, 2008 2:06 am Post subject: |
|
|
Apprentice
Joined: 13 Feb 2008
Posts: 38
|
I Too have a similar requirement.
We need to stop the broker when a message flow fails.Can some one give a clue of how we can stop the broker is such cases from a message flow. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 15, 2008 2:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rsmile wrote: |
| We need to stop the broker when a message flow fails. |
Why? What happens if the flow "fails" because of one badly formed message or other data problem? Do you seriously intend to halt all processing while the problem is resolved, allowing messages which could potentially be processed to back up?
If yes, you either have some relaxed SLAs or serious message affinity issues! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 15, 2008 2:24 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
To put another slant on the question, if the message flow has "failed", how is anything in the ESQL going to help with the problem? By definition the flow (and possibly the broker) is already in an unreliable state because of this "failure". So the only way this kind of problem can be handled is by external monitoring software of some kind.
Unless you're talking about handled errors (see my previous post) where the flow detects invalid data and as part of the error handling tries to stop itself. In that case, see also my previous post!!! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rsmile |
| Posted: Fri Feb 15, 2008 3:12 am Post subject: |
|
|
Apprentice
Joined: 13 Feb 2008
Posts: 38
|
I need to stop the message flow as part of the error handling, this occurs in a very rare case.
Vitor could you give the link to your previous post. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 15, 2008 3:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rsmile wrote: |
| I need to stop the message flow as part of the error handling, this occurs in a very rare case. |
Well as jefflowrey pointed out up top, ESQL doesn't allow access to OS functions. You could write a custom C node that launched a shell process and issued the command; I've no idea if that would work, it would be a massively undesireable thing to do (how would anyone know the flow/broker had stopped) and I struggle to see what kind of error handling could possibly warrent this action, that wasn't involving a more significant broker error which should be handled by more conventional means.
It's one of those "you could do this but it's difficult, dangerous and why would you want to" situations. I mean, you could run a TV off a 11Kv transmission line; you just need a really big transformer and a lot of room at the back of your house. Plus some high fencing, no emotional attachment to any pets or children and the TV sited far enough back in your living room that it won't shower you with glass when it explodes. But you could do it. But a wall socket remains the preferred choice of connection.
| rsmile wrote: |
Vitor could you give the link to your previous post.
|
I meant my previous post in this thread - apologies for any ambiguity. I still don't see (as I repeat above) what circumstances would warrent a flow trying to end itself!
Example please (even if rare). If there isn't a better way of dealing with these situations, there should be!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Feb 15, 2008 3:50 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| rsmile wrote: |
| I need to stop the message flow as part of the error handling, this occurs in a very rare case. |
Supposing you're at least at version 6 you could use a JCN to access the the configmgr proxy (java) and stop the flow using that...
Note this is still quite ugly...
Easier way to stop the flow would be to ensure that a roll back is done and have no bothreshold on the queue?
Any other suggestions welcome.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| fschofer |
| Posted: Fri Feb 15, 2008 4:00 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 15, 2008 4:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
Easier way to stop the flow would be to ensure that a roll back is done and have no bothreshold on the queue?
|
Would that actually stop the flow? Or just dump the failing message onto the backout queue (which is my preferred error handling anyway)?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sunny_30 |
| Posted: Mon Feb 18, 2008 6:36 pm Post subject: |
|
|
Master
Joined: 03 Oct 2005
Posts: 258
|
| Another easy way to stop/disable the flow is to send a PCF message from within the flow that get-inhibits the Input-queue itself. |
|
| Back to top |
|
|
|
|
