Hi Geode Team/Users, I need your help figuring out why the Apache Geode Java Client is behaving the way it does. Overall my task is simple. I just need to connect to a Geode server running in a small Kubernetes test cluster via a Spring Boot application.
Geode Server On the Geode side I have enabled the REST API by setting the "-Dgemfire.start-dev-rest-api" property true. It's working properly. bash-4.4# curl -i -X GET http://localhost:7070/gemfire-api/v1 HTTP/1.1 200 OK Date: Mon, 07 Sep 2020 12:39:43 GMT Location: http://localhost:7070/gemfire-api/v1 Spring Boot App On the App side I'm using the below annotations in order I could do the region creation part through the client: @ClientCacheApplication(useHttp=true) @EnableClusterConfiguration @EnableEntityDefinedRegions Problem When I check the application log during start app I can see that the client is trying to use a slightly different URL for the RegionCreation POST request: org.springframework.context.ApplicationContextException: Failed to start bean 'gemfireClusterSchemaObjectInitializer'; nested exception is org.springframework.web.client.HttpClientErrorException$NotFound: 404 Not Found: [HTTP ERROR 404 Not Found URI: /gemfire/v1/regions STATUS: 404 MESSAGE: Not Found SERVLET: null ] So instead of "/gemfire-api/v1" or "/geode/v1" it's trying to access the "/gemfire/v1" url. Could you help me figure out why is that? Is this a bug? Regards, Gábor
