On Fri, Jun 4, 2010 at 10:32 PM, DmitryM <[email protected]> wrote: > > Igor, > > Can you please comment on the following couple of points I got? > > 1. "Pulling session from memcached node": I double checked the > recommendation and it looks like fetching session from the memcached node > doesn't take much time (around 200ms at most). But there was a > recommendation about immediate session attributes deserialization after > session replication > (http://apache-wicket.1842946.n4.nabble.com/A-few-clustering-questions-td1863992.html#a1863993). > Do you think it may be a potential issue causing the request processing > delay I experienced?
i would use a profiler and see where the time goes, that way you dont have to guess. > 2. The memcached-session-manager's developer suggested I could try to use > plain HttpSessionStore (instead of default SecondLevelCacheSessionStore). > But when I tried his suggestion I got the following stacktrace: > > java.lang.ExceptionInInitializerError ... > which is caused by the Injector usage in one of the classes used by a Page. > Why do you think Application.get() method may blow up? Why isn't the > ThreadLocal application instance get set? unless memcached serializer works asynchronously in its own thread. -igor > > Thanks, > Dmitry > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/SessionStore-life-cycle-in-cluster-tp2242105p2244022.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
