exec java -Dfile.encoding=utf-8 -Dloader.path=/opt/apps -Dspring.config.additional-location=/opt/apps/config/ -XX:+ExitOnOutOfMemoryError -cp . -jar /opt/apps/app.jar
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
21:13:51,728 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@58bf8650 - URL [jar:nested:/opt/apps/app.jar/!BOOT-INF/classes/!/logback-spring.xml] is not of type file
21:13:51,855 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [STDOUT]
21:13:51,856 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
21:13:51,865 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
21:13:51,896 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [info_log]
21:13:51,896 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
21:13:51,913 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@253348306 - setting totalSizeCap to 10 GB
21:13:51,918 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@253348306 - Archive files will be limited to [10 MB] each.
21:13:51,921 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@253348306 - No compression will be used
21:13:51,923 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@253348306 - Will use the pattern /opt/dataease2.0/logs/dataease/info.%d.%i.log for the active file
21:13:51,948 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@782a4fff - The date pattern is 'yyyy-MM-dd' from file name pattern '/opt/dataease2.0/logs/dataease/info.%d.%i.log'.
21:13:51,948 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@782a4fff - Roll-over at midnight.
21:13:51,958 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@782a4fff - Setting initial period to 2026-05-25T13:13:51.958Z
21:13:51,962 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
21:13:51,965 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[info_log] - Active log file name: /opt/dataease2.0/logs/dataease/info.log
21:13:51,966 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[info_log] - File property is set to [/opt/dataease2.0/logs/dataease/info.log]
21:13:51,968 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [error_log]
21:13:51,968 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
21:13:51,970 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@373437697 - setting totalSizeCap to 10 GB
21:13:51,970 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@373437697 - Archive files will be limited to [10 MB] each.
21:13:51,970 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@373437697 - No compression will be used
21:13:51,970 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@373437697 - Will use the pattern /opt/dataease2.0/logs/dataease/error.%d.%i.log for the active file
21:13:51,971 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@4efcf8a - The date pattern is 'yyyy-MM-dd' from file name pattern '/opt/dataease2.0/logs/dataease/error.%d.%i.log'.
21:13:51,971 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@4efcf8a - Roll-over at midnight.
21:13:51,971 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@4efcf8a - Setting initial period to 2026-05-25T13:13:51.971Z
21:13:51,973 |-INFO in ch.qos.logback.core.model.processor.ImplicitModelHandler - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
21:13:51,974 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[error_log] - Active log file name: /opt/dataease2.0/logs/dataease/error.log
21:13:51,974 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[error_log] - File property is set to [/opt/dataease2.0/logs/dataease/error.log]
21:13:51,974 |-INFO in ch.qos.logback.classic.model.processor.RootLoggerModelHandler - Setting level of ROOT logger to INFO
21:13:51,975 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@307765b4 - Propagating INFO level on Logger[ROOT] onto the JUL framework
21:13:51,976 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [STDOUT] to Logger[ROOT]
21:13:51,976 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [info_log] to Logger[ROOT]
21:13:51,976 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [error_log] to Logger[ROOT]
21:13:51,976 |-INFO in ch.qos.logback.core.model.processor.DefaultProcessor@7cc586a8 - End of configuration.
21:13:51,976 |-INFO in org.springframework.boot.logging.logback.SpringBootJoranConfigurator@7db534f2 - Registering current configuration as safe fallback point
  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/

 :: Spring Boot ::                (v3.3.0)

