You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Robert Joseph Evans (JIRA)" <ji...@apache.org> on 2012/10/27 00:05:12 UTC
[jira] [Created] (HADOOP-8986) Server$Call object is never released
after it is sent
Robert Joseph Evans created HADOOP-8986:
-------------------------------------------
Summary: Server$Call object is never released after it is sent
Key: HADOOP-8986
URL: https://issues.apache.org/jira/browse/HADOOP-8986
Project: Hadoop Common
Issue Type: Bug
Components: ipc
Affects Versions: 0.23.4, 2.0.2-alpha
Reporter: Robert Joseph Evans
Assignee: Robert Joseph Evans
Priority: Critical
When an IPC response cannot be returned without blocking the Server$Call object attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8986) Server$Call object is never
released after it is sent
Posted by "Suresh Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486402#comment-13486402 ]
Suresh Srinivas commented on HADOOP-8986:
-----------------------------------------
+1 for the patch. I feel it is unnecessary to add test for this.
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8986) Server$Call object is never
released after it is sent
Posted by "Daryn Sharp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486296#comment-13486296 ]
Daryn Sharp commented on HADOOP-8986:
-------------------------------------
Looks good. Did you investigate whether a test can be added to {{TestIPCServerResponder}}? It causes partial writes which may allow you to check if the response is null out after the call finally completes.
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8986) Server$Call object is never
released after it is sent
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487791#comment-13487791 ]
Hudson commented on HADOOP-8986:
--------------------------------
Integrated in Hadoop-Mapreduce-trunk #1242 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1242/])
HADOOP-8986. Server$Call object is never released after it is sent (bobby) (Revision 1403745)
Result = FAILURE
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1403745
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
> Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8986) Server$Call object is never
released after it is sent
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487726#comment-13487726 ]
Hudson commented on HADOOP-8986:
--------------------------------
Integrated in Hadoop-Hdfs-trunk #1212 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1212/])
HADOOP-8986. Server$Call object is never released after it is sent (bobby) (Revision 1403745)
Result = FAILURE
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1403745
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
> Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8986) Server$Call object is never
released after it is sent
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486980#comment-13486980 ]
Hudson commented on HADOOP-8986:
--------------------------------
Integrated in Hadoop-trunk-Commit #2943 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/2943/])
HADOOP-8986. Server$Call object is never released after it is sent (bobby) (Revision 1403745)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1403745
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
> Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8986) Server$Call object is never
released after it is sent
Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485238#comment-13485238 ]
Robert Joseph Evans commented on HADOOP-8986:
---------------------------------------------
This can save several hundred MB on an AM with many reduce tasks.
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
>
> When an IPC response cannot be returned without blocking the Server$Call object attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8986) Server$Call object is never released
after it is sent
Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Joseph Evans updated HADOOP-8986:
----------------------------------------
Attachment: HADOOP-8986.txt
There are no tests for this patch. I have tested it manually. All of the old functionality should still work, it is just that more memory will be released to be collected when a call finishes.
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8986) Server$Call object is never released
after it is sent
Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Joseph Evans updated HADOOP-8986:
----------------------------------------
Resolution: Fixed
Fix Version/s: 0.23.5
2.0.3-alpha
3.0.0
Status: Resolved (was: Patch Available)
Thanks Daryn and Suresh for the reviews.
I waited to check it in until I could run one more test to measure how much memory savings this had on my original test case. I ran a sleep job with 20,000 mappers and 3,000 reducers. This was on a cluster large enough and free enough that all of them could be running at the same time. The peek memory usage decreased from about 500MB to 285MB and the final heap as most of the reducers started to get close to completing dropped to 200MB, where as before it was still up at 500MB.
I put it into trunk, branch-2, and branch-0.23
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
> Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8986) Server$Call object is never released
after it is sent
Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Joseph Evans updated HADOOP-8986:
----------------------------------------
Description: When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data. (was: When an IPC response cannot be returned without blocking the Server$Call object attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.)
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8986) Server$Call object is never
released after it is sent
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487670#comment-13487670 ]
Hudson commented on HADOOP-8986:
--------------------------------
Integrated in Hadoop-Yarn-trunk #22 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/22/])
HADOOP-8986. Server$Call object is never released after it is sent (bobby) (Revision 1403745)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1403745
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
> Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8986) Server$Call object is never
released after it is sent
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486273#comment-13486273 ]
Hadoop QA commented on HADOOP-8986:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12551227/HADOOP-8986.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1685//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1685//console
This message is automatically generated.
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8986) Server$Call object is never
released after it is sent
Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486335#comment-13486335 ]
Robert Joseph Evans commented on HADOOP-8986:
---------------------------------------------
I didn't look that closely at adding in a test because I was mostly concerned that it did not break any existing functionality. I will look at TestIPCResponder to see if I can add something in there.
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8986) Server$Call object is never
released after it is sent
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487716#comment-13487716 ]
Hudson commented on HADOOP-8986:
--------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #421 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/421/])
svn merge -c 1403745 FIXES: HADOOP-8986. Server$Call object is never released after it is sent (bobby) (Revision 1403750)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1403750
Files :
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
> Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8986) Server$Call object is never released
after it is sent
Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Joseph Evans updated HADOOP-8986:
----------------------------------------
Status: Patch Available (was: Open)
> Server$Call object is never released after it is sent
> -----------------------------------------------------
>
> Key: HADOOP-8986
> URL: https://issues.apache.org/jira/browse/HADOOP-8986
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.23.4, 2.0.2-alpha
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Attachments: HADOOP-8986.txt
>
>
> When an IPC response cannot be returned without blocking an Server$Call object is attached to the SelectionKey of the write selector. However the call object is never removed from the SlectionKey. So for a connection that rarely has large responses but is long lived there is a lot of data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira