Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 42159 invoked from network); 14 Jul 2005 13:22:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Jul 2005 13:22:36 -0000 Received: (qmail 77378 invoked by uid 500); 14 Jul 2005 13:22:35 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 77335 invoked by uid 500); 14 Jul 2005 13:22:34 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Delivered-To: moderator for dev@directory.apache.org Received: (qmail 51665 invoked by uid 99); 13 Jul 2005 16:05:29 -0000 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=DNS_FROM_RFC_WHOIS,HTML_50_60,HTML_MESSAGE,RCVD_BY_IP X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C587C5.13061178" Subject: [mina] ByteBuffer allocation memory leak Date: Wed, 13 Jul 2005 18:08:14 +0200 Message-ID: <8DE3B7F7701E624B95DFA90DCB930D8707CD50@mailsrv.transwitch.co.za> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [mina] ByteBuffer allocation memory leak Thread-Index: AcWHxRL2RuSoURc6ST6m+DvANYgbUw== From: "Donovan Du Plessis" To: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------_=_NextPart_001_01C587C5.13061178 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Environment: Processing multiple xml message requests on multiple socket connections. Currently we are sending +/- 3000 xml requests per second to your MINA implementation (IoHandlerAdapter). Design: When data is read on the socket connection, it is passed to an object which breaks the data buffer down into individual packets. These 'packets' are then encoded and written back to the session. Symptoms: Memory leaking is occurring when a new ByteBuffer is allocated to store the 'packet'. e.g. ByteBuffer buffer_ =3D ByteBuffer.allocate(lengthOfPacket); We have used a java profiler to monitor the running application, and found a memory leak is occurring at the allocation point. Please could you advise us on how to overcome this problem, as the documentation states that the allocated buffer needs not be released, as MINA releases is automatically once a call is made to the IoSession write() method. Regards, Donovan ------_=_NextPart_001_01C587C5.13061178 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable [mina] ByteBuffer allocation memory leak

Environment:

Processing multiple xml message requests on multiple = socket connections. Currently we are sending +/- 3000 xml requests per = second to your MINA implementation (IoHandlerAdapter).

Design:

When data is read on the socket connection, it is = passed to an object which breaks the data buffer down into individual = packets.  These ‘packets’ are then encoded and written = back to the session.

Symptoms:

Memory leaking is occurring when a new ByteBuffer is = allocated to store the ‘packet’.

e.g. ByteBuffer buffer_ =3D = ByteBuffer.allocate(lengthOfPacket);

We = have used a java profiler to monitor the running application, and found = a memory leak is occurring at the allocation point.

Please could you advise us on how to overcome this = problem, as the documentation states that the allocated buffer needs not = be released, as MINA releases is automatically once a call is made to = the IoSession write() method.

Regards,

Donovan

------_=_NextPart_001_01C587C5.13061178--