There's a request scheduler that sits in front of Jetty that simply stops
sending it requests, and when we know it's no longer serving requests, we
kill the process.
The takeaway here is to design for statelessness when possible, and treat
local memory as an extremely volatile resource. Your appli
Ok, then my last question. How do you terminate a thread "gracefully"?
In standard Java, there is no way to do that (or at least there is not
any I'm aware of).
In GAE you trigger the "DeadlineExceededException", which reminds me a
bit of the standard "ThreadDeath" exception (triggered by the
Thre
No, the situation is handled gracefully.
On Thu, Jul 1, 2010 at 12:29 PM, Luis wrote:
> Thanks again!
>
> But then I have a related question: when you terminate some request
> that has last too long, you just kill the whole JVM? Cannot that
> affect other petitions attended by other servlets (ru
Thanks again!
But then I have a related question: when you terminate some request
that has last too long, you just kill the whole JVM? Cannot that
affect other petitions attended by other servlets (running in
different threads) of the same application running in that JVM?
Best,
Luis
On Jul 1, 8:
