swhitmire
Reputable Poster
We have a custom UBE that calls another custom UBE. The UBE being called needs to
run in a single-threaded queue to ensure that only one copy runs at a time.
We have the version set for a single-threaded queue, but when it's called by
the other UBE, it runs in the queue that UBE ran in instead. Since the calling UBE doesn't finish
until the called UBE finishes, we can't just set the calling UBE to run in the single-threaded queue.
Has anyone had this problem before, and if so, how did you solve it?
run in a single-threaded queue to ensure that only one copy runs at a time.
We have the version set for a single-threaded queue, but when it's called by
the other UBE, it runs in the queue that UBE ran in instead. Since the calling UBE doesn't finish
until the called UBE finishes, we can't just set the calling UBE to run in the single-threaded queue.
Has anyone had this problem before, and if so, how did you solve it?