Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 29825 invoked from network); 26 Aug 2010 08:43:40 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Aug 2010 08:43:40 -0000 Received: (qmail 20138 invoked by uid 500); 26 Aug 2010 08:43:40 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 19971 invoked by uid 500); 26 Aug 2010 08:43:37 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 19963 invoked by uid 99); 26 Aug 2010 08:43:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Aug 2010 08:43:36 +0000 X-ASF-Spam-Status: No, hits=2.3 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_SOFTFAIL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of michaelcouck@hotmail.com does not designate 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Aug 2010 08:43:31 +0000 Received: from jim.nabble.com ([192.168.236.80]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1OoY3C-0003iU-K1 for dev@openjpa.apache.org; Thu, 26 Aug 2010 01:43:10 -0700 Date: Thu, 26 Aug 2010 01:43:10 -0700 (PDT) From: "michael.couck" To: dev@openjpa.apache.org Message-ID: <1282812190530-5464778.post@n2.nabble.com> In-Reply-To: References: <1282637241123-5455918.post@n2.nabble.com> Subject: Re: Memory leak MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Kevin, Thanks for the quick response! You are right, I am using the runtime enhancement, and I know that it is not recommended, but I just find it cleaner. We are in a performance testing phase at the moment so I can't fiddle with the configuration right now, but I will get round to setting the JavaAgent on the command line and re-testing for a leak. Adding enhancement at build time is not an option as we do all sorts of other stuff and I am pretty sure this will create it's own issues. In any case I don't think anyone will hit this any time soon so no problem there. Cheers and thanks, Michael -- View this message in context: http://openjpa.208410.n2.nabble.com/Memory-leak-tp5455918p5464778.html Sent from the OpenJPA Developers mailing list archive at Nabble.com.