2026-04-07 09:18:07.181 [WARN] [1] [main] org.springframework.cloud.config.client.ConfigServerConfigDataLoader Line:253 Could not locate PropertySource ([ConfigServerConfigDataResource@4d770bcd uris = array<String>['http://wconnect-config-server'], optional = true, profiles = 'apitest']): I/O error on GET request for "http://wconnect-config-server/work-performance/apitest/latest": wconnect-config-server
 2026-04-07 09:18:07.182 [WARN] [1] [main] org.springframework.cloud.config.client.ConfigServerConfigDataLoader Line:253 Could not locate PropertySource ([ConfigServerConfigDataResource@fe156f4 uris = array<String>['http://wconnect-config-server'], optional = true, profiles = 'default']): I/O error on GET request for "http://wconnect-config-server/work-performance/default/latest": wconnect-config-server
 2026-04-07 09:18:10.164 [WARN] [1] [main] org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Line:437 Bean 'org.springframework.cloud.commons.config.CommonsConfigAutoConfiguration' of type [org.springframework.cloud.commons.config.CommonsConfigAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
 2026-04-07 09:18:10.169 [WARN] [1] [main] org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Line:437 Bean 'org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration' of type [org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
 2026-04-07 09:18:10.172 [WARN] [1] [main] org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Line:437 Bean 'loadBalancerClientsDefaultsMappingsProvider' of type [org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration$$Lambda/0x00007fc1f17065f8] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
 2026-04-07 09:18:10.175 [WARN] [1] [main] org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Line:437 Bean 'defaultsBindHandlerAdvisor' of type [org.springframework.cloud.commons.config.DefaultsBindHandlerAdvisor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
 2026-04-07 09:18:10.207 [WARN] [1] [main] org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Line:437 Bean 'spring.datasource.dynamic-com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceProperties' of type [com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
 2026-04-07 09:18:10.216 [WARN] [1] [main] org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Line:437 Bean 'com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceAopConfiguration' of type [com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceAopConfiguration$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
 2026-04-07 09:18:10.237 [WARN] [1] [main] org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Line:437 Bean 'dsProcessor' of type [com.baomidou.dynamic.datasource.processor.DsJakartaHeaderProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
 2026-04-07 09:18:11.345 [WARN] [1] [main] org.dozer.config.GlobalSettings                    Line:118 Dozer configuration file not found: dozer.properties.  Using defaults for all Dozer global properties.
 2026-04-07 09:18:11.522 [WARN] [1] [main] com.zaxxer.hikari.HikariConfig                     Line:1087 work_performance - idleTimeout is close to or more than maxLifetime, disabling it.
 2026-04-07 09:18:11.720 [WARN] [1] [main] com.zaxxer.hikari.HikariConfig                     Line:1087 monthly_report - idleTimeout is close to or more than maxLifetime, disabling it.
 2026-04-07 09:18:11.730 [WARN] [1] [main] com.zaxxer.hikari.HikariConfig                     Line:1087 database - idleTimeout is close to or more than maxLifetime, disabling it.
 2026-04-07 09:18:19.249 [WARN] [1] [main] org.springframework.boot.autoconfigure.thymeleaf.ThymeleafAutoConfiguration$DefaultTemplateResolverConfiguration Line:102 Cannot find template location: classpath:/templates/ (please add some templates, check your Thymeleaf configuration, or set spring.thymeleaf.check-template-location=false)
 2026-04-07 09:18:33.910 [WARN] [1] [Thread-4] org.apache.catalina.loader.WebappClassLoaderBase   Line:173 The web application [ROOT] appears to have started a thread named [boundedElastic-evictor-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.base/jdk.internal.misc.Unsafe.park(Native Method)
 java.base/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:269)
 java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1758)
 java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)
 java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
 java.base/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1070)
 java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
 java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
 java.base/java.lang.Thread.run(Thread.java:1583)
 2026-04-07 09:18:33.911 [WARN] [1] [Thread-4] org.apache.catalina.loader.WebappClassLoaderBase   Line:173 The web application [ROOT] appears to have started a thread named [boundedElastic-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.base/jdk.internal.misc.Unsafe.park(Native Method)
 java.base/java.util.concurrent.locks.LockSupport.park(LockSupport.java:371)
 java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(AbstractQueuedSynchronizer.java:519)
 java.base/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3780)
 java.base/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3725)
 java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1707)
 java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1170)
 java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
 java.base/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1070)
 java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
 java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
 java.base/java.lang.Thread.run(Thread.java:1583)
 