You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Mario Rodriguez <sp...@gmail.com> on 2009/09/14 11:35:44 UTC

Best Practices: Wicket and BEA Weblogic Configuration

I have read several postings regarding the configuration of wicket for BEA
clusters. There is however very little information about the best practices
for such configuration. I have read that the "persistent-store-type" should
be configured as "replicated_if_clustered" but besides this parameter, there
is no much documentation.

Although every application is unique, is there anybody out there that has
any recommendation regarding the following parameters:

   - max-in-memory-sessions
   - cache-size (for JDBC and in memory)
   - invalidation-interval-secs (for doing house cleanning for timeouts and
   invalid sessions)

Any comments will be greatly appreciated.

Thanks,

-- 
Mario
Sent from Barcelona, Spain

sesseion timeout using a Panel

Posted by Joe <hu...@yahoo.cn>.
i have a pannel code for login ,when  session timeout ,i don't login fist time. it mean i must refresh the page, then i can login form the login pannel when the session timeout.
if the login code is not the pannel, it don't need refresh the login page ,and it can login .i don't know why. thx
 
joe



      ___________________________________________________________ 
  好玩贺卡等你发,邮箱贺卡全新上线! 
http://card.mail.cn.yahoo.com/