I would go for the first solution, as it avoid creating a new background thread for each new session, which as you state may severly impact server load. To achieve this, what comes to mind is having a per-session object holding the top-level continuations of a session (and thus, indirectly, the continuation trees), have this object implement HttpSessionBindingListener, and register it for monitoring by the expiration thread.
Sylvain
I have posted a patch at http://issues.apache.org/bugzilla/show_bug.cgi?id=31676 could you please review that?
-- Leszek Gawron [EMAIL PROTECTED]
