RE: Memory leaks

[Stettler, Robert]

Gotcha.  Thanks.   -----Original Message----- From: John Hawkins [mailto:[EMAIL PROTECTED] Sent: Thursday, December 22, 2005 8:12 AM To: Apache AXIS C User List Subject: RE: Memory leaks   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" <[EMAIL PROTECTED]> 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 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:[EMAIL PROTECTED] 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" <[EMAIL PROTECTED]> 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. 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.