03-02-2012 11:17 AM
Workaround 1) is perfectly OK, thank you.
We are using these queues in an environment where we distribute work to threads on one machine and remote engines on other machines. I did not anticipate a need to dequeue from both types simultaneously.and had originally chosen the scheme to use local names where possible, computer-based names only where necessary, because local queues are slightly faster (the asterisk-queues being considerably slower, I noticed).
However, the absolute difference in turnaround time is so small that it is absolutely OK for us to use fully qualified names everywhere.
thanks
Peter
03-02-2012 11:18 AM
Nice idea, using the process ID in the queue name.
Peter