Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 91242 invoked from network); 22 Dec 2005 13:13:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Dec 2005 13:13:04 -0000 Received: (qmail 89143 invoked by uid 500); 22 Dec 2005 13:13:03 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 89126 invoked by uid 500); 22 Dec 2005 13:13:03 -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 89114 invoked by uid 99); 22 Dec 2005 13:13:02 -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:13:02 -0800 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of HAWKINSJ@uk.ibm.com designates 195.212.29.136 as permitted sender) Received: from [195.212.29.136] (HELO mtagate3.uk.ibm.com) (195.212.29.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Dec 2005 05:13:01 -0800 Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate3.uk.ibm.com (8.12.10/8.12.10) with ESMTP id jBMDC5Qg060490 for ; Thu, 22 Dec 2005 13:12:05 GMT Received: from d06av02.portsmouth.uk.ibm.com (d06av02.portsmouth.uk.ibm.com [9.149.37.228]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id jBMDC4cg234232 for ; Thu, 22 Dec 2005 13:12:05 GMT Received: from d06av02.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av02.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id jBMDC4lk001101 for ; Thu, 22 Dec 2005 13:12:04 GMT Received: from d06ml068.portsmouth.uk.ibm.com (d06ml068.portsmouth.uk.ibm.com [9.149.38.194]) by d06av02.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id jBMDC4oD001094 for ; Thu, 22 Dec 2005 13:12:04 GMT In-Reply-To: <45E26618E6D0D74CA16839B00E0C981402C011A4@KDCP4PMBX03.cof.ds.capitalone.com> To: "Apache AXIS C User List" MIME-Version: 1.0 Subject: RE: Memory leaks X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: John Hawkins X-MIMETrack: S/MIME Sign by Notes Client on John Hawkins/UK/IBM(Release 6.0.2CF1|June 9, 2003) at 22/12/2005 13:10:36, Serialize by Notes Client on John Hawkins/UK/IBM(Release 6.0.2CF1|June 9, 2003) at 22/12/2005 13:10:36, Serialize complete at 22/12/2005 13:10:36, S/MIME Sign failed at 22/12/2005 13:10:37: The cryptographic key was not found, Serialize by Router on D06ML068/06/M/IBM(Release 6.53HF247 | January 6, 2005) at 22/12/2005 13:12:04, Serialize complete at 22/12/2005 13:12:04 Message-ID: Date: Thu, 22 Dec 2005 13:12:02 +0000 Content-Type: multipart/alternative; boundary="=_alternative 004861C0802570DF_=" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multipart message in MIME format. --=_alternative 004861C0802570DF_= Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable I mean we think it's the way we use the parser i.e. we think it's our code = not xerces itself but we haven't done enough investigation ot confirm. "Stettler, Robert" =20 22/12/2005 13:05 Please respond to "Apache AXIS C User List" To "Apache AXIS C User List" cc Subject RE: Memory leaks When you say parser layer, do you mean the way Axis? uses the parser is=20 causing leaks, or the parser itself it leaking? I am using Xerces parser=20 myself in my code and if it is leaking it is very slow. I ran a loop for=20 5 minute or so and no leak showed up. =20 When I run the axis sample in a loop the leak is constant and shows up=20 quickly and does not level off. It leaks more the larger the response=20 document is which makes sense if guess if it is in the parser layer. =20 =20 -----Original Message----- From: John Hawkins [mailto:HAWKINSJ@uk.ibm.com]=20 Sent: Wednesday, December 21, 2005 4:49 AM To: Apache AXIS C User List Subject: Re: Memory leaks =20 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=20 that this release should have far fewer leaks.=20 "Stettler, Robert" =20 21/12/2005 02:24=20 Please respond to "Apache AXIS C User List" To "Apache AXIS C User List" =20 cc =20 Subject Memory leaks =20 =20 =20 I am using 1.5 final. It seems to be leaking. I am deleting objects=20 returned by generated stubs and I delete the Soap object when I am done=20 with it. Is there any other clean up that is required?=20 The information contained in this e-mail is confidential and/or=20 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=20 addressed. If the reader of this message is not the intended recipient,=20 you are hereby notified that any review, retransmission, dissemination,=20 distribution, copying or other use of, or taking of any action in reliance = upon this information is strictly prohibited. If you have received this=20 communication in error, please contact the sender and delete the material=20 from your computer. The information contained in this e-mail is confidential and/or=20 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=20 addressed. If the reader of this message is not the intended recipient,=20 you are hereby notified that any review, retransmission, dissemination,=20 distribution, copying or other use of, or taking of any action in reliance = upon this information is strictly prohibited. If you have received this=20 communication in error, please contact the sender and delete the material=20 from your computer. --=_alternative 004861C0802570DF_= Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
I mean we think it's the way we use the parser i.e. we think it's our code not xerces itself but we haven't done enough investigation ot confirm.




"Stettler, Rober= t" <robert.stettler@capitalone.com>

22/12/2005 13:05
Please respond to
"Apache AXIS C User List"
To
"Apache AXIS C User List" <axis-c-user@ws.apache.org>
cc
Subject
RE: Memory leaks=





When you say parser layer, do you mean the way Axis’ uses the parser is causing leaks, or the pa= rser 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, Rober= t" <robert.stettler@capitalone.com>

21/12/2005 02:24


Please respond to
"Apache AXIS C User List"
To
"Apach= e 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<= br>
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 recipien= t,

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<= br>
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 recipien= t,

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.

--=_alternative 004861C0802570DF_=--