If you are using wicket and terracotta then I recommend that you keep an eye on this thread on the wicket forums (http://www.nabble.com/Terracotta-integration-td18168616.html) where I am attempting to work on some improvements to the wicket / terracotta integration.

Cheers,

Richard

I am also using Wicket/Terracotta/Jetty and so I really want to thank you for your effort! I am going to adopt this implementation as well!

@Jan: I also feel that Jetty’s TC support would benefit of some improvements (talking about tim-jetty-6.1.4-1.1.0). The synchronization of org.mortbay.terracotta.servlet.TerracottaSessionManager is quite bad as it is using synchronized(this) and two ConcurrentHashMaps. This approach requires a considerable amount of TC transactions. I think, the terracotta session manager would benefit of a simpler approach using a single ReentrantReadWriteLock and two ordinary HashMaps.

regards
Stefan

I think the main problem was the use of ConcurrentHashMaps where you didn’t really need them; I was seeing lots of lock classes being distributed because of it. However I’m not really an expert on this and you may want to talk to gbevin on the terracotta forums (http://forums.terracotta.org/forums/user/profile/333.page) as he works for terracotta and knows more about it than I do.

Cheers,
Richard

I’m always keen to improve Jetty’s integrations with 3rd party libs such as Terracotta, and I’d be interested to hear the areas that you feel need some extra attention to bring it to a par with Tomcat/Terracotta - or even beyond
regards
Jan