Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 53748 invoked from network); 2 Feb 2009 08:58:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Feb 2009 08:58:00 -0000 Received: (qmail 40292 invoked by uid 500); 2 Feb 2009 08:58:00 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 40266 invoked by uid 500); 2 Feb 2009 08:58:00 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 40255 invoked by uid 99); 2 Feb 2009 08:58:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 00:58:00 -0800 X-ASF-Spam-Status: No, hits=-2.8 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [194.138.12.131] (HELO mxs1.siemens.at) (194.138.12.131) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 08:57:45 +0000 Received: from vies1k7x.sie.siemens.at ([158.226.129.83]) by mxs1.siemens.at with ESMTP id n128vN6S027482 for ; Mon, 2 Feb 2009 09:57:23 +0100 Received: from nets139a.ww300.siemens.net ([192.168.217.3]) by vies1k7x.sie.siemens.at (8.12.11.20060308/8.12.1) with ESMTP id n128vMgh016341 for ; Mon, 2 Feb 2009 09:57:23 +0100 Received: from nets13ja.ww300.siemens.net ([158.226.250.79]) by nets139a.ww300.siemens.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Feb 2009 09:57:21 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C98514.424C119E" Subject: Memory leak? Date: Mon, 2 Feb 2009 09:57:18 +0100 Message-ID: <30DB6ACF50A0A3439F39EFEB1C52E16607A9D994@nets13ja.ww300.siemens.net> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Memory leak? Thread-Index: AcmEuUYga1tkg5GpTa2UZbr3JQtchwAWqBpA References: <68f4a0e80901261814t41685e72y880e675310b3bfe0@mail.gmail.com> <68f4a0e80901270431o7bfeb8d9q7eae57d7dd43c726@mail.gmail.com> <30DB6ACF50A0A3439F39EFEB1C52E166078F22BA@nets13ja.ww300.siemens.net> <68f4a0e80902010922n225e5ffbx1483a8203c7d438e@mail.gmail.com> <30DB6ACF50A0A3439F39EFEB1C52E166078F22BE@nets13ja.ww300.siemens.net> From: "Hirsch, Richard" To: X-OriginalArrivalTime: 02 Feb 2009 08:57:21.0999 (UTC) FILETIME=[4299DDF0:01C98514] X-purgate: clean X-purgate: This mail is considered clean X-purgate-type: clean X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net X-purgate-ID: 149917::090202095723-0B9D8BA0-603F5662/0-0/0-15 X-purgate-size: 280589/0 X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C98514.424C119E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Do we have a memory leak somewhere? Take a look at the process memory at the stax site. There are no TCP connections but process memory keeps on increasing. D.=20 ------_=_NextPart_001_01C98514.424C119E--