（从源码解答）Failed to instantiate [org.elasticsearch.client.transport.TransportClient]

最新推荐文章于 2024-05-01 19:17:00 发布

为了正义还战

最新推荐文章于 2024-05-01 19:17:00 发布

阅读量5k

点赞数 10

文章标签： java spring redis

本文链接：https://blog.csdn.net/qq_35480753/article/details/106130535

版权

报错信息：

之前项目整合了redis，今天我试着整合elasticsearch时，项目启动报错

（先提一下原因，redis跟Elasticsearch都是用的Netty载体，两个先后加载顺序，都会设置一个availableProcessors的参数，redis创建bean后再创建Elasticsearch，会判断该参数被创建过了而导致bean创建失败）

Error creating bean with name ‘elasticsearchClient’；具体报错如下

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'elasticsearchClient' defined in class path resource [org/springframework/boot/autoconfigure/data/elasticsearch/ElasticsearchAutoConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.elasticsearch.client.transport.TransportClient]: Factory method 'elasticsearchClient' threw exception; nested exception is java.lang.IllegalStateException: availableProcessors is already set to [8], rejecting [8]
	at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:656) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:484) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1338) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1177) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:882) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:878) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:550) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
	at com.mySpring.SpringOaApplication.main(SpringOaApplication.java:56) ~[classes/:na]
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.elasticsearch.client.transport.TransportClient]: Factory method 'elasticsearchClient' threw exception; nested exception is java.lang.IllegalStateException: availableProcessors is already set to [8], rejecting [8]
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:185) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:651) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	... 19 common frames omitted
Caused by: java.lang.IllegalStateException: availableProcessors is already set to [8], rejecting [8]
	at io.netty.util.NettyRuntime$AvailableProcessorsHolder.setAvailableProcessors(NettyRuntime.java:51) ~[netty-common-4.1.48.Final.jar:4.1.48.Final]
	at io.netty.util.NettyRuntime.setAvailableProcessors(NettyRuntime.java:87) ~[netty-common-4.1.48.Final.jar:4.1.48.Final]
	at org.elasticsearch.transport.netty4.Netty4Utils.setAvailableProcessors(Netty4Utils.java:79) ~[transport-netty4-client-6.8.7.jar:6.8.7]
	at org.elasticsearch.transport.netty4.Netty4Transport.<init>(Netty4Transport.java:112) ~[transport-netty4-client-6.8.7.jar:6.8.7]
	at org.elasticsearch.transport.Netty4Plugin.lambda$getTransports$0(Netty4Plugin.java:85) ~[transport-netty4-client-6.8.7.jar:6.8.7]
	at org.elasticsearch.client.transport.TransportClient.buildTemplate(TransportClient.java:192) ~[elasticsearch-6.8.7.jar:6.8.7]
	at org.elasticsearch.client.transport.TransportClient.<init>(TransportClient.java:288) ~[elasticsearch-6.8.7.jar:6.8.7]
	at org.elasticsearch.transport.client.PreBuiltTransportClient.<init>(PreBuiltTransportClient.java:128) ~[transport-6.8.7.jar:6.8.7]
	at org.elasticsearch.transport.client.PreBuiltTransportClient.<init>(PreBuiltTransportClient.java:114) ~[transport-6.8.7.jar:6.8.7]
	at org.elasticsearch.transport.client.PreBuiltTransportClient.<init>(PreBuiltTransportClient.java:104) ~[transport-6.8.7.jar:6.8.7]
	at org.springframework.data.elasticsearch.client.TransportClientFactoryBean.buildClient(TransportClientFactoryBean.java:85) ~[spring-data-elasticsearch-3.2.6.RELEASE.jar:3.2.6.RELEASE]
	at org.springframework.data.elasticsearch.client.TransportClientFactoryBean.afterPropertiesSet(TransportClientFactoryBean.java:80) ~[spring-data-elasticsearch-3.2.6.RELEASE.jar:3.2.6.RELEASE]
	at org.springframework.boot.autoconfigure.data.elasticsearch.ElasticsearchAutoConfiguration.elasticsearchClient(ElasticsearchAutoConfiguration.java:59) ~[spring-boot-autoconfigure-2.2.6.RELEASE.jar:2.2.6.RELEASE]
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:na]
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
	at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	... 20 common frames omitted

Disconnected from the target VM, address: '127.0.0.1:55055', transport: 'socket'

Process finished with exit code 1

解决思路：

空话：问题的出现往往网上会有很多类似解答的文章，但是大多千篇一律，并且给出的解答简单粗暴，加个什么配置，什么设置为false；永远告诉你怎么做，但是极少有人会有空指出为什么这么做。今天也是试试的心态，顺便检验一下自己的读码能力，写一篇文章，以这个创建elasticsearch bean失败为例，告诉大家创建失败怎么解决，为什么这样解决，下次遇到类似的这种问题，能不能自己独立fix掉。

