You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using base-repo with search enabled and an ES instance not running under the default URL 'localhost:9200', but a different hostname or port number (configured in application.properties file), leads to Error creating bean with name 'dataResourceController' due to org.springframework.dao.DataAccessResourceFailureException: Connection refused.
Meanwhile, the ElasticsearchUtil is quite satisfied (aka the ES service is running and reachable):
2024-11-18 16:27:56 2024-11-18T15:27:56.665Z TRACE 9 --- [ main] e.k.datamanager.util.ElasticSearchUtil : Trying to connect to elasticsearch instance.
2024-11-18 16:27:56 2024-11-18T15:27:56.776Z TRACE 9 --- [ main] e.k.datamanager.util.ElasticSearchUtil : Status code value: 200
To Reproduce
Steps to reproduce the behavior:
setup ES on non-9200 port or not-localhost
set repo.search.url to ES URL from step 1
enable search for base-repo
start application
See error
Expected behavior
Connection should be made to custom ES service
Describe the bug
Using base-repo with search enabled and an ES instance not running under the default URL 'localhost:9200', but a different hostname or port number (configured in application.properties file), leads to
Error creating bean with name 'dataResourceController'
due toorg.springframework.dao.DataAccessResourceFailureException: Connection refused
.Meanwhile, the ElasticsearchUtil is quite satisfied (aka the ES service is running and reachable):
To Reproduce
Steps to reproduce the behavior:
repo.search.url
to ES URL from step 1Expected behavior
Connection should be made to custom ES service
Likely culprit
https://github.com/kit-data-manager/base-repo/blob/main/src/main/java/edu/kit/datamanager/repo/configuration/ElasticConfiguration.java#L42
It seems to help to provide
here, and to get host and port from there.
The text was updated successfully, but these errors were encountered: