Thank you for your response! Alright, I will make all the objects placed on httpSession serializable. Coming from a commercial app server environment, we were spoiled by it's ability to simply igore these objects on the session, not forwarding them to other cluster member nodes.
So, if we are throwing errors in production that might go to the Console, running in Windows 2003 as a Service, and redirecting the "out" and "err" to a file, are we accumulating memory simply because of the console output ? If so is there a way to flush this periodically? Or, is it that errors thrown up this high into the console have components that get added to some collection and therefore won't get garbage collected ? Also, not that it should be our first line of defence, but to prevent excessive console messages, is there a way to catch the errors thrown from httpSession Clustering ? Bob View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3881814#3881814 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3881814 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
