New Warning messages during start

[korbelm]

in 1.8 version during tomcat start there are new warning messages (postgres db), please check

[WARN] Unable to proxy interface-implementing method [public final boolean org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.supports(java.lang.Object)] because it is marked as final, consider using interface-based JDK proxies instead.
09:43:56.297
[WARN] Unable to proxy interface-implementing method [public final org.springframework.web.servlet.ModelAndView org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(jakarta.servlet.http.HttpServletRequest,jakarta.servlet.http.HttpServletResponse,java.lang.Object) throws java.lang.Exception] because it is marked as final, consider using interface-based JDK proxies instead.
09:43:56.298
[WARN] Unable to proxy interface-implementing method [public final long org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.getLastModified(jakarta.servlet.http.HttpServletRequest,java.lang.Object)] because it is marked as final, consider using interface-based JDK proxies instead.
09:43:56.308
[WARN] Unable to proxy interface-implementing method [public final void org.springframework.web.context.support.WebApplicationObjectSupport.setServletContext(jakarta.servlet.ServletContext)] because it is marked as final, consider using interface-based JDK proxies instead.
09:43:56.315
[WARN] Unable to proxy interface-implementing method [public final void org.springframework.context.support.ApplicationObjectSupport.setApplicationContext(org.springframework.context.ApplicationContext) throws org.springframework.beans.BeansException] because it is marked as final, consider using interface-based JDK proxies instead

[WARN] Bean 'jobRegistry' of type [org.springframework.batch.core.configuration.support.MapJobRegistry] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [jobRegistryBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.

[banterCZ]

It cannot be reproduced. Most probably spotted on PowerAuth Cloud. Reported in enrollment-server wultra/enrollment-server#1089