Dear Cassandra :) Thanks for your kind help, I think I didn't make my question clear in the previous email. After reading more about keel, let me phrase my question again :)
Looking at the file KeelAbstractServer.java (under keel-server), it maintains a hashmap of contexts for each "sessionid". In the functions like getContext(), saveContext() etc., I can see contexts are created and saved for each sessionid. But I don't see any contexts are removed from the Hashmap if the session expires. Will this be a potential problem of memory leak? Regards Ying --- Vidakovic Aleksandar <[EMAIL PROTECTED]> wrote: > Salut Ying, > > I answered that question already in advance... call > me "Cassandra" ;-) but I'll repeat it for you: > > [code] > > <web-app > > ... > <param-name>keel.client.timeout</param-name> > <param-value>480000</param-value> > </context-param> > ... > > [/code] > > This is the time in milliseconds for the keel client > to time out. Or did you mean the timeout for > receiving openjms events? This timeout is hardcoded > in the class > "org.keel.comm.openjms.servers.KeelOpenJMSServer" in > the method "messageLoop"... it is set to 10 seconds. > > Hope this helps... > > Aleks > > -----Urspr�ngliche Nachricht----- > Von: tuzi cool [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 25. Januar 2005 03:09 > An: [EMAIL PROTECTED] > Betreff: Re: AW: [Keelgroup] A question about login > session timeout > __________________________________ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
