Hi Ted, Do you mean GC problem can prevent delivery of SESSION EXPIRE event? Hum...so you have met this problem before? I didn't see any OOM though, will look into it more.
On Mon, Aug 16, 2010 at 12:46 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: > I am assuming that you are using ZK from java. > > Very likely you are having GC problems. > > Turn on verbose GC logging and see what is happening. You may also want to > change the session timeout values. > > It is very common for the use of ZK to highlight problems that you didn't > know that you had. > > On Sun, Aug 15, 2010 at 8:51 PM, Qing Yan <qing...@gmail.com> wrote: > >> We started using ZK in production recently and run into some problems. >> The user case is simple we have a central >> monitor checks the ephermenal nodes created by distributed apps, if >> the node dissappear, corresponding app will get restarted. Each app >> will also handle SESSION_EXPIRE by shutting itself down... >> >> Whats happening now is sometimes the central monitor will try to >> restart the app, in the mean time the app runs fine and sees no sign >> of SESSION_EXPIRED. Any clue what's going on here? >> >> Thanks >> >