I think this message is better suited for the developers. It seemed a bit over the heads of the users list.
-----Original Message----- From: Leone, James Sent: Monday, August 04, 2003 8:08 PM To: '[EMAIL PROTECTED]' Subject: memory leak with large POST We're a few days from pushing a Struts based application to production. One of our clever QA created a simple Perl script which assembles a POST with one very large parameter (80k) and calls the front page of our application. The front page action does not use an actionform nor does it examine the large parameter in any way; however, after so many serialized calls from this script, we experienced out of memory errors. We did a lot of customizing on Struts, so to narrow down where the code was I deploy the struts-example.war. I pointed the same script to /struts-example/tour.do Again the parameter is not used by this action, but in the same number of requests this caused an out of memory error. All of this was done running Weblogic 7.0 SP 1. To further determine the problem, I ran the struts-example application in Tomcat. In a similar amount of time, down she went. Has anybody run tests of this nature? Any ideas why the gc is not collecting it's due memory. No...this is not a session thing. I've run other apps that do not use Struts, but do use sessions, and they stood strong. Smaller sized POSTs have revealed a similar memory problem, it just takes longer to surface. Right now I'm using hprof to investigate further. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