2026-05-25 21:13:52.039 INFO  --- [kground-preinit] o.h.validator.internal.util.Version      : HV000001: Hibernate Validator 8.0.1.Final
2026-05-25 21:13:52.183 INFO  --- [           main] io.dataease.CoreApplication              : Starting CoreApplication v2.10.20 using Java 21.0.6 with PID 1 (/opt/apps/app.jar started by root in /deployments)
2026-05-25 21:13:52.185 INFO  --- [           main] io.dataease.CoreApplication              : The following 1 profile is active: "standalone"
2026-05-25 21:13:54.746 INFO  --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode
2026-05-25 21:13:54.753 INFO  --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data LDAP repositories in DEFAULT mode.
2026-05-25 21:13:54.847 INFO  --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 85 ms. Found 0 LDAP repository interfaces.
2026-05-25 21:13:54.880 INFO  --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode
2026-05-25 21:13:54.882 INFO  --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data Redis repositories in DEFAULT mode.
2026-05-25 21:13:54.913 INFO  --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 19 ms. Found 0 Redis repository interfaces.
2026-05-25 21:13:56.245 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jdbc.DataSourceConfiguration$Hikari' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceConfiguration$Hikari] 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 [schedulerStarter]? 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-05-25 21:13:56.267 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration' of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration] 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 [schedulerStarter]? 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-05-25 21:13:56.271 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'stringOrNumberMigrationVersionConverter' of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$StringOrNumberToMigrationVersionConverter] 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 [schedulerStarter]? 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-05-25 21:13:56.288 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.datasource-org.springframework.boot.autoconfigure.jdbc.DataSourceProperties' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceProperties] 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 [schedulerStarter]? 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-05-25 21:13:56.301 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration$PooledDataSourceConfiguration' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration$PooledDataSourceConfiguration] 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 [schedulerStarter]? 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-05-25 21:13:56.306 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'jdbcConnectionDetails' of type [org.springframework.boot.autoconfigure.jdbc.PropertiesJdbcConnectionDetails] 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 [schedulerStarter]? 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-05-25 21:13:56.333 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'dataSource' of type [com.zaxxer.hikari.HikariDataSource] 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 [schedulerStarter]? 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-05-25 21:13:56.355 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'quartz-com.fit2cloud.autoconfigure.QuartzProperties' of type [com.fit2cloud.autoconfigure.QuartzProperties] 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 [schedulerStarter]? 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-05-25 21:13:56.367 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jdbc.DataSourceTransactionManagerAutoConfiguration$JdbcTransactionManagerConfiguration' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceTransactionManagerAutoConfiguration$JdbcTransactionManagerConfiguration] 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 [schedulerStarter]? 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-05-25 21:13:56.388 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.transaction.TransactionManagerCustomizationAutoConfiguration' of type [org.springframework.boot.autoconfigure.transaction.TransactionManagerCustomizationAutoConfiguration] 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 [schedulerStarter]? 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-05-25 21:13:56.394 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'transactionExecutionListeners' of type [org.springframework.boot.autoconfigure.transaction.ExecutionListenersTransactionManagerCustomizer] 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 [schedulerStarter]? 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-05-25 21:13:56.403 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.transaction-org.springframework.boot.autoconfigure.transaction.TransactionProperties' of type [org.springframework.boot.autoconfigure.transaction.TransactionProperties] 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 [schedulerStarter]? 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-05-25 21:13:56.407 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'platformTransactionManagerCustomizers' of type [org.springframework.boot.autoconfigure.transaction.TransactionManagerCustomizers] 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 [schedulerStarter]? 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-05-25 21:13:56.419 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'transactionManager' of type [org.springframework.jdbc.support.JdbcTransactionManager] 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 [schedulerStarter]? 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-05-25 21:13:56.445 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'com.fit2cloud.autoconfigure.QuartzAutoConfiguration' of type [com.fit2cloud.autoconfigure.QuartzAutoConfiguration$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). The currently created BeanPostProcessor [schedulerStarter] is declared through a non-static factory method on that class; consider declaring it as static instead.
2026-05-25 21:13:56.472 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.flyway-org.springframework.boot.autoconfigure.flyway.FlywayProperties' of type [org.springframework.boot.autoconfigure.flyway.FlywayProperties] 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 [schedulerStarter]? 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-05-25 21:13:56.485 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$FlywayConfiguration' of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$FlywayConfiguration] 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 [schedulerStarter]? 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-05-25 21:13:56.499 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'flywayConnectionDetails' of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$PropertiesFlywayConnectionDetails] 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 [schedulerStarter]? 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-05-25 21:13:56.503 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'resourceProviderCustomizer' of type [org.springframework.boot.autoconfigure.flyway.ResourceProviderCustomizer] 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 [schedulerStarter]? 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-05-25 21:13:56.702 WARN  --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'flyway' of type [org.flywaydb.core.Flyway] 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 [schedulerStarter]? 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-05-25 21:13:56.742 INFO  --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2026-05-25 21:14:27.944 INFO  --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2026-05-25 21:14:58.977 INFO  --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2026-05-25 21:15:30.004 INFO  --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2026-05-25 21:16:01.013 INFO  --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2026-05-25 21:16:32.032 INFO  --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2026-05-25 21:17:03.065 INFO  --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2026-05-25 21:17:34.097 INFO  --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...