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
RE: [Axis1] Axis Memory Leak
Regenerating the clients is going to be very difficult. We have several spread throughout the organization and already in production. I am disappointed to hear that the client version is so tightly integrated to the server version. Seems like this sort of defeats the goals and benefits of a web service based SOA. I will start taking a look at making the switch, but can someone confirm that there was such a bug or leak that was addresses in the 1.2.1 version. I would hate to make this change, especially due to the potentially large impact to the organization, if it does not fix the problem. Thanks, Ken -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 9:18 AM To: axis-user@ws.apache.org Subject: 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 ** 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 **
RE: [Axis1] Axis Memory Leak
We are currently running out of memory in production after about three days. However, this is not our only memory leak. We are also working on revolving a leak we seem to be having in XALAN with a transform. The XALAN leak is definitely the larger of the two. Currently, we are avoiding the problem by restarting the server daily. However, this is not an acceptable solution for the long term. -Original Message- From: Benjamin Marcel Flohr [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 9:22 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: AW: [Axis1] Axis Memory Leak 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 ** 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 **
RE: [Axis1] Axis Memory Leak
Name: org/apache/xerces/impl/Version.class Comment: Xerces-J 2.6.2 Implementation-Title: org.apache.xerces.impl.Version Implementation-Version: 2.6.2 Implementation-Vendor: Apache Software Foundation Implementation-URL: http://xml.apache.org/xerces2-j/ Name: org/xml/sax/ Comment: based on xml-commons external 1.2.01 Specification-Title: Simple API for XML Specification-Vendor: David Megginson Specification-Version: 2.0.1 Implementation-Title: org.xml.sax Implementation-Version: 2.0.1 Implementation-Vendor: David Megginson Implementation-URL: http://www.saxproject.org/ Name: org/w3c/dom/ Comment: based on xml-commons external 1.2.01 Specification-Title: Document Object Model, Level 2 Core Specification-Vendor: World Wide Web Consortium Specification-Version: 1.0 Implementation-Title: org.w3c.dom Implementation-Version: 1.0 Implementation-Vendor: World Wide Web Consortium Implementation-URL: http://www.w3c.org/DOM/ Name: javax/xml/parsers/ Comment: based on xml-commons external 1.2.01 Specification-Title: Java API for XML Processing Specification-Version: 1.2 Specification-Vendor: Sun Microsystems Inc. Implementation-Title: javax.xml.parsers Implementation-Version: 1.2.01 Implementation-Vendor: Sun Microsystems Inc. Implementation-URL: http://java.sun.com/xml/jaxp.html Name: javax/xml/transform/ Comment: based on xml-commons external 1.2.01 Specification-Title: Java API for XML Processing Specification-Version: 1.2 Specification-Vendor: Sun Microsystems Inc. Implementation-Title: javax.xml.transform Implementation-Version: 1.2.01 Implementation-Vendor: Sun Microsystems Inc. Implementation-URL: http://java.sun.com/xml/jaxp.html Name: org/apache/xerces/xni/ Comment: Xerces Native Interface Specification-Title: Xerces Native Interface Specification-Version: 1.1 Specification-Vendor: Apache Software Foundation Implementation-Title: org.apache.xerces.xni Implementation-Version: 1.1 Implementation-Vendor: Apache Software Foundation Implementation-URL: http://xml.apache.org/xerces2-j/ Manifest-Version: 1.0 Created-By: 1.3.1 (IBM Corporation) Main-Class: org.apache.xalan.xslt.Process Class-Path: xercesImpl.jar xml-apis.jar Name: org/apache/xalan Comment: Main Xalan engine implementing TrAX/JAXP Specification-Title: Java API for XML Processing Specification-Vendor: Sun Microsystems Inc. Specification-Version: 1.2 Implementation-Title: org.apache.xalan Implementation-Version: 2.6.0 Implementation-Vendor: Apache Software Foundation Implementation-URL: http://xml.apache.org/xalan-j/dist/ Name: org/apache/xpath Comment: XPath engine Implementation-Title: org.apache.xpath Implementation-Version: 2.6.0 Implementation-Vendor: Apache Software Foundation Implementation-URL: http://xml.apache.org/xalan-j/dist/ Name: org/apache/xml Comment: DTM implementation and utilities Implementation-Title: org.apache.xml Implementation-Version: 2.6.0 Implementation-Vendor: Apache Software Foundation Implementation-URL: http://xml.apache.org/xalan-j/dist/ Name: org/apache/xalan/xsltc Comment: Main XSLTC engine implementing TrAX/JAXP Specification-Title: Java API for XML Processing Specification-Vendor: Sun Microsystems Inc. Specification-Version: 1.2 Implementation-Title: org.apache.xalan.xsltc Implementation-Version: 2.6.0 Implementation-Vendor: Apache Software Foundation Implementation-URL: http://xml.apache.org/xalan-j/dist/ Name: runtime Comment: Runtime component of JCup Specification-Title: Runtime component of JCup Specification-Vendor: Princeton University Specification-Version: 0.10k Implementation-Title: runtime Implementation-Version: 2.6.0 Implementation-Vendor: Princeton University Implementation-URL: http://www.cs.princeton.edu/~appel/modern/java/CUP/ Name: org/apache/bcel Comment: Byte Code Engineering Library Specification-Title: Byte Code Engineering Library Specification-Vendor: Markus Dahm Specification-Version: 5.0 rc1 Implementation-Title: org.apache.bcel Implementation-Version: 2.6.0 Implementation-Vendor: Apache Software Foundation Implementation-URL: http://jakarta.apache.org/bcel Name: org/apache/regexp Comment: Java Regular Expression package Specification-Title: Java Regular Expression package Specification-Vendor: Apache Software Foundation Specification-Version: 1.2 Implementation-Title: org.apache.regexp Implementation-Version: 2.6.0 Implementation-Vendor: Apache Software Foundation Implementation-URL: http://jakarta.apache.org/regexp -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 9:35 AM To: axis-user@ws.apache.org Subject: Re: [Axis1] Axis Memory Leak Which version of xerces are u using? -- dims On 8/26/05, Hoying, Ken [EMAIL PROTECTED] wrote: We are currently running out of memory in production after about three days. However, this is not our only memory leak. We are also working on revolving a leak we seem to be having in XALAN with a transform. The XALAN leak is definitely the larger of the two. Currently
