[
https://issues.apache.org/jira/browse/APEXCORE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205035#comment-15205035
]
ASF GitHub Bot commented on APEXCORE-398:
-----------------------------------------
GitHub user vrozov opened a pull request:
https://github.com/apache/incubator-apex-core/pull/279
APEXCORE-398 - Ack may not be delivered from buffer server to it's client
@PramodSSImmaneni Please review and cherry-pick into all affected branches.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vrozov/incubator-apex-core APEXCORE-398
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-apex-core/pull/279.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 #279
----
commit d8416f7e00af56df6000e1be1c143b0e18baaf61
Author: Vlad Rozov <[email protected]>
Date: 2016-03-21T20:22:58Z
APEXCORE-398 - Ack may not be delivered from buffer server to it's client
----
> Ack may not be delivered from buffer server to it's client
> ----------------------------------------------------------
>
> Key: APEXCORE-398
> URL: https://issues.apache.org/jira/browse/APEXCORE-398
> Project: Apache Apex Core
> Issue Type: Bug
> Affects Versions: 3.2.0, 3.3.0, 3.2.1, 3.4.0, 3.3.1
> Reporter: Vlad Rozov
> Assignee: Vlad Rozov
>
> When buffer server receives and processes purge/reset requests from an
> application master it puts ack to AbstractClient write queue. This queue may
> not necessarily be flushed and message delivered to the Application master.
> If message sits in the queue and is not delivered, connection stays open
> leading to resource leaks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