1、java的throw exception往往都是会把执行的类、执行的方法、甚至在文件的多少行都会打印出来的。这里我们点击高亮显示的bean name，会跳转到ElasticsearchAutoConfiguration类里面一个elasticsearchClient方法；
在这里插入图片描述
显然，这里是实例化TransportClient对象出错了，那么我们需要合理利用Debbuger的信息，进行单不调试

2、注意到factory.afterPropertiesSet();这个方法，跟进去；发现这个方法有一个创建传输客户端的预先操作，传参就是你为elasticsearch配置的一些节点信息，比如节点名称，节点ip等；
3、跟进到buildClient方法，有一个

this.client = new PreBuiltTransportClient(this.settings(), new Class[0]);

继续跟进到PreBuiltTransportClient方法，
跟到

static {
        initializeNetty();
        PRE_INSTALLED_PLUGINS = Collections.unmodifiableList(Arrays.asList(Netty4Plugin.class, ReindexPlugin.class, PercolatorPlugin.class, MustachePlugin.class, ParentJoinPlugin.class));
    }

我们看到有一个初始化Netty的操作，可想而知elasticsearch也是用的Netty做为服务器框架；简单初始化后，又一个预安装插件的方法，Netty4、Reindex、Percolator、Mustache、ParentJoin这几个插件，方法里面肯定要他们进行初始化。
4、继续单步，此时进入到TransportClient的buildTemplate方法；
在这里插入图片描述
里面有一个new PluginService，初始化插件，继续跟进去，来到PluginsService类，里面遍历传进来的plugin一一进行初始化。
5、继续往下，初始化完插件后，开始build各个模块，创建网络模块时，传入之前的5个插件服务，然后过滤到网络插件使用的是Netty，所以实例Transpot类是从网络模块中获取到了Netty组件。
在这里插入图片描述
6、然后他接着获取传输的提供者，调用了Netty4Plugin的getTransports方法；里面他new了一个Netty4Transport类，此时，我们发现，他调用了

Netty4Utils.setAvailableProcessors((Integer)EsExecutors.PROCESSORS_SETTING.get(settings));

进去set方法，他先判断系统属性es.set.netty.runtime.available.processors的bool值，缺省则为true；

boolean set = Booleans.parseBoolean(System.getProperty("es.set.netty.runtime.available.processors", "true"));

7、继续跟进来到NettyRuntime的setAvailableProcessors方法

synchronized void setAvailableProcessors(int availableProcessors) {
            ObjectUtil.checkPositive(availableProcessors, "availableProcessors");
            if (this.availableProcessors != 0) {
                String message = String.format(Locale.ROOT, "availableProcessors is already set to [%d], rejecting [%d]", this.availableProcessors, availableProcessors);
                throw new IllegalStateException(message);
            } else {
                this.availableProcessors = availableProcessors;
            }
        }

他先是判断激活中的netty运行时的availableProcessors属性，获取到了（int）8，由于不等于0，则抛出已被设置过的异常。
8、至此，问题原因跟踪完毕。那么继续解决，原因很简单，就是这个参数曾经被设置过了；

真正解决：

你一要么让他在elasticsearch加载初始化时，不要进入这个设置availableProcessors属性的方法，那我们溯源代码，发现我们前面贴上的代码有一个bool值 set，默认为true，当他为false时，则不会进入设置，所以出现了网上的一种解决方案，在run你的springBoot项目之前，给他来一个参数默认值。

System.setProperty("es.set.netty.runtime.available.processors", "false");

二要么让Redis跟Elasticsearch使用的Netty不要是同一个对象，理论上使用让他们引用不同版本的Netty包即可，具体则是在maven仓库里进行区分开来。

终于解决！

只是想分享解决问题的思路，个人认为知其然知其所以然，你才有能力凌驾他。而大多数文章简单粗暴的告诉大家第一种解决问题的代码，要么是自己也不懂，抄的别人的，要么我就想不出来为什么了~
当然术业有专攻，并不是所有问题都需要一刨到底，当将军学指挥总要比冲锋陷阵的小兵高级些。（太晚了，我就不花时间读二遍纠正错别字这种错误了）

为了正义还战

关注

10
点赞
踩
9

收藏

觉得还不错? 一键收藏
2
评论
（从源码解答）Failed to instantiate [org.elasticsearch.client.transport.TransportClient]

报错信息：之前项目整合了redis，今天我试着整合elasticsearch时，项目启动Error creating bean with name ‘elasticsearchClient’；具体报错如下org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'elasticsearchClient' defined in class path resource [org/spring
复制链接

扫一扫