No problem. I'm still investigating a remaining memory leak on the C++ broker on Windows, but that patch corrected most of it...
On Tue, Aug 28, 2012 at 2:49 PM, Chuck Rolke (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/QPID-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443451#comment-13443451] > > Chuck Rolke commented on QPID-4257: > ----------------------------------- > > Kerry, > > Thanks for posting the patch. I will give it some attention. > > Chuck > > > Windows+SSL: Client hang on broker close, broker memory leak > > ------------------------------------------------------------ > > > > Key: QPID-4257 > > URL: https://issues.apache.org/jira/browse/QPID-4257 > > Project: Qpid > > Issue Type: Bug > > Components: C++ Broker, C++ Client > > Affects Versions: 0.12, 0.13, 0.14, 0.15, 0.16, 0.17, 0.18, 0.19 > > Environment: Windows client on Windows 7, Windows broker on > Server 2K8, using SSL. > > Reporter: Kerry Bonin > > Labels: patch > > Fix For: 0.19 > > > > Attachments: windows_ssl_hang_r1377724.patch > > > > Original Estimate: 168h > > Remaining Estimate: 168h > > > > Windows clients hang when broker dies via SSL connection - fetch never > returns even w/ IMMEDIATE timeout. > > Windows broker memory grows linearly with SSL connection count, leak per > connection, until broker exhausts memory and crashes. > > -- > 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 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
