重新编译 elasticsearch6.4.2 核心源码,启动error

重新编译了 elasticsearch 核心源码,替换$es_home/lib/elasticsearch-6.4.2.jar 启动报错

java.lang.ExceptionInInitializerError: null
at org.elasticsearch.common.logging.DeprecationLogger.(DeprecationLogger.java:163) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.common.unit.ByteSizeValue.(ByteSizeValue.java:38) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.http.HttpTransportSettings.(HttpTransportSettings.java:85) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.bootstrap.Security.addSocketPermissionForHttp(Security.java:342) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.bootstrap.Security.addBindPermissions(Security.java:329) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.bootstrap.Security.createPermissions(Security.java:254) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.bootstrap.Security.configure(Security.java:122) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:208) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:326) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:136) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:127) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) ~[elasticsearch-cli-6.4.2.jar:6.4.2]
at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-6.4.2.jar:6.4.2]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:93) ~[elasticsearch-6.4.2.jar:6.4.2]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:86) ~[elasticsearch-6.4.2.jar:6.4.2]
Caused by: java.lang.NullPointerException
at org.elasticsearch.Build.(Build.java:127) ~[elasticsearch-6.4.2.jar:6.4.2]
… 16 more

使用 jd-gui 反编译发现,最核心的 Bootstrap.class 无法反编译,所以是打包除了问题,重新打包得以解决
發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章