这些 Spring 调试消息意味着什么?
我在独立的 Java 应用程序中使用 Spring IoC。当应用程序启动时,它会创建一个包含启动信息的日志。有些消息我不明白,请帮助我理解它们并解释如果必须修复它们如何修复它们?我也很好奇:这些消息对我的应用程序稳定性是否有任何危险?
让我害怕的消息以“无法”一词开头。目前该应用程序运行良好。
INFO - Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@52cc95d: startup date [Thu Jun 02 16:02:12 MSD 2011]; root of context hierarchy
INFO - Loading XML bean definitions from class path resource [application-config.xml]
DEBUG - Using JAXP provider [com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl]
DEBUG - Loading schema mappings from [META-INF/spring.schemas]
DEBUG - Loaded schema mappings: {http://www.springframework.org/schema/tx/spring-tx-2.5.xsd=org/springframework/transaction/config/spring-tx-2.5.xsd, http://www.springframework.org/schema/tx/spring-tx-2.0.xsd=org/springframework/transaction/config/spring-tx-2.0.xsd, http://www.springframework.org/schema/tx/spring-tx.xsd=org/springframework/transaction/config/spring-tx-3.0.xsd, http://www.springframework.org/schema/tx/spring-tx-3.0.xsd=org/springframework/transaction/config/spring-tx-3.0.xsd}
DEBUG - Loading bean definitions
DEBUG - Loaded 3 bean definitions from location pattern [application-config.xml]
DEBUG - Bean factory for org.springframework.context.support.ClassPathXmlApplicationContext@52cc95d: org.springframework.beans.factory.support.DefaultListableBeanFactory@33aae94f: defining beans [propertyPlaceholderConfigurer,dbWorker,connectionPool]; root of factory hierarchy
DEBUG - Creating shared instance of singleton bean 'propertyPlaceholderConfigurer'
DEBUG - Creating instance of bean 'propertyPlaceholderConfigurer'
DEBUG - Eagerly caching bean 'propertyPlaceholderConfigurer' to allow for resolving potential circular references
DEBUG - Finished creating instance of bean 'propertyPlaceholderConfigurer'
INFO - Loading properties file from class path resource [config.properties]
DEBUG - Unable to locate MessageSource with name 'messageSource': using default [org.springframework.context.support.DelegatingMessageSource@49bdc9d8]
DEBUG - Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using default [org.springframework.context.event.SimpleApplicationEventMulticaster@255d17d7]
INFO - Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@33aae94f: defining beans [propertyPlaceholderConfigurer,dbWorker,connectionPool]; root of factory hierarchy
DEBUG - Returning cached instance of singleton bean 'propertyPlaceholderConfigurer'
DEBUG - Creating shared instance of singleton bean 'dbWorker'
DEBUG - Creating instance of bean 'dbWorker'
DEBUG - Eagerly caching bean 'dbWorker' to allow for resolving potential circular references
DEBUG - Creating shared instance of singleton bean 'connectionPool'
DEBUG - Creating instance of bean 'connectionPool'
DEBUG - Eagerly caching bean 'connectionPool' to allow for resolving potential circular references
DEBUG - Finished creating instance of bean 'connectionPool'
DEBUG - Finished creating instance of bean 'dbWorker'
DEBUG - Returning cached instance of singleton bean 'connectionPool'
DEBUG - Unable to locate LifecycleProcessor with name 'lifecycleProcessor': using default [org.springframework.context.support.DefaultLifecycleProcessor@4b1c2b67]
DEBUG - Returning cached instance of singleton bean 'lifecycleProcessor'
I use Spring IoC in my stand-alone Java application. When the application starts it creates a log with start-up info. Some messages I don't understand, please help me to understand them and explain how to fix them if they must be fixed? Also I am curious: Is there any danger for my application stability because of these messages?
Messages that scare me off starts with word "Unable". At the moment the application works quite well.
INFO - Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@52cc95d: startup date [Thu Jun 02 16:02:12 MSD 2011]; root of context hierarchy
INFO - Loading XML bean definitions from class path resource [application-config.xml]
DEBUG - Using JAXP provider [com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl]
DEBUG - Loading schema mappings from [META-INF/spring.schemas]
DEBUG - Loaded schema mappings: {http://www.springframework.org/schema/tx/spring-tx-2.5.xsd=org/springframework/transaction/config/spring-tx-2.5.xsd, http://www.springframework.org/schema/tx/spring-tx-2.0.xsd=org/springframework/transaction/config/spring-tx-2.0.xsd, http://www.springframework.org/schema/tx/spring-tx.xsd=org/springframework/transaction/config/spring-tx-3.0.xsd, http://www.springframework.org/schema/tx/spring-tx-3.0.xsd=org/springframework/transaction/config/spring-tx-3.0.xsd}
DEBUG - Loading bean definitions
DEBUG - Loaded 3 bean definitions from location pattern [application-config.xml]
DEBUG - Bean factory for org.springframework.context.support.ClassPathXmlApplicationContext@52cc95d: org.springframework.beans.factory.support.DefaultListableBeanFactory@33aae94f: defining beans [propertyPlaceholderConfigurer,dbWorker,connectionPool]; root of factory hierarchy
DEBUG - Creating shared instance of singleton bean 'propertyPlaceholderConfigurer'
DEBUG - Creating instance of bean 'propertyPlaceholderConfigurer'
DEBUG - Eagerly caching bean 'propertyPlaceholderConfigurer' to allow for resolving potential circular references
DEBUG - Finished creating instance of bean 'propertyPlaceholderConfigurer'
INFO - Loading properties file from class path resource [config.properties]
DEBUG - Unable to locate MessageSource with name 'messageSource': using default [org.springframework.context.support.DelegatingMessageSource@49bdc9d8]
DEBUG - Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using default [org.springframework.context.event.SimpleApplicationEventMulticaster@255d17d7]
INFO - Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@33aae94f: defining beans [propertyPlaceholderConfigurer,dbWorker,connectionPool]; root of factory hierarchy
DEBUG - Returning cached instance of singleton bean 'propertyPlaceholderConfigurer'
DEBUG - Creating shared instance of singleton bean 'dbWorker'
DEBUG - Creating instance of bean 'dbWorker'
DEBUG - Eagerly caching bean 'dbWorker' to allow for resolving potential circular references
DEBUG - Creating shared instance of singleton bean 'connectionPool'
DEBUG - Creating instance of bean 'connectionPool'
DEBUG - Eagerly caching bean 'connectionPool' to allow for resolving potential circular references
DEBUG - Finished creating instance of bean 'connectionPool'
DEBUG - Finished creating instance of bean 'dbWorker'
DEBUG - Returning cached instance of singleton bean 'connectionPool'
DEBUG - Unable to locate LifecycleProcessor with name 'lifecycleProcessor': using default [org.springframework.context.support.DefaultLifecycleProcessor@4b1c2b67]
DEBUG - Returning cached instance of singleton bean 'lifecycleProcessor'
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
这只是您可能不需要的调试级别输出。本质上,它告诉您尚未定义任何覆盖其默认功能的特定类,因此它将使用默认功能。这里没什么可担心的。
This is just debug level output which you probably don't need. Essentially it's telling you that you haven't defined any particular classes which override its default functionality, so it's going to use the default functionality. There's nothing to worry about here.
如果您显式定义了这些 bean 中的任何一个,那么您可能会遇到问题,因为 Spring 会注入错误的类型,因为它找不到您的自定义 bean。但是,如果您尚未定义这些 bean,则这些消息是良性的。 Spring 只是让您知道正在使用默认 bean - 正如 @Phill 已经回答的那样。
If you have explicitly defined any of those beans then you might have a problem as Spring would be injecting the wrong type, since it is not finding your custom bean. However, if you have not defined these beans, then these messages are benign. Spring is just letting you know that the default bean is being used - as @Phill has already answered.