Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 983EC10996 for ; Mon, 2 Dec 2013 08:40:44 +0000 (UTC) Received: (qmail 59517 invoked by uid 500); 2 Dec 2013 08:40:41 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 59246 invoked by uid 500); 2 Dec 2013 08:40:38 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 59215 invoked by uid 99); 2 Dec 2013 08:40:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Dec 2013 08:40:38 +0000 Date: Mon, 2 Dec 2013 08:40:38 +0000 (UTC) From: "matteo rulli (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (AMQ-4889) ProxyConnector memory usage skyrockets when several ssl handshakes fails MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836369#comment-13836369 ] matteo rulli edited comment on AMQ-4889 at 12/2/13 8:39 AM: ------------------------------------------------------------ Still an issue in long-term memory consumption due to another bug in ProxyConnector: missing equals and hashCode methods in ProxyConnections induced a memory leakeage in connections collection inside ProxyConnector. I added another patch to solve also this issue. was (Author: matteor): Still an issue in long-term memory consumption due to another bug in ProxyConnector: missing equals and hashCode methods in ProxyConnections induced a memory leakeage in connections collection inside ProxyConnector. Added another patch to solve also this issue. > ProxyConnector memory usage skyrockets when several ssl handshakes fails > ------------------------------------------------------------------------ > > Key: AMQ-4889 > URL: https://issues.apache.org/jira/browse/AMQ-4889 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.8.0, 5.9.0 > Environment: Seen in Windows 7 64bit, Windows Server 2008 R2 and Linux RHEL 6.3 64 bit > Reporter: matteo rulli > Attachments: NIOSSLTransport_patch_AMQ_4889.txt, ProxyConnIssue.rar, ProxyConnection_patch_AMQ_4889.txt, ProxyConnector_patch_AMQ_4889.txt, after_lsof.txt, after_netstat.txt, lsof.txt, netstat.txt, sockstat.txt > > > See [nabble|http://activemq.2283324.n4.nabble.com/Proxy-Connector-memory-consumption-td4674255.html] for further details. > To reproduce the issue: > # Start embedded proxy broker and the AMQ broker that are embedded in *AMQTestBroker* project (see attachments); > # Start the *AMQTestConsumer* project; This program repeatedly tries opening a connection to the ProxyConnector with wrong certificates. > # Open jconsole to monitor AMQTestBroker memory usage: you should experience an OOM error within one hour with the suggested settings (Xmx = 2048m). > Launch configurations and test keystores are attached to this issue along with the java projects. > This behavior seems to affect _ProxyConnector_ only, running the test against a standard nio-based _TransportConnector_ does not seem to produce anomalous memory consumptions. -- This message was sent by Atlassian JIRA (v6.1#6144)