Problems encountered in the development --- [is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-pr oxying]

Scene reproduction: the development environment is no problem, no problem testing environment, but to the production environment to die, reported the following error

 

2020-03-09 10:59:39,402 main INFO Log4j appears to be running in a Servlet environment, but there's no log4j-web module available. If you want better web container sup port, please add the log4j-web JAR to your web archive or server lib directory. [2020-03-09 10:59:40.099] INFO  [main] org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker postProcessAfterInitialization 33 0 - Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPrope rtiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$884e3542] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-pr oxying)

Solution: This situation is loading a configuration file on the problem, I spent a few hours, and finally found the key value yml file is not the beginning of the * in front of their own plus a letter or number on the line just fine a.

 

Guess you like

Origin www.cnblogs.com/hujunwei/p/12452167.html