[ 
https://issues.apache.org/jira/browse/ROCKETMQ-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16351997#comment-16351997
 ] 

ASF GitHub Bot commented on ROCKETMQ-355:
-----------------------------------------

lindzh commented on issue #222: [ROCKETMQ-355] Client asyncSend is not fully 
async
URL: https://github.com/apache/rocketmq/pull/222#issuecomment-362966428
 
 
   @zhouxinyu,yeah, keep comment is a good idea for continuous develop. At 
first I want to limit the send request and using network semaphore as send 
signal,but after doing that I found it was a mistake and open another PR for 
concise and speed.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Client asyncSend is not fully async.
> ------------------------------------
>
>                 Key: ROCKETMQ-355
>                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-355
>             Project: Apache RocketMQ
>          Issue Type: Bug
>          Components: rocketmq-client
>            Reporter: lindzh
>            Assignee: Xiaorui Wang
>            Priority: Major
>
> Client asyncSend is not fully async because of param validation, connection 
> status check and get route info may cause exception,and these exceptions is 
> called in user thread may cause biz stop.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to