Steps to reproduce :
- Clone https://github.com/spring-cloud/spring-cloud-task/tree/master/spring-cloud-task-samples/timestamp
- Run the application - The service dies after it prints the timestamp
- Add:
<dependency>
<groupId>org.elasticsearch.client</groupId>
<artifactId>elasticsearch-rest-high-level-client</artifactId>
<version>7.0.0</version>
</dependency>
- Re-run the application - The service now stays alive
Notes
With:
Spring Cloud Task - Finchley.SR3
Spring Boot - 2.0.x
Rest High Level Client - 6.4.2
The app functions as intended.
With:
Spring Cloud Task - Greenwich.SR1
Spring Boot -2.1.x
Rest High Level Client - 6.4.2
The app exhibits the problematic behavior
Adding a configuration and beaning the RestHighLevelClient and closing the connection on task completion has no affect on this functionality.