# Spingboot upgrade from 2.x to 3.1.0 which is causing app failure due to elastic search dependency

**URL:** <https://discuss.elastic.co/t/spingboot-upgrade-from-2-x-to-3-1-0-which-is-causing-app-failure-due-to-elastic-search-dependency/366024>\
**Category:** Elasticsearch\
**Created:** [September 4, 2024, 9:55am UTC](https://discuss.elastic.co/t/spingboot-upgrade-from-2-x-to-3-1-0-which-is-causing-app-failure-due-to-elastic-search-dependency/366024 "2024-09-04T09:55:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rohit\_Rawat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohit_rawat/32/137298_2.png) [@Rohit\_Rawat](https://discuss.elastic.co/u/Rohit_Rawat)\
**Post date:** [September 4, 2024, 9:55am UTC](https://discuss.elastic.co/t/spingboot-upgrade-from-2-x-to-3-1-0-which-is-causing-app-failure-due-to-elastic-search-dependency/366024/1 "2024-09-04T09:55:55Z")

</div>

```auto
org.springframework.boot:spring-boot-starter-data-elasticsearch:jar:3.1.0:compile
[INFO] \- org.springframework.data:spring-data-elasticsearch:jar:5.1.0:compile (version managed from 5.1.0)
[INFO] \- co.elastic.clients:elasticsearch-java:jar:8.7.1:compile 

```

```auto
Error creating bean with name 'storeDetailsRepo' defined in com.xyz.abc.communication.elk.repository.ElkStoreDetailsRepo defined in @EnableElasticsearchRepositories declared on ElasticsearchRepositoriesRegistrar.EnableElasticsearchRepositoriesConfiguration: Cannot resolve reference to bean 'elasticsearchTemplate' while setting bean property 'elasticsearchOperations' Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'elasticsearchTemplate' defined in class path resource [org/springframework/boot/autoconfigure/data/elasticsearch/ElasticsearchDataConfiguration$JavaClientConfiguration.class]: Unsatisfied dependency expressed through method 'elasticsearchTemplate' parameter 0: Error creating bean with name 'elasticsearchClient' defined in class path resource [org/springframework/boot/autoconfigure/elasticsearch/ElasticsearchClientConfigurations$ElasticsearchClientConfiguration.class]: Unsatisfied dependency expressed through method 'elasticsearchClient' parameter 0: Error creating bean with name 'restClientTransport' defined in class path resource [org/springframework/boot/autoconfigure/elasticsearch/ElasticsearchClientConfigurations$ElasticsearchTransportConfiguration.class]: Signature Parse error: expected a class type

```

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [September 4, 2024, 4:39pm UTC](https://discuss.elastic.co/t/spingboot-upgrade-from-2-x-to-3-1-0-which-is-causing-app-failure-due-to-elastic-search-dependency/366024/2 "2024-09-04T16:39:37Z")

</div>

From #Elastic Search to #Elasticsearch

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [September 4, 2024, 4:42pm UTC](https://discuss.elastic.co/t/spingboot-upgrade-from-2-x-to-3-1-0-which-is-causing-app-failure-due-to-elastic-search-dependency/366024/3 "2024-09-04T16:42:29Z")

</div>

In the trace you shared I don't see anything related to a class provided by the Elasticsearch client.

So my guess is that this is something on your end?

> Error creating bean with name 'restClientTransport'

May be share your code?  
Or the full stacktrace if any?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 2, 2024, 4:42pm UTC](https://discuss.elastic.co/t/spingboot-upgrade-from-2-x-to-3-1-0-which-is-causing-app-failure-due-to-elastic-search-dependency/366024/4 "2024-10-02T16:42:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.