I have tweaked the docs to note that implicitly(/explicitly) asynchronous CompletionListener related sends are not governed by that option. The site will reflect that upon the next release.
Robbie On Mon, 10 Jun 2019 at 16:30, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: <snipped> > > It is not a bug. As explained above and last year, that option does > not control CompletionListener-using sends. Providing a > CompletionListener means it is asynchronous and you get the eventual > result back via it. That is explicit in its operation and is the only > reason for providing it. > <snipped> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
