Hi Udo, Server gfsh>version --full Build-Date: 2020-08-17 08:42:10 +0000 Build-Id: infra 202008170838 Build-Java-Vendor: Private Build Build-Java-Version: 1.8.0_252 Build-Platform: Linux 4.15.0-101-generic amd64 Product-Name: Apache Geode Product-Version: 1.12.0.9-NORDIX.202008170838 Source-Date: 2020-08-17 08:09:19 +0000 Source-Repository: HEAD Source-Revision: be8d0606ba2ad2961e603098ac4d970738a55547 Running on: /192.168.254.58, 2 cpu(s), amd64 Linux 4.12.14-195-default
Client 'org.springframework.geode:spring-geode-starter:1.3.3.RELEASE' /// Gábor From: Udo Kohlmeyer <[email protected]> Sent: Tuesday, September 8, 2020 10:08 AM To: [email protected] Subject: Re: Geode REST API - Question Hi there Gabor. Can you please elaborate on versions of Geode and Spring Boot Data Geode are you using. You can confirm if you are using compatible versions here. https://github.com/spring-projects/spring-boot-data-geode/wiki/Spring-Boot-for-Apache-Geode-and-Pivotal-GemFire-Version-Compatibility-Matrix<https://protect2.fireeye.com/v1/url?k=cef1194a-9051db0f-cef159d1-8692dc8284cb-7308fce7ed79d1a9&q=1&e=5a50da78-7bd5-4e72-a2e5-d11eb95e9631&u=https%3A%2F%2Fgithub.com%2Fspring-projects%2Fspring-boot-data-geode%2Fwiki%2FSpring-Boot-for-Apache-Geode-and-Pivotal-GemFire-Version-Compatibility-Matrix> —Udo On Sep 8, 2020, 6:03 PM +1000, Gábor Kendelényi <[email protected]<mailto:[email protected]>>, wrote: 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
