Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 85831 invoked from network); 22 Dec 2005 13:05:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Dec 2005 13:05:58 -0000 Received: (qmail 75478 invoked by uid 500); 22 Dec 2005 13:05:57 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 75464 invoked by uid 500); 22 Dec 2005 13:05:56 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 75453 invoked by uid 99); 22 Dec 2005 13:05:56 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Dec 2005 05:05:56 -0800 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=DNS_FROM_RFC_POST,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [199.244.214.30] (HELO iron03.kdc.capitalone.com) (199.244.214.30) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Dec 2005 05:05:55 -0800 Received: from unknown (HELO KDCP4PIMS02.cof.ds.capitalone.com) ([10.4.100.53]) by iron03.kdc.capitalone.com with ESMTP; 22 Dec 2005 08:05:34 -0500 X-IronPort-AV: i="3.99,283,1131339600"; d="scan'208,217"; a="20619102:sNHT28829092" Received: from KDCP4PBHD01.cof.ds.capitalone.com ([10.4.100.50]) by KDCP4PIMS02.cof.ds.capitalone.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Dec 2005 08:05:34 -0500 Received: from KDCP4PMBX03.cof.ds.capitalone.com ([10.4.100.42]) by KDCP4PBHD01.cof.ds.capitalone.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Dec 2005 08:05:33 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C606F8.64F4CB84" X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: RE: Memory leaks Date: Thu, 22 Dec 2005 08:05:34 -0500 Message-ID: <45E26618E6D0D74CA16839B00E0C981402C011A4@KDCP4PMBX03.cof.ds.capitalone.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Memory leaks Thread-Index: AcYGFDPlh/tzYR5FTpWvdTBA8DWf2gA4xJOQ From: "Stettler, Robert" To: "Apache AXIS C User List" X-OriginalArrivalTime: 22 Dec 2005 13:05:33.0404 (UTC) FILETIME=[647A71C0:01C606F8] 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_01C606F8.64F4CB84 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" When you say parser layer, do you mean the way Axis' uses the parser is causing leaks, or the parser itself it leaking? I am using Xerces parser myself in my code and if it is leaking it is very slow. I ran a loop for 5 minute or so and no leak showed up. When I run the axis sample in a loop the leak is constant and shows up quickly and does not level off. It leaks more the larger the response document is which makes sense if guess if it is in the parser layer. -----Original Message----- From: John Hawkins [mailto:HAWKINSJ@uk.ibm.com] Sent: Wednesday, December 21, 2005 4:49 AM To: Apache AXIS C User List Subject: Re: Memory leaks We are aware that we have some memory leaks in xerces parser layer. Please also be aware that the memory model has changed substantially in 1.6 and that this release should have far fewer leaks. "Stettler, Robert" 21/12/2005 02:24 Please respond to "Apache AXIS C User List" To "Apache AXIS C User List" cc Subject Memory leaks I am using 1.5 final. It seems to be leaking. I am deleting objects returned by generated stubs and I delete the Soap object when I am done with it. Is there any other clean up that is required? The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. ------_=_NextPart_001_01C606F8.64F4CB84 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="us-ascii"

When you say parser layer, do you mean the way Axis’ uses the parser is causing leaks, or the parser itself it leaking?  I am using Xerces parser myself in my code and if it is leaking it is very slow.  I ran a loop for 5 minute or so and no leak showed up.

 

When I run the axis sample in a loop the leak is constant and shows up quickly and does not level off.  It leaks more the larger the response document is which makes sense if guess if it is in the parser layer.

 

 

-----Original Message-----
From: John Hawkins [mailto:HAWKINSJ@uk.ibm.com]
Sent: Wednesday, December 21, 2005 4:49 AM
To: Apache AXIS C User List
Subject: Re: Memory leaks

 


We are aware that we have some memory leaks in xerces parser layer. Please also be aware that the memory model has changed substantially in 1.6 and that this release should have far fewer leaks.



"Stettler, Robert" <robert.stettler@capitalone.com>

21/12/2005 02:24

Please respond to
"Apache AXIS C User List"

To

"Apache AXIS C User List" <axis-c-user@ws.apache.org>

cc

 

Subject

Memory leaks

 

 

 




I am using 1.5 final.  It seems to be leaking.  I am deleting objects returned by generated stubs and I delete the Soap object when I am done with it.  Is there any other clean up that is required?








The information contained in this e-mail is confidential and/or proprietary

to Capital One and/or its affiliates. The information transmitted herewith

is intended only for use by the individual or entity to which it is

addressed.  If the reader of this message is not the intended recipient,

you are hereby notified that any review, retransmission, dissemination,

distribution, copying or other use of, or taking of any action in reliance

upon this information is strictly prohibited. If you have received this

communication in error, please contact the sender and delete the material

from your computer.








The information contained in this e-mail is confidential and/or proprietary

to Capital One and/or its affiliates. The information transmitted herewith

is intended only for use by the individual or entity to which it is 

addressed.  If the reader of this message is not the intended recipient, 

you are hereby notified that any review, retransmission, dissemination, 

distribution, copying or other use of, or taking of any action in reliance 

upon this information is strictly prohibited. If you have received this 

communication in error, please contact the sender and delete the material 

from your computer.
------_=_NextPart_001_01C606F8.64F4CB84--