[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Simplest way to detect: Hey, where'd my thread go?

To conclude, after I debugged a bit:

Jetty is nice and dandy, logs the problem, as long you have some runtime exception (anything that descends from Exception)...

But is grumpy and silent when you have an Error (like OutOfMemoryError).

And in both cases, thread gets removed from the pool, but in 2nd case you have no notification about it at all in logs...


On Tue, Jun 26, 2012 at 4:45 PM, TamÃs CservenÃk <tamas@xxxxxxxxxxxxx> wrote:
New info:

It's a nice OutOfMemoryError in Nexus code.

I remember I saw some thread (or Jira issue) about why Jetty intentionally does not handle this... am I right?


On Tue, Jun 26, 2012 at 4:14 PM, TamÃs CservenÃk <tamas@xxxxxxxxxxxxx> wrote:
Hi Jetty list!

I have a situation where I confirmed that Jetty's pool is "loosing" threads. I bet it's my code (runtime or maybe even Error is thrown somewhere I assume?), but...

What is the easiest thing with Jetty (8.1.x), to instrument the threads, or install some "custom"ÂUncaughtExceptionHandler or alike (to detect and see where any why is this happening)?

Also, what is the default Jetty behavior with Threads that happens to throw some Runtime Exception or Error? The Jetty log contains no entry about anything, so I am just speculating the reasons why threads areÂdisappearing....

WhatÂUncaughtExceptionHandler is by default used?

Any help appreciated.

Reference to: