Post reply

Problems with variables in parallel execution

  • September 19, 2012 at 7:36 am

    #281785

    I have a parent package(Pkg1) which executes Pkg2 thrice in parallel. And Pkg2 executes Pkg3 thrice in parallel. These packages have variables(with same names between childs and parent) passed from parent to child packages. I use a script task to pass the variables to the child and execute using execute() method.

    However, I see the logs that the variable values passed are jumbled between the executions. Suppose variable value is passed A for first of the parallel executions and passed B for second of the parallel executions, I see that during execution the second one takes a value of A.

    I changed the common variable names in the Pkg2. But still the issue exists. Do I have to modify the variable names for Pkg1 too? Will that fix it, or is there anything else I can do?

    Thanks and Regards,

    Praveena

  • September 19, 2012 at 12:30 pm

    #1539744

    venus.pvr (9/19/2012)

    I have a parent package(Pkg1) which executes Pkg2 thrice in parallel. And Pkg2 executes Pkg3 thrice in parallel. These packages have variables(with same names between childs and parent) passed from parent to child packages. I use a script task to pass the variables to the child and execute using execute() method.

    However, I see the logs that the variable values passed are jumbled between the executions. Suppose variable value is passed A for first of the parallel executions and passed B for second of the parallel executions, I see that during execution the second one takes a value of A.

    I changed the common variable names in the Pkg2. But still the issue exists. Do I have to modify the variable names for Pkg1 too? Will that fix it, or is there anything else I can do?

    Thanks and Regards,

    Praveena

    I've not come across this problem, but one thing I would do is set pre-execute breakpoints on all of the control flow items & then run in debug mode just to assure yourself 100% that things are definitely going wrong in the way that you describe - could there be something in your logic which is messing things up, for example?

    The absence of evidence is not evidence of absence.
    Martin Rees

    You can lead a horse to water, but a pencil must be lead.
    Stan Laurel

  • September 21, 2012 at 2:01 pm

    #1540957

    The errors were gone when I used ExecuteProcess task to execute the childpackages instead.

    Thanks and Regards,

    Praveena

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply