[
https://issues.apache.org/jira/browse/THRIFT-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168729#comment-13168729
]
Bryan Duxbury commented on THRIFT-1457:
---------------------------------------
You could just implement another framed transport that discards buffers instead
of reuses them...
> Capacity of TframedTransport write buffer is never reset
> --------------------------------------------------------
>
> Key: THRIFT-1457
> URL: https://issues.apache.org/jira/browse/THRIFT-1457
> Project: Thrift
> Issue Type: Improvement
> Components: Java - Library
> Affects Versions: 0.6.1
> Reporter: Arthur Meyer
> Attachments: THRIFT-1457.patch
>
>
> The writeBuffer_ instance variable of TframedTransport can only grow and is
> never reset to its original capacity. This causes memory issues for clients
> using a connection pool.
> The size of this buffer grows to 16MB in our application. With a connection
> pool of 50 connections, this leads to a loss up to 800MB.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
