You are right It’s my mistake I was trying to simplify my code for the mail and
I put the useHttp to the wrong annotation:
@EnableGemfireRepositories(basePackages = "com.ericsson.eea.privacy.dao")
@EnableEntityDefinedRegions(basePackages =
"com.ericsson.eea.privacy.entity")
@EnablePdx
@EnableIndexing
@ClientCacheApplication(locators = { @ClientCacheApplication.Locator(host =
"eric-data-kvdb-ag-locator", port = 10334) }, logLevel = "debug")
@EnableClusterConfiguration(
useHttp=true,
host="eric-data-kvdb-ag-server",
port=7070,
requireHttps=false
)
Lib: 'org.springframework.geode:spring-geode-starter:1.3.3.RELEASE'
Server: Product-Version: 1.12.0.9-NORDIX.202008170838
From: Udo Kohlmeyer <[email protected]>
Sent: Tuesday, September 8, 2020 10:20 AM
To: [email protected]
Subject: Re: Geode REST API - Question
Hi there Gabor,
I’ve done some digging.. And I really don’t know what version of SBDG or SDG
you are using in your client.
In none of the supported versions is there any support for
`ClientCacheApplication(useHttp=true)`
Maybe you are looking for:
`EnableClusterConfiguration(useHttp=true)`
And in case you want to opt-out of using HTTPS
`EnableClusterConfiguration(useHttp=true, requireHttps=false)`
Please let me know what versions of the libraries you are using, so that we can
try and help you further.
—Udo
On Sep 8, 2020, 6:08 PM +1000, Udo Kohlmeyer
<[email protected]<mailto:[email protected]>>, wrote:
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=8bdcd0ff-d56c4d65-8bdc9064-867b36d1634c-e7df90ff1c0652f3&q=1&e=30d4a48f-50ea-4de6-8a21-b9b72218bea2&u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fgithub.com%252Fspring-projects%252Fspring-boot-data-geode%252Fwiki%252FSpring-Boot-for-Apache-Geode-and-Pivotal-GemFire-Version-Compatibility-Matrix%26data%3D02%257C01%257Cudo%2540vmware.com%257Cf8577a04f2d9453a173008d853ce57f2%257Cb39138ca3cee4b4aa4d6cd83d9dd62f0%257C0%257C0%257C637351492990187660%26sdata%3DsI%252B8DyDkwN18q9tDp9NKW3%252FhIpPEcE3GQHM0TxYsQoc%253D%26reserved%3D0>
—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
