[
https://issues.apache.org/jira/browse/ARTEMIS-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110368#comment-15110368
]
ASF GitHub Bot commented on ARTEMIS-350:
----------------------------------------
GitHub user andytaylor opened a pull request:
https://github.com/apache/activemq-artemis/pull/334
ARTEMIS-350 - add timeout to avoid deadlock
https://issues.apache.org/jira/browse/ARTEMIS-350
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andytaylor/activemq-artemis master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/334.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #334
----
commit a24dc5b61aec4c0bf71173056915a09187c216ea
Author: Andy Taylor <andy.tayl...@gmail.com>
Date: 2016-01-21T10:02:24Z
ARTEMIS-350 - add timeout to avoid deadlock
https://issues.apache.org/jira/browse/ARTEMIS-350
----
> possible OOM in replication manager
> -----------------------------------
>
> Key: ARTEMIS-350
> URL: https://issues.apache.org/jira/browse/ARTEMIS-350
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Andy Taylor
> Assignee: Andy Taylor
> Fix For: 1.3.0
>
>
> This is becausee we have no flow control, we need to throttle back when the
> channel is not writable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
