问题描述
我有Win 10 x64。我更新到Java 8 Update171。尝试使用此命令行运行ES
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
我升级到172，它是相同的。 （免责声明：这可能是未预期的而不是意外的，但我没有重新安装172进行检查，然后再次降级。）
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看了jvm.options，我唯一能找到 common的地方是在评论中
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
$ b很重要
$ b
降级为je 8 U 162解决了此问题，一切都很好。
我的本地DynamoDB在最新的Java下运行正常。这是我如何启动ES的问题（不要这么认为-它已经使用了很长时间了）？ ES或Java是否有问题？有没有人知道的解决方法，我宁愿运行最新的Java。
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.
推荐答案
对我来说， elasticsearch.bat从％JAVA％更改为！JAVA！在第47行
For me helped to change in elasticsearch.bat from %JAVA% to !JAVA! in line 47
这篇关于ES无法在Win x64 Java SE 8 u 171/2上启动的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！