Avatar

Level 4

I ran a test.  I did experience concurrency issues, i.e., dirty writes.

My suspicion is that even using a SetValue (rather than my custom DSC) could still see this issue.   After all, under the hood, the SetValue is a Java component which takes parameters and provides an output.  I could write test code to prove this I guess.

I think my only real choice to resolve this is to write my own mutex to serialize access to my critical process variable.  If mutex is set, route to Wait activity and try again later.