Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Apache RocketMQ
Rocketmq
提交
01a0eb00
R
Rocketmq
项目概览
Apache RocketMQ
/
Rocketmq
上一次同步 大约 3 年
通知
267
Star
16139
Fork
68
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
R
Rocketmq
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
提交
01a0eb00
编写于
2月 15, 2017
作者:
J
Jaskey
提交者:
Zhanhui Li
3月 27, 2017
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Fix possible NullPointerException when retry in send Async way
上级
15af63e2
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
14 addition
and
8 deletion
+14
-8
client/src/main/java/org/apache/rocketmq/client/impl/MQClientAPIImpl.java
...java/org/apache/rocketmq/client/impl/MQClientAPIImpl.java
+14
-8
未找到文件。
client/src/main/java/org/apache/rocketmq/client/impl/MQClientAPIImpl.java
浏览文件 @
01a0eb00
...
...
@@ -438,34 +438,40 @@ public class MQClientAPIImpl {
)
{
int
tmp
=
curTimes
.
incrementAndGet
();
if
(
needRetry
&&
tmp
<=
timesTotal
)
{
MessageQueue
tmpmq
=
producer
.
selectOneMessageQueue
(
topicPublishInfo
,
brokerName
);
String
addr
=
instance
.
findBrokerAddressInPublish
(
tmpmq
.
getBrokerName
());
String
retryBrokerName
=
brokerName
;
//by default, it will send to the same broker
if
(
topicPublishInfo
!=
null
)
{
//select one message queue accordingly, in order to determine which broker to send
MessageQueue
mqChosen
=
producer
.
selectOneMessageQueue
(
topicPublishInfo
,
brokerName
);
retryBrokerName
=
mqChosen
.
getBrokerName
();
}
String
addr
=
instance
.
findBrokerAddressInPublish
(
retryBrokerName
);
log
.
info
(
"async send msg by retry {} times. topic={}, brokerAddr={}, brokerName={}"
,
tmp
,
msg
.
getTopic
(),
addr
,
tmpmq
.
getBrokerName
()
);
retryBrokerName
);
try
{
request
.
setOpaque
(
RemotingCommand
.
createNewRequestId
());
sendMessageAsync
(
addr
,
tmpmq
.
getBrokerName
()
,
msg
,
timeoutMillis
,
request
,
sendCallback
,
topicPublishInfo
,
instance
,
sendMessageAsync
(
addr
,
retryBrokerName
,
msg
,
timeoutMillis
,
request
,
sendCallback
,
topicPublishInfo
,
instance
,
timesTotal
,
curTimes
,
context
,
producer
);
}
catch
(
InterruptedException
e1
)
{
onExceptionImpl
(
tmpmq
.
getBrokerName
()
,
msg
,
timeoutMillis
,
request
,
sendCallback
,
topicPublishInfo
,
instance
,
timesTotal
,
curTimes
,
e1
,
onExceptionImpl
(
retryBrokerName
,
msg
,
timeoutMillis
,
request
,
sendCallback
,
topicPublishInfo
,
instance
,
timesTotal
,
curTimes
,
e1
,
context
,
false
,
producer
);
}
catch
(
RemotingConnectException
e1
)
{
producer
.
updateFaultItem
(
brokerName
,
3000
,
true
);
onExceptionImpl
(
tmpmq
.
getBrokerName
()
,
msg
,
timeoutMillis
,
request
,
sendCallback
,
topicPublishInfo
,
instance
,
timesTotal
,
curTimes
,
e1
,
onExceptionImpl
(
retryBrokerName
,
msg
,
timeoutMillis
,
request
,
sendCallback
,
topicPublishInfo
,
instance
,
timesTotal
,
curTimes
,
e1
,
context
,
true
,
producer
);
}
catch
(
RemotingTooMuchRequestException
e1
)
{
onExceptionImpl
(
tmpmq
.
getBrokerName
()
,
msg
,
timeoutMillis
,
request
,
sendCallback
,
topicPublishInfo
,
instance
,
timesTotal
,
curTimes
,
e1
,
onExceptionImpl
(
retryBrokerName
,
msg
,
timeoutMillis
,
request
,
sendCallback
,
topicPublishInfo
,
instance
,
timesTotal
,
curTimes
,
e1
,
context
,
false
,
producer
);
}
catch
(
RemotingException
e1
)
{
producer
.
updateFaultItem
(
brokerName
,
3000
,
true
);
onExceptionImpl
(
tmpmq
.
getBrokerName
()
,
msg
,
timeoutMillis
,
request
,
sendCallback
,
topicPublishInfo
,
instance
,
timesTotal
,
curTimes
,
e1
,
onExceptionImpl
(
retryBrokerName
,
msg
,
timeoutMillis
,
request
,
sendCallback
,
topicPublishInfo
,
instance
,
timesTotal
,
curTimes
,
e1
,
context
,
true
,
producer
);
}
}
else
{
if
(
context
!=
null
)
{
context
.
setException
(
e
);
context
.
getProducer
().
executeSendMessageHookAfter
(
context
);
}
try
{
sendCallback
.
onException
(
e
);
}
catch
(
Exception
ignored
)
{
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录