Re: JMSOrderException when sending message on distibuted
queue

This behavior is the expected trade-off of using hash based routing instead of
path service routing, as is detailed in the unit-of-order and unit-of-work
documentation. 

To think of it simply in another way: Hash based UOO routing pre-selects the
target member destination for a UOO based on the UOO string itself (the
algorithm is something like member_num = uoo.hashCode() % num_members), so a
particular UOO always hashes to the same member regardless of whether the member
is currently available. This is what allows hash routing to work without a
central authority like the path service.