[jira] [Commented] (ROCKETMQ-355) Client asyncSend is not fully async.

Thu, 25 Jan 2018 23:21:37 -0800 

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

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

coveralls commented on issue #222: [ROCKETMQ-355] Client asyncSend is not fully 
async
URL: https://github.com/apache/rocketmq/pull/222#issuecomment-360454546
 
 
   
   [![Coverage 
Status](https://coveralls.io/builds/15231078/badge)](https://coveralls.io/builds/15231078)
   
   Coverage increased (+0.2%) to 40.138% when pulling 
**0e09e265456f81315a3b2d1edd67fc0370638cb5 on lindzh:fix_asyncSend** into 
**a096580f3152e12fc9f9876c9e9721eb0109a90a on apache:develop**.
   

----------------------------------------------------------------
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:
[email protected]


> 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