cloud-config-client | Cloud Config Client for Node | Runtime Evironment library

This is a really odd error that I am getting while doing a maven build. I am encountering an error like this:

I want log4j2-spring.xml to read a property from the application.properties file. But seems log4j2-spring.xml is unable to read this. I have read https://logging.apache.org/log4j/2.x/manual/lookups.html#SpringLookup to implement this.

I have seen this answer on this site. Tried like this as well. But it didn't help me.

My build.gradle is like this:

Apparently, to use the log4j-spring-cloud-config-client with Spring Cloud Config, you need to take advantage of the SearchPathLocator functionality to pull the raw file based on a specific URI. From the Spring-cloud-config code it appears only the JGitEnvironmentRepository and NativeEnvironmentRepository implement that interface and offer that functionality.

Running locally, if I hit the following endpoint, I get back a raw log4j2 config file: http://localhost:8088/config-server-properties-poc/default/master/log4j2.xml.

When I try that with an S3 backend, I get a 404, and it doesn't try to search for that specific file. I was able to work around this by naming my file to log4j2-default.json (XML is not supported). When I hit the following URL, I can get my properties back but not in the correct format http://localhost:8088/log4j2/default

Format

so I have a simple project like:

When I access my Spring Boot Application at http://localhost:8080/ I always receive following JSON. I have no idea where this JSON comes from and I don't think I made a controller for this. Have you maybe seen something like this before? Does it have something to do with Swagger?

p.s. I'm using spring MVC and spring Security in my application.

This is my build.gradle file:

I am new to Spring technology and this issue has been bugging me for hours. My spring cloud config client isn't able to read properties from the config server because I am getting an IllegalArgumentException. The config server displays all the properties, but I think there is an issue with the name attribute in the propertySources list and my wild guess is that it is the reason why I am getting this issue. I am attaching the source code, error and the output here. Please help me out!!

Error:

We have Spring Cloud application using Eureka as service discovery, Config Service and WebFlux. Service works fine with Spring Cloud Hoxton.SR4, but fails with Hoxton.SR5 on app start during fetching data from Eureka. If Eureka has small number of registered apps (e.g. 30), it works fine, but in case it has around 250 services, it fails with the following exception

DataBufferLimitException: Exceeded limit on max bytes to buffer : 262144 Error has been observed at the following site(s): checkpoint ⇢ Body from GET http://eureka.xxx.com:8080/eureka/apps/?regions=us-east-1.

If we remove WebFlux from classpath, it also works fine even with Hoxton.SR5. I provided reproducible issue on github (but in order to reproduce, we need to connect to Eureka having several hundreds of registered apps). I also saw issue with similar exception , in their case issue occurred on the controller side, but in our case on app start, and property spring.codec.max-in-memory-size doesn't work here.

Spring Boot version 2.3.1.RELEASE.

Stack trace:

I have a problem connecting to the config-server. I am not sure what am I doing wrong. I have configured server running in a docker container named "config-server" on port 8888.

In an effort to put together an example project for Spring Cloud Config server and (Java and non-Java) clients using Vault, I decided to go the route of a multi-module Gradle build. Since I already had two working Java projects (server and client), I figured that I could pull the common configuration up into the parent build.gradle and conditionally apply the configuration for the Java subprojects. I started with the server subproject, and ran into an issue that I've been unable to resolve.

The build.gradle for the parent module looks like: