-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrew,
Andrew Hole wrote: | "I think you need to manage your events in a way that takes into account | the fact that valueUnbound will can be called by "other" members in the | cluster." | It is not a easy task, rigth? | Could you be more specific in the way of developing it? Hmm... I hadn't seen your stack trace before writing my own post. Does it appear that the TC that is going down is propagating the "expire" event to the sessions on other servers? Is that why the "new" TC is also calling valudUnbound? I'm interested in finding out exactly what is happening before I suggest a solution. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfDJ94ACgkQ9CaO5/Lv0PCTYQCgijoEPPCCPrPhITX3gvYVn70G 6PsAnRJzSE1WVsXUAaJ87VdgHVmIZTyz =Wl0Z -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
