| Author |
Message
|
| Siddu |
 Posted: Fri Nov 22, 2013 2:50 am Post subject: Unable to deploy Message Flows with collector nodes |
 |
|
Apprentice
Joined: 22 Aug 2012
Posts: 44
|
Hi All,
I've a message flow which has two collector nodes.
Collector configuration is empty. When trying to deploy the flow onto Execution group it takes very long time. In first 2/3 attempts flow fails to deploy with timeout notification(after 15 minutes). After that retrying again it gets deployed. I tried using mqsideploy command also but still facing same problem.Is it due to the collector node in a flow? Is there any fix for this?
Thanks
Siddu
_________________
"Be honest. It is one of the few things that you can control in your life." |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Nov 22, 2013 5:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What version of WMB?
How many other flows are in the EG?
Do other flows expereince the same deploy problem?
And no, a flow with 1-n collector nodes should not fundamentally take longer to deploy than any other flow with the same number of nodes.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Nov 22, 2013 7:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
A flow can't be redeployed until it has stopped processing all work.
You can confirm that the problem is with the deployment or with the flow trying to finish work by deleting the flow before you deploy it. If it deletes quickly but fails to deploy quickly, then the problem is with the deployment. If it fails to delete quickly but deploys fast then the problem is with the flow still processing work.
Note that there's nothing unique about the collector node here. |
|
| Back to top |
|
|
| ganesh |
| Posted: Fri Nov 22, 2013 5:52 pm Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| To isolate and debug the problem better and if you could afford creating a new execution group then create one and try to deploy the flow which has collector nodes, by doing this you can make sure the problem was not because of some other flow keeping the EG busy and hence causing your deploy of flow with collector node take longer time. |
|
| Back to top |
|
|
| sumit |
| Posted: Sat Nov 23, 2013 5:06 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
At times, I have seen this problem when someone is running debug and without finishing the message processing, started to deploy a flow in same execution group.
At a higher level, it's the same problem of execution group being busy.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| Siddu |
| Posted: Sun Nov 24, 2013 11:19 pm Post subject: |
|
|
Apprentice
Joined: 22 Aug 2012
Posts: 44
|
| Vitor wrote: |
What version of WMB?
How many other flows are in the EG?
Do other flows expereince the same deploy problem?
And no, a flow with 1-n collector nodes should not fundamentally take longer to deploy than any other flow with the same number of nodes. |
Hi Vitor,
WMB version is 7.0
There are no flows on this EG. I'm deleting all the existin flows on this EG before deploying my onto this.
Do Collections and Event Queues have any role to play here? Do I need to make sure these queues are also empty before redeploying? If I delete the existing flow for redeployment but there are messages in Collection/Event System Queues which waiting to be processed, can cause problem?
_________________
"Be honest. It is one of the few things that you can control in your life." |
|
| Back to top |
|
|
| Siddu |
| Posted: Sun Nov 24, 2013 11:21 pm Post subject: |
|
|
Apprentice
Joined: 22 Aug 2012
Posts: 44
|
| mqjeff wrote: |
A flow can't be redeployed until it has stopped processing all work.
You can confirm that the problem is with the deployment or with the flow trying to finish work by deleting the flow before you deploy it. If it deletes quickly but fails to deploy quickly, then the problem is with the deployment. If it fails to delete quickly but deploys fast then the problem is with the flow still processing work.
Note that there's nothing unique about the collector node here. |
Hi Jeff,
I'm able to delete the existing flow quickly from Execution Group, but not able able to deploy the flow quickly. Do you think the problem might be with Collection/Event System Queues of collector node?
_________________
"Be honest. It is one of the few things that you can control in your life." |
|
| Back to top |
|
|
| Siddu |
| Posted: Sun Nov 24, 2013 11:25 pm Post subject: |
|
|
Apprentice
Joined: 22 Aug 2012
Posts: 44
|
| sumit wrote: |
At times, I have seen this problem when someone is running debug and without finishing the message processing, started to deploy a flow in same execution group.
At a higher level, it's the same problem of execution group being busy. |
Hi Sumit,
I'm redeploying the flow only after terminating debugger and deleting all flows on the Execution Group. If Execution Group is busy with debugging, then it shouldn't allow me to delete the existing flows. Please correct me if I'm wrong.
_________________
"Be honest. It is one of the few things that you can control in your life." |
|
| Back to top |
|
|
|
|
