Open KonradHoeffner opened 11 months ago
Part 2 due to the character limit of 65536:
top-deployment-backend-1 | 2023-11-03 08:21:40.743 INFO 1 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Will secure any request with [org.springframework.security.web.session.DisableEncodeUrlFilter@51869ad6, org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@27a90ce5, org.springframework.security.web.context.SecurityContextPersistenceFilter@3c87e851, org.springframework.security.web.header.HeaderWriterFilter@1fc5c0b2, org.springframework.web.filter.CorsFilter@77f4038c, org.springframework.security.web.authentication.logout.LogoutFilter@4bff28e7, org.springframework.security.oauth2.server.resource.web.BearerTokenAuthenticationFilter@1eb9d69a, org.springframework.security.web.savedrequest.RequestCacheAwareFilter@6124dda2, org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@380e33c2, org.springframework.security.web.authentication.AnonymousAuthenticationFilter@49a06087, org.springframework.security.web.session.SessionManagementFilter@d2cb2d0, org.springframework.security.web.access.ExceptionTranslationFilter@949d347, org.springframework.security.web.access.intercept.FilterSecurityInterceptor@44e08a7a]
top-deployment-backend-1 | 2023-11-03 08:21:40.897 WARN 1 --- [ main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
top-deployment-backend-1 | 2023-11-03 08:21:41.539 INFO 1 --- [ main] j.s.t.ScheduledThreadPoolJobRunrExecutor : ThreadManager of type 'ScheduledThreadPool' started
top-deployment-backend-1 | 2023-11-03 08:21:41.541 INFO 1 --- [pool-2-thread-4] org.jobrunr.server.BackgroundJobServer : Found 0 recurring jobs that need to be updated.
top-deployment-backend-1 | 2023-11-03 08:21:41.543 INFO 1 --- [pool-1-thread-1] org.jobrunr.server.BackgroundJobServer : JobRunr BackgroundJobServer (e2174be3-a28b-4f51-b56e-ffacdd3bb456) using InMemoryStorageProvider and 160 BackgroundJobPerformers started successfully
top-deployment-backend-1 | 2023-11-03 08:21:41.543 INFO 1 --- [pool-1-thread-1] org.jobrunr.server.ServerZooKeeper : Server e2174be3-a28b-4f51-b56e-ffacdd3bb456 is master (this BackgroundJobServer)
top-deployment-backend-1 | 2023-11-03 08:21:41.720 INFO 1 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 1 endpoint(s) beneath base path '/actuator'
top-deployment-backend-1 | 2023-11-03 08:21:41.751 INFO 1 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path '/api'
top-deployment-backend-1 | 2023-11-03 08:21:41.762 INFO 1 --- [ main] c.s.top.backend.TopBackendApplication : Started TopBackendApplication in 7.15 seconds (JVM running for 7.795)
The corresponding environment variable is LIQUIBASE_LOG_LEVEL
. It has a higher precedents than the liquibase.properties
file. (see https://docs.liquibase.com/concepts/connections/liquibase-environment-variables.html)
After more research I I found the liquibase issue has two parts:
JAVA_OPTS=-Dlogging.level.liquibase=WARN
works as well in docker-compose.env to get rid of the other INFO messages. But to make sure I will set LIQUIBASE_LOG_LEVEL there as well.Liquibase v4.25.0 was released on November 13 and mentions the pull request in the "New Features" section: https://github.com/liquibase/liquibase/releases/tag/v4.25.0
The "Running Changeset" messages are now gone after upgrading to Liquibase v4.25.0.
LIQUIBASE_LOG_LEVEL=WARNING
has no effect.
backend:
image: ghcr.io/onto-med/top-backend:v0.6.9
[...]
environment:
- LIQUIBASE_LOG_LEVEL=WARNING
$ docker compose logs backend | grep liquibase
backend-1 | 2023-12-18 09:21:08.932 INFO 1 --- [ main] liquibase.database : Set default schema name to public
backend-1 | 2023-12-18 09:21:08.987 INFO 1 --- [ main] liquibase.lockservice : Successfully acquired change log lock
backend-1 | 2023-12-18 09:21:09.004 INFO 1 --- [ main] liquibase.changelog : Reading resource: db/changelog/changesets/202210170901-init-db.yaml
[...]
Even though the env var is set inside the container:
$ docker compose exec backend /bin/bash
root@77f229d94447:/usr/src/top-backend# echo $LIQUIBASE_LOG_LEVEL
WARNING
Strangely, the liquibase INFO messages still occur with backend version v0.7.0-beta-10 where https://github.com/Onto-Med/top-backend/commit/d9bf3f939f2095b455ae02bdcfc0bc505de367a6 is included.
Part of https://github.com/Onto-Med/top-deployment/issues/44. Right now there is a large amount of unnecessary log output: