On Tue, 4 Nov 2014, kiwiwings wrote:
I hopefully have time tonight for a closer look. But google says, that
it might has to do with JDK itself [1] - at least the line numbers are
very close to the stack trace.
It's probably another issue for the to-be-written known issues list ...
Maybe add a catch for it, and log a "your jvm is broken, consider
updating" in place of the current failure?
That'd let me roll the 3.11 beta 3 release :)
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
