users@grizzly.java.net

Re: java.lang.NoClassDefFoundError in runtime kills selector thread?

From: Ryan Lubke <ryan.lubke_at_oracle.com>
Date: Sun, 18 Dec 2016 23:55:45 -0800

Sorry for the delay. I've never seen anything like this particular
error case. Is it possible to reproduce outside of Mule?

> Daniel Feist <mailto:dfeist_at_gmail.com>
> December 14, 2016 at 16:23
> Hi Alexey/Ryan,
>
> Seeing a really weird issue where, in runtime, sometimes after 1wk or
> more, NoClassDefFoundError errors are being thrown causing selectors
> thread to exit in some cases, and worker threads to fail in other
> cases.
>
> Here are a couple of reports of when it's happened in a worker thread:
> -
> http://stackoverflow.com/questions/40779193/mule-http-listener-thread-cant-resolve-org-glassfish-grizzly-localization-logme
> - https://www.mulesoft.org/jira/browse/MULE-10222
>
> It also happens in selector thread sometimes too, resulting in simply
> the following, curiously with no log output whatsoever.
>
> Exception: java.lang.NoClassDefFoundError thrown from the
> UncaughtExceptionHandler in thread "grizzly.selector(2)"
>
> Given there is no log output this also suggests an issue with
> LogMessages here too. From a class-loading perspective, everything is
> in the same classloader with no runtime changes being made.
>
> Any thoughts at all?
>
> Dan