|
|
|
[
Permlink
| « Hide
]
Robin Shen [16/Oct/11 12:26 AM]
Can not reproduce. Please re-open by providing more info.
I followed your scenario, but still can not get it reproduced. This is what I am doing:
1. create configuration root/A, and root/B 2. create two queue, A and B, A has one worker, and B has five workers. 3. modify root/A to use queue A, and root/B to use queue B. 4. add a step to root/A to trigger root/B with "wait for finish" set to "always". 5. add several sleep steps to root/B to sleep for some time. 6. trigger root/A and root/B will be triggered by root/A as a result. 7. root/A will run until root/B finishes, and this is expected. In my case config A calls Config B and config B has multiple steps. This all seems to work fine as long as I have them using the same Queue but in this case I have a queue with a single worker thread to not allow multiple calls to config A type of configurations before it finishes. Config B is using a different Queue that has many worker threads. So my thinking is somehow the change to use different Queues changes the workflow. Do you still need a sample?
The configuration to be triggered might has been triggered by another configuration in the same trigger chain. That is, if A trigges B and C, and then B triggesC, the trigger step of B might finish immediately if C has already been built when triggered from A.
If this is not the case, please create a test case to demonstrate the problem, and then send the database backup of the test case. |