Hi Claus You can use session passivation if your servlet engine / application server supports this. The application server then passivates HTTP sessions that have been idle for a specified amount of time and re-activates them on demand.
As the application server uses serialization in order to passivate the session state, you need to make sure that all your application classes are serializable (the ULC framework classes are). Cheers Rolf ************************************** Rolf Pfenninger Canoo Engineering AG Kirschgartenstrasse 7 CH-4051 Basel Tel +41 61 228 9444 Fax +41 61 228 9449 mailto:[EMAIL PROTECTED] http://www.canoo.com ULC - Rich Clients for J2EE http://www.canoo.com/ulc ************************************** -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Mittwoch, 25. Oktober 2006 09:41 To: [EMAIL PROTECTED] Subject: [ULC-developer] Controlled shutdown of ULC Connections to reduce server (memory) load ? Hi all, let me sketch briefly the problem scenario: There is a heavy loaded server. Users start applications to have them quickly available, but many of them are idle most of the time. Could somebody think of a way to init controlled connection shutdown if an application instance is idle too long ? Of course that would have to include features like to save the application's current state and data before shutting it down. Any help appreciated. best regards, C.J.Seitter MÜNCHENER VEREIN http://www.muenchener-verein.de Versicherungsgruppe [EMAIL PROTECTED] Pettenkoferstraße 19 D-80336 München Tel.: 089/5152-1073 Fax 089/5152-3073 _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer
