Hello, what is the effect of this memory leak. We are using Axis 1.0 in production without having any problems. Can you tell me more ? thanx, benjamin
-----Ursprüngliche Nachricht----- Von: Davanum Srinivas [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 26. August 2005 15:18 An: axis-user@ws.apache.org Betreff: Re: [Axis1] Axis Memory Leak Please switch to Axis 1.2.1. No you can't replace the jar. you need to regen the server and client. "Axis 1.0 jar used on a client work with the Axis 1.2.1 server" may work but it depends if there was a bug in the exact scenario you are using. -- dims On 8/26/05, Hoying, Ken <[EMAIL PROTECTED]> wrote: > > > > We are having issues with a slow memory leak that is resulting in > OutOfMemory errors in our production environment after about 3 days time. > We are currently using Axis 1.0. After profiling the application with > OptimizeIt, it appears that there is a memory leak that seems to be tied to > the following: > > > org.apache.axis.Message.getSOAPEnvelope() > > Can anyone confirm that this was a known memory leak and it is have been > fixed in a subsequent release of Axis? > > I am also curious to know what implications would arise from switching to > Axis 1.2.1. Can I just replace the jar or do I need to regen class and > clients? Does the Axis 1.0 jar used on a client work with the Axis 1.2.1 on > the server? > > Thank you, > Ken Hoying > > ************************************************************** > This message, including any attachments, contains confidential information > intended for a specific individual and purpose, and is protected by law. If > you are not the intended recipient, please contact sender immediately by > reply e-mail and destroy all copies. You are hereby notified that any > disclosure, copying, or distribution of this message, or the taking of any > action based on it, is strictly prohibited. > TIAA-CREF > ************************************************************** > -- Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform
