Good question. I've got a tool for quantifying its memory usage, but haven't done it yet. (The "just get it done" mentality pervades here at times.) I did have to increase the max heap size that Tomcat uses. (It was at 325Mb so just to be safe I increased it to 512Mb.)
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, November 01, 2004 6:38 AM To: [EMAIL PROTECTED] Subject: RE: Axis blows up in AbstractXMLEncoder when serializing a complex object array of over 1000 elements. How does this class perform in terms of Peak memory Usage when you are trying to send across 10-50 MB of Data using Webservice ? Thanks and Regards, Gary Grewal "Tami Wright" <[EMAIL PROTECTED] To: <[EMAIL PROTECTED]> yinc.com> cc: Subject: RE: Axis blows up in AbstractXMLEncoder when serializing 11/01/2004 02:15 a complex object array of over 1000 elements. AM Please respond to axis-user Okay, figured out the problem. A third-party commercial app (a service that my web-service is a client to) was returning munged data. There should not be this problem inside this app, so apparently the problem was not Axis' fault. I wrote a little utility class (using a couple of lines of code from the AbstractXMLEncoder inside of Axis) to do a check on my strings that are going on the wire to ensure that they are XML friendly so that they can be appropriately serialized/deserialized. If they aren't, this object makes thems so. Here is the code for anyone interested: /** * Created by IntelliJ IDEA. * User: ttwright * Date: Oct 31, 2004 * Time: 11:49:28 PM * To change this template use File | Settings | File Templates. */ public class XMLFriendlyString { public String getXMLFriendlyString(String unfriendlyString) { char[] characters = unfriendlyString.toCharArray(); char character; StringBuffer stringBuf = new StringBuffer(unfriendlyString.length()); for (int i = 0; i < characters.length; i++) { character = characters[i]; if (character < 0x20) character = ' '; stringBuf.append(character); } return stringBuf.toString(); } } -----Original Message----- From: Tami Wright [mailto:[EMAIL PROTECTED] Sent: Friday, October 29, 2004 3:40 PM To: [EMAIL PROTECTED] Subject: RE: Axis blows up in AbstractXMLEncoder when serializing a complex object array of over 1000 elements. Hi, Thanks for responding. I changed the heap size for Tomcat and shutdown TCPMon and am still getting the same error. Tami -----Original Message----- From: Greg Michalopoulos [mailto:[EMAIL PROTECTED] Sent: Friday, October 29, 2004 2:51 PM To: [EMAIL PROTECTED] Subject: RE: Axis blows up in AbstractXMLEncoder when serializing a complex object array of over 1000 elements. I found that tcpmon uses a lot of memory, so if you are using that you'll need to increase the heap size when starting tcpmon. -----Original Message----- From: Tami Wright [mailto:[EMAIL PROTECTED] Sent: Friday, October 29, 2004 4:35 PM To: [EMAIL PROTECTED] Subject: Axis blows up in AbstractXMLEncoder when serializing a complex object array of over 1000 elements. Hi All, Anyone ever had problems with Axis (1.2 beta) blowing up when trying to return a complex object containing an array of 1000 elements or so? I am and I wondered if it was a bug. If so, where do I go to file a bug report? Thanks, Tami This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates
