DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22207>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22207 serialization and deserialization Summary: serialization and deserialization Product: Struts Version: 1.1 Final Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: Controller AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] As described in mail thread with subject: Memory consumption 1.1 b3 vs. 1.1 final. When serializating a form from the session scope it also serializes the moduleConfig. This causes a large nr of modulConfigs to be saved, unessesarily. This causes problems in enviroments that messure memory consumption per session by serializing. And it causes unessesary data to be replicated to other servers in a cluster enviroment. Solution? By declaring the moduleConfig variable in org.apache.struts.config.ActionFormConfig transient the config isn't serialized. This _might_ cause other issues when deserializing again. Obviously there is a need for a sustainable solution. I'm unfortunatly unable to submit a patch at this time. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
