I have Win 10 x64. I updated to Java 8 Update 171. Attempting to run ES up with this command line
cd bin
elasticsearch.bat -Ecluster.name=ABTest_Cluster_00 -Enode.name=ABTest_Node_00
resulted in failure to start with this rather cryptic error
Common was unexpected at this time
I upgraded to 172 and it was the same. (Disclaimer: It might have been "not expected" rather than "unexpected" but I'm not re-installing 172 to check it and then downgrading again.)
I had a look in jvm.options and the only place I could find "common" was in a comment
# turn off a JDK optimization that throws away stack traces for common
# exceptions because stack traces are important for debugging
-XX:-OmitStackTraceInFastThrow
Downgrading to je 8 U 162 fixed the issue and all was well. My local DynamoDB ran up OK under the latest Java. Is this an issue with how I'm starting ES (don't think so - it's been working for ages)? Is an issue with ES or Java? Is there a work around that anyone knows of as I'd rather run the latest Java.
For me helped to change in elasticsearch.bat from %JAVA% to !JAVA! in line 47
With elastic 6.6.2
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With