[
https://issues.apache.org/jira/browse/ROCKETMQ-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258371#comment-16258371
]
ASF GitHub Bot commented on ROCKETMQ-290:
-----------------------------------------
coveralls commented on issue #178: [ROCKETMQ-290] Fix memory leak in
WaitNotifyObject#waitingThreadTable
URL: https://github.com/apache/rocketmq/pull/178#issuecomment-345496888
[](https://coveralls.io/builds/14272196)
Coverage increased (+0.1%) to 38.92% when pulling
**32e212d07a586fcc477d0d455bb1a41b32c198f7 on Jason918:ROCKETMQ-290** into
**3a0451b286686199270adaa8d2252052c86eddbb on apache:master**.
----------------------------------------------------------------
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]
> Memory leaks in
> org.apache.rocketmq.store.ha.WaitNotifyObject#waitingThreadTable
> --------------------------------------------------------------------------------
>
> Key: ROCKETMQ-290
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-290
> Project: Apache RocketMQ
> Issue Type: Bug
> Components: rocketmq-store
> Affects Versions: 4.1.0-incubating
> Reporter: Jas0n918
> Assignee: yukon
> Priority: Critical
>
> There are only add-element operations for waitingThreadTable in Class
> org.apache.rocketmq.store.ha.WaitNotifyObject.
> Each time a new thread calls Method WaitNotifyObject#allWaitForRunning,
> waitingThreadTable get new element.
> This leak actually happens in Master Broker when Slave reconnect to the
> Master, a new HAConnection is created, and WaitNotifyObject#allWaitForRunning
> will be called in LogHAConnection.WriteSocketService#run.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
