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? Thanks, ~t~ On Tue, Jun 26, 2012 at 4:14 PM, Tamás Cservenák <[email protected]>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: > http://www.ibm.com/developerworks/java/library/j-jtp0924/index.html > > > Thanks, > ~t~ >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
