When an application ivokes any of the library methods with the noWait
flag set, the broker will not reply back with a message to confirm that the
request (e.g. declare a queue, exchange etc.) was successful. As a
result the returned Future values where never completed thus causing the
callers to hang.
When using the noWait flag, the broker will report errors asynchronously
via the channel or connection instance.
Coverage increased (+0.004%) to 93.107% when pulling ac86799dbcd7ec7be1ca0fea5340aee167ad99a4 on fix-incorrect-handling-of-nowait-flag into 41410bf88c15b57d8be7ad8d88468bd6dbd4cab4 on master.
When an application ivokes any of the library methods with the noWait flag set, the broker will not reply back with a message to confirm that the request (e.g. declare a queue, exchange etc.) was successful. As a result the returned Future values where never completed thus causing the callers to hang.
When using the noWait flag, the broker will report errors asynchronously via the channel or connection instance.