Executor exceptions stacktrace omitted by HotSpot in long running application
I'm considering to improve the experience of hitting potential
exceptions stacktrace omitted in long running application, which is
a JVM HotSpot optimization as Shixiong(Ryan) commented.
There might be 2 options:
1. Adds `-XX:-OmitStackTraceInFastThrow` as a common Executor JVM
2. Adds an Executor replacement workflow with a fresh new JVM when
exceptions stacktrace being omitted.
I prefer option 1, there might be performance concerns. But option 2
isn't supposed to increase the performance since which JVM is replaced
by a new one to force working on no stacktrace fast throw mode.