| Author |
Message
|
| punky |
 Posted: Thu May 31, 2012 9:14 pm Post subject: Killing pending comands for start and stop message flows. |
 |
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
Hi All,
I am using WMB toolkit.
Due to multiple issued commands to start and stop message flows, the proker has created a kist of tasks to start and stop the message flows and is not responding to new commands.
Is there some way, I can kill these previously given commands, and get the flow restarted by issuing new command.
Please reply at the earliest. |
|
| Back to top |
|
 |
| mqsiuser |
| Posted: Fri Jun 01, 2012 2:15 am Post subject: Re: Killing pending comands for start and stop message flows |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
Kill the process, it is called "Data Flow Engine"
You should not have problems starting and stopping EGs... note that if there are a couple of flows deployed, that this may take some time.
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Jun 01, 2012 4:59 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Sounds like your not using proper runtime user Id / group. What is the service Id that your Broker runs under?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jun 01, 2012 5:00 am Post subject: Re: Killing pending comands for start and stop message flows |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| mqsiuser wrote: |
| Kill the process, it is called "Data Flow Engine" |
How will that cause the list of pending tasks to get cleared? |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Fri Jun 01, 2012 9:07 am Post subject: Re: Killing pending comands for start and stop message flows |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| mqjeff wrote: |
| mqsiuser wrote: |
| Kill the process, it is called "Data Flow Engine" |
How will that cause the list of pending tasks to get cleared? |
The OP shall do this and tell us if it helps.
@OP: AIX or Windows ? Is the Broker on the same Windows-box as the toolkit ?
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jun 01, 2012 9:27 am Post subject: Re: Killing pending comands for start and stop message flows |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| mqsiuser wrote: |
| mqjeff wrote: |
| mqsiuser wrote: |
| Kill the process, it is called "Data Flow Engine" |
How will that cause the list of pending tasks to get cleared? |
The OP shall do this and tell us if it helps. |
The only way it would help is if the last started task had caused the EG to hang.
Why do you expect that the last started task had caused the EG to hang?
We also need to know exactly what version of the Broker is involved, as the moving parts are very different between v6.0 and v8.0. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Fri Jun 01, 2012 11:23 am Post subject: Re: Killing pending comands for start and stop message flows |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| mqjeff wrote: |
| Why do you expect that the last started task had caused the EG to hang? |
Intuition... I just get this right intuitivly... no brute force: kill, then restart (is likely to help  )
Look did the OP complain on my suggestion ?
I guess my advice solved his problem, thats why he is not getting back (into the discussion) 
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 01, 2012 11:58 am Post subject: Re: Killing pending comands for start and stop message flows |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqsiuser wrote: |
| mqjeff wrote: |
| Why do you expect that the last started task had caused the EG to hang? |
Intuition... I just get this right intuitivly... no brute force: kill, then restart (is likely to help ) |
I've always got into trouble acting as if things work the way I think they do. I likewise struggle to see how stopping and starting the EG will clear a queued list of pending tasks.
| mqsiuser wrote: |
| Look did the OP complain on my suggestion ? |
If the OP knew enough to complain about the suggestion, he wouldn't have posted.
| mqsiuser wrote: |
| I guess my advice solved his problem, thats why he is not getting back (into the discussion) |
Or he's one of the army of posters who post a question, get asked questions in return and never respond. The forum is littered with them. I used to wonder what happened about their problems, but gave up years ago.
Do we think this guy is still working on his ODBC and will respond shortly?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Sat Jun 02, 2012 12:31 am Post subject: Re: Killing pending comands for start and stop message flows |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| Vitor wrote: |
| I likewise struggle to see how stopping and starting the EG will clear a queued list of pending tasks. |
Probably the queued list of tasks gets deleted (when restarting).
The question is: Where is the queue and how do you delete ?
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Jun 02, 2012 2:25 am Post subject: Re: Killing pending comands for start and stop message flows |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| mqsiuser wrote: |
| Vitor wrote: |
| I likewise struggle to see how stopping and starting the EG will clear a queued list of pending tasks. |
Probably the queued list of tasks gets deleted (when restarting).
The question is: Where is the queue and how do you delete ? |
No.
The question is: why is the broker not processing the queue.
Restarting it won't answer that question. It'll just avoid it until next time.
And... No, I don't think the queued list of tasks DOES get deleted at restart. |
|
| Back to top |
|
|
| punky |
| Posted: Sun Jun 03, 2012 7:25 pm Post subject: |
|
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
I think I was not able to explain the entire situation.
We have the WMB server on a UNIX machine.
I use a Toolkit installed on Windows RDP to connect to the UNIX system (to deploy flows, start/and stop flows).
In case of an outbound IDOC scenario, the IDOCS were struck and after checking I found that there was an RFC connection error (which is caused because the WMB flow is stopped).
So I wanted to stop and start the flow (restart the flow).
As the flow was not responding, the commands to start and stop the flow was issued multiple times (few tasks vissible in the pending list).
I waited for the tasks to get complete, but looks some deadlock occured.
So I asked, how can I remove the pending task (to clear the deadlock situation).
The problem is solved now, by deleting the flow and deploying it again.
Looks strange, but I was able to delete the flow.
Thanks every one for help...
This is a wonderful forum and I learn a lot from here
Regards,
PUnky |
|
| Back to top |
|
|
|
|
