Yes, we did precisely that.
But the developers are running around asking "why?" For some reason they think that glassfish shouldn't be persisting their object and they want the systems admins to "fix it" via some sort of configuration setting.
I read on some blog that glassfish persists all sessions whenever an "asadmin stop-domain foo" is executed. It writes all objects to ".ser" files that are deleted upon restart. This may explain why stop-domain is so slow. Why does it do this?
Does this mean that a browser may not even notice a stop-domain / start-domain cycle?
I did see there is a setting in sun-web.xml that prevent this on individual applications.
[Message sent by forum member 'bryanut' (bryanut)]
http://forums.java.net/jive/thread.jspa?messageID=353323