Martin,
I understand this is getting a bit off topic so we could as well drop it.
I understand that the threads and session will eventually be garbage
collected (go to /dev/null as you said). But this is not necessarily bad,
is it? In my case these threads are updating an application-wide cache.
Hi,
On Sat, Nov 23, 2013 at 2:11 PM, Marios Skounakis msc...@gmail.com wrote:
Bas,
Thanks for your answer. I understand what you're saying and you're right.
If I were designing the application now I'd do one of your suggestions.
But unfortunately we've written most of the code and these
Hi,
I guess it depends on the lifecycle of those threads how I would handle
this.
Suppose the session is invalidated and destroyed, what should happen to
the threads? Do they continue (A) or do they need to stop (B)?
A) In this case I would not depend on the session at all, if possible.
Bas,
Thanks for your answer. I understand what you're saying and you're right.
If I were designing the application now I'd do one of your suggestions.
But unfortunately we've written most of the code and these threads now
depend on spring session beans. Right now B is pretty much the only viable
Hi all,
This is maybe a Spring question but as my app is a wicket app and I use
this list regularly and everyone is very helpful I thought I'd ask here
first.
I have a RequestCycleListener which during onBeginRequest() conditionally
spawns some background threads and runs them using an Executor.
