3 Replies Latest reply on Dec 12, 2012 5:44 PM by Alexander Schmied

    direct-deliver documentation inconsistency

    Tim H Newbie

      The documentation around direct-deliver seems to be contradictory.  This is from 16.4.1...

       

      When a message arrives on the server and is delivered to waiting consumers, by default, the delivery is done on a different thread to that which the message arrived on. This gives the best overall throughput and scalability, especially on multi-core machines. However it also introduces some extra latency due to the extra context switch required. If you want the lowest latency and the possible expense of some reduction in throughput then you can make sure direct-deliver to true. The default value for this parameter is true.

       

      The two parts in bold seem to be mismatched.  Either the default is False, or by default when a message arrives, the delivery is done on the same thread (which is my interpretation of what direct-deliver means).