Is this an issue because the session is being serialized? Maybe the reference to the struts config needs to be declared transient and be restored if the object is deserialized.
Brendan -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] Sent: Monday, July 28, 2003 1:20 PM To: Struts Users Mailing List Subject: RE: Memory consumption 1.1 b3 vs. 1.1 final On Mon, 28 Jul 2003, Maya Retzlaff wrote: > Date: Mon, 28 Jul 2003 21:19:19 +0200 > From: Maya Retzlaff <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: 'Struts Users Mailing List' <[EMAIL PROTECTED]> > Subject: RE: Memory consumption 1.1 b3 vs. 1.1 final > > Hi, > > Unfortunate no one replied. But I'll try again with more information. > > After a bit more debugging, when using the debugger see screen shot. > http://maya.retzlaff.se/debugScreenShot.png, sorry couldn't export to text. > Its a bit censored. > > This means that the whole struts-config.xml (a HashMap with 127 elements) is > saved in the session for every user when <action scope="session"> is set in > struts-config.xml. For us with the memory restrictions we face, the 50k that > the strutsconfig takes in memory is very severe. Why are you assuming that the memory is being duplicated? All of the references point to the one-and-only copy of the actual Config instances, in the collection that was built when the configuration file was first parsed. Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
