hi, we terminate our application with ULCSession.currentSession().stopApplication();
regards Dejan mailto:[EMAIL PROTECTED] Wednesday, January 31, 2007, 8:27:26 PM, you wrote: JM> Hi Dejan, JM> When a ULC application is terminated (ApplicationContext.terminate()), its JM> session (ULCSession) is removed from the HTTPSession. Over and above this, JM> ULC does not interfere or invalidate the HTTPSession on termination of an JM> application because the HTTPSession may have stuff from other applications JM> running in the container. JM> How are you terminating your applications? JM> Thanks and regards, JM> Janak >>-----Original Message----- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] Behalf Of Dejan Pecar >>Sent: Tuesday, January 30, 2007 10:54 AM >>To: [email protected] >>Subject: [ULC-developer] HTTPSession >> >> >>hi, >> >>when we open mutliple ulc programs and close them again we see >>that the according HTTPSessions are >>still in memory and use quite a lot of memory depending on the >>complexity of the started programs. >> >> >>my question is shouldn't ulc discard a session after >>Application.stop() ? or at least cleanup the session so >>that the garbage collector can free the memory ? >> >>regards >> Dejan >>mailto:[EMAIL PROTECTED] >> >>_______________________________________________ >>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
