I am really surprised. I observed on the site (when the project started) that they planned to use SAX to improve performance. But the memory graph shows that it is indeed using a lot of memory.
Abhinav Maheshwari -----Original Message----- From: Matt Munz [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 9:50 PM To: [EMAIL PROTECTED] Subject: RE: Axis 1.1 Memory leaks Luciano, Thanks. To any devs out there - would you mind saving us a bit of time? How does this part of the architecture work? - Matt ________________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 11:10 AM To: [EMAIL PROTECTED] Subject: RE: Axis 1.1 Memory leaks No, Matt I did not verify against the code. I planned to do some JProbe analysis but I did not find the time yet. Luciano -----Original Message----- From: Matt Munz [mailto:[EMAIL PROTECTED] Sent: Wednesday 25 February 2004 17:08 To: [EMAIL PROTECTED] Subject: RE: Axis 1.1 Memory leaks Luciano, Have you verified this by looking at the code? I haven't had the time to do that yet. If Axis is building the DOM before writing to the socket, I really want to know why. - Matt ________________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 10:24 AM To: [EMAIL PROTECTED] Subject: RE: RE: Axis 1.1 Memory leaks Hi Matt, > Intuitively, and perhaps naively, I find it hard to understand the extent of the memory ramp-up. It almost > appears as if the entire DOM is being built before writing to the socket begins? This couldn't be the > case,right? I'm afraid it is the case. I really don't see any other reason why Axis should fail when it receives a large xml document with an OutOfMemoryException. Luciano -----Original Message----- From: Matt Munz [mailto:[EMAIL PROTECTED] Sent: Wednesday 25 February 2004 16:13 To: [EMAIL PROTECTED] Subject: RE: Axis 1.1 Memory leaks Hi all, I am also having memory issues with large messages in Axis. Are there any unit tests that address this issue? It seems to me that performance is very important for Axis, and that excessive memory use is highly undesirable. For sure, the (approximate) memory consumption-to-message size ratio should be available in the documentation. For my purposes, it is as important as the SOAP compatibility measurements, since I have little use for features that are too expensive for me to employ. Intuitively, and perhaps naively, I find it hard to understand the extent of the memory ramp-up. It almost appears as if the entire DOM is being built before writing to the socket begins? This couldn't be the case, right? - Matt -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 7:29 AM To: [EMAIL PROTECTED] Subject: Réf. : RE: Axis 1.1 Memory leaks Hi, I see your message and this url. Is it possible to know what are the xml parsers you have used to reduce objects in memory... We have the same problems with Xerces! Thanks for your answer, Thierry > A year or so ago we ran into a problem like this, but it wasn't with > Axis - it was Xerces. A change of parser massively reduced the number of > objects being created and destroyed, and greatly improved performance > (this parser wouldn't do you any good, we wrote it to specifically solve > this problem and had complete control over the XML being parsed). You > might want to try Axis with a different parser. > Hi Ian, > increasing the heap size is a risky solution in my opinion, because (at least in my case) > I will never know when the memory will be enough to handle my large xml document. > I believe that there is some inefficiency in Axis code when it comes to handle > large xml documents. In the next days I will perform some JProbe checking to see > which component is eating all the memory. > Check out this thread: > http://marc.theaimsgroup.com/?l=axis-user&m=104513273521082&w=2 > Luciano Les informations contenues dans ce message sont confidentielles et peuvent constituer des informations privilegiees. Si vous n etes pas le destinataire de ce message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d en utiliser tout ou partie. Si vous avez recu ce message par erreur, merci de le supprimer de votre systeme, ainsi que toutes ses copies, et d en avertir immediatement l expediteur par message de retour.... Il est impossible de garantir que les communications par messagerie electronique arrivent en temps utile, sont securisees ou denuees de toute erreur ou virus. En consequence, l expediteur n accepte aucune responsabilite du fait des erreurs ou omissions qui pourraient en resulter. --- ----------------------------------------------------- --- The information contained in this e-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return e-mail. E-mail communications cannot be guaranteed to be timely secure, error or virus-free. The sender does not accept liability for any errors or omissions which arise as a result. Any e-mail message from the European Central Bank (ECB) is sent in good faith but shall neither be binding nor construed as constituting a commitment by the ECB except where provided for in a written agreement. This e-mail is intended only for the use of the recipient(s) named above. Any unauthorised disclosure, use or dissemination, either in whole or in part, is prohibited. If you have received this e-mail in error, please notify the sender immediately via e-mail and delete this e-mail from your system.
