On Jan 9, 2008 11:22 AM, Andrea K. <[EMAIL PROTECTED]> wrote: > > Hi Alex, > I attached the code. As you can see is not complex. > Logout are never done for readonly sessions, but only for admin (write) > operations. > Every X minutes sessionpool is purged and new sessions are created. Obsolete > sessions are logged out or expire automatically. > > Thanks a lot for your help. > BR. > A. - http://www.nabble.com/file/p14707938/session_pool.java > session_pool.java
Andrea, I must confess that I haven't got the time too fully look through your code. Moreover it is not immediately clear how it gets called, as the class is offering only a get operation and not a release as normal pools. But, if you are invoking this code on each HTTP request, then I would say that you really have a big bottleneck in your app and you should try to get rid of it (synchronization at the level of your pool, synchronization at the level of collections). My whole heartly advise would be to look into an existing pooling solution (even if a generic one) and try to use it. Without any intentions to criticize your code, most probably an existing solution would have already been passing through testing and different scenario usages that are making it a bit more stable and reliable than your home made pool (I really hope you are not getting this the wrong way). bests, ./alex -- .w( the_mindstorm )p. > -- > View this message in context: > http://www.nabble.com/Shared-session-pool-tp14486499p14707938.html > > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. > >
