From fae5b7a68193b5863c54aac1df14d1b7b99041e0 Mon Sep 17 00:00:00 2001 From: melissaml Date: Thu, 8 Feb 2018 09:15:31 +0800 Subject: [PATCH] Modify grammatical errors Change-Id: I8c1cd79179eb3930b1ce69c63015adc5ec4a1d3c --- releasenotes/notes/rabbit-no-wait-for-ack-9e5de3e1320d7660.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/releasenotes/notes/rabbit-no-wait-for-ack-9e5de3e1320d7660.yaml b/releasenotes/notes/rabbit-no-wait-for-ack-9e5de3e1320d7660.yaml index 4b9d47af3..28a711d8b 100644 --- a/releasenotes/notes/rabbit-no-wait-for-ack-9e5de3e1320d7660.yaml +++ b/releasenotes/notes/rabbit-no-wait-for-ack-9e5de3e1320d7660.yaml @@ -4,7 +4,7 @@ other: On rabbitmq, in the past, acknownlegement of messages was done within the application callback thread/greenlet. This thread was blocked until the message was ack. In newton, we rewrote the message acknownlegement to - ensure we haven't two threads writting the the socket at the same times. + ensure we haven't two threads writting the socket at the same times. Now all pendings ack are done by the main thread. They are no more reason to block the application callback thread until the message is ack. Other driver already release the application callback threads before the message