Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate @EnableLogging annotation [DATAGEODE-299] #344

spring-projects-issues opened this issue Feb 6, 2020 · 0 comments

Deprecate @EnableLogging annotation [DATAGEODE-299] #344

spring-projects-issues opened this issue Feb 6, 2020 · 0 comments


Copy link

@spring-projects-issues spring-projects-issues commented Feb 6, 2020

John Blum opened DATAGEODE-299 and commented

The SDG @EnableLogging annotation no longer has any effect or control over the logging capabilities of Apache Geode (and by extension, Pivotal GemFire) any longer.

This is to say, that GemFire/Geode's own configuration properties (e.g. -Dgemfire.log-level) absolutely have no effect any more as of Apache Geode 1.9.2 & Pivotal GemFire 9.8.4.

The only way to log output from Apache Geode or Pivotal GemFire to Standard Out, to a log file, or other destination is to..

  1. Include a logging provider on the Spring application classpath (e.g. logback-classic if the Spring application is using the SLF4J API, which is quite common, particularly for Spring Boot applications).

  2. If the logging provider is not Log4j (i.e. log4j-core), then you will additionally need to add a adapter/bridge JAR between Log4j and the logging provider. Note, Apache Geode/Pivotal GemFire use the Log4j API to log output for Apache Geode and Pivotal GemFire respectively.

For example, if you are using SLF4J with Logback as your logging provider, then you will additionally need to add the org.apache.logging.log4j:log4j-to-slf4j dependency to your Spring application classpath.

  1. Then a user must supply a logging provider configuration file at the configured location with the appropriate Loggers and Appender to log output from either Apache Geode/Pivotal GemFire or Spring, and any other 3rd party libs you wish to log output for.

For example:

In addition to the deprecation, we must also provide documentation in the Annotation-based Configuration Model Chapter of the Reference Documentation, here:

No further details from DATAGEODE-299

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants