奇怪的Tomcat 8部署行为

当我安装上运行的ext3基于Java 1.8.0_92在CentOS 6.7，我得到以下错误部署我的春节4.0.1.RELEASE web应用到Tomcat 8.0.33：奇怪的Tomcat 8部署行为

org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'qualityAuditTokenService' defined in URL [jar:file:/home/www/webapps/ROOT/WEB-INF/lib/product-service-2.0.1-SNAPSHOT.jar!/com/company/product/services/QualityAuditTokenService.class]: Unsatisfied dependency expressed through constructor argument with index 0 of type [com.company.workflow.dao.TokenDao]: : No qualifying bean of type [com.company.workflow.dao.TokenDao] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {}; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type [com.company.workflow.dao.TokenDao] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {} 
    at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:742) 
    at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196) 
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1114) 
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1017) 
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:504) 
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:475) 
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:304) 
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228) 
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:300) 
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:195) 
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:700) 
    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:760) 
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) 
    at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:403) 
    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:306) 
    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:106) 
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4811) 
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5251) 
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147) 
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725) 
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701) 
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717) 
    at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1092) 
    at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1834) 
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
    at java.lang.Thread.run(Thread.java:745) 
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type [com.company.workflow.dao.TokenDao] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {} 
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.raiseNoSuchBeanDefinitionException(DefaultListableBeanFactory.java:1100) 
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:960) 
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:855) 
    at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:806) 
    at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:734) 
    ... 28 more

但是，如果我将安装完全相同的Web应用程序安装到在CentOS 6.7上的Java 1.8.0_92上运行的NFS装载上安装的Tomcat 8.0.33，则它工作得很好。如果我将它安装到Centos上的ext3上的Tomcat 7.0.69，Ubuntu上的ext4上的Tomcat 8.0.33以及Windows上的NTFS上，它也可以正常工作。所以它只是把这个错误在CentOS上的ext3上的Tomcat 8.0.33上运行。如果这不是我们的实时部署环境，那不会有太大的问题。

所以这显然不是标准的“缺少注释”或“JAR类型中缺少的bean类”之类的问题，尽管我很乐意听到这种情况下的建议，以免我错过了某些东西。

这个部署的奇怪之处在于Spring bean在不同的文件系统上以不同的顺序创建。在这项工作中的版本，在日志文件中会显示以下的用Spring记录刷爆：

DEBUG DefaultListableBeanFactory:449 - Creating instance of bean 'tokenDaoHbm' 
DEBUG DefaultListableBeanFactory:249 - Returning cached instance of singleton bean 'sessionFactory' 
DEBUG DefaultListableBeanFactory:249 - Returning cached instance of singleton bean 'searchSessionFactory' 
DEBUG DefaultListableBeanFactory:750 - Autowiring by type from bean name 'tokenDaoHbm' via constructor to bean named 'sessionFactory' 
DEBUG DefaultListableBeanFactory:523 - Eagerly caching bean 'tokenDaoHbm' to allow for resolving potential circular references 
DEBUG DefaultListableBeanFactory:249 - Returning cached instance of singleton bean 'org.springframework.transaction.config.internalTransactionAdvisor' 
DEBUG DefaultListableBeanFactory:249 - Returning cached instance of singleton bean 'org.springframework.cache.config.internalCacheAdvisor' 
DEBUG AnnotationTransactionAttributeSource:108 - Adding transactional method 'TokenDaoHbm.update' with attribute: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; '' 
DEBUG InfrastructureAdvisorAutoProxyCreator:551 - Creating implicit proxy for bean 'tokenDaoHbm' with 0 common interceptors and 1 specific interceptors 
DEBUG JdkDynamicAopProxy:117 - Creating JDK dynamic proxy: target source is SingletonTargetSource for target object [[email protected]] 
DEBUG DefaultListableBeanFactory:477 - Finished creating instance of bean 'tokenDaoHbm'

这是一个能够满足了它创建的依赖豆 - 在抛出异常的版本，这个bean创建是值得注意的是它的缺席。

TL; DR

那么，怎样才能操作系统，文件系统类型和/或网络延迟改变Spring的创建豆的顺序（或以其他方式打破它的相关性分析）？这肯定是在WAR文件中提供的东西（以及与它打包的Spring版本）？

我试图通过@ComponentScan和@Qualifier来影响bean创建无济于事 - 还有其他方法吗？

此问题与下面链接的问题类似，但没有发布解决方案（并且它们遇到了Tomcat 7而不是8问题）。 Need help debugging Tomcat 7 application error

任何与此有关的帮助非常感谢，因为这一个真让我烦恼！ :-D

来源

2016-04-26 Matt Innes

我现在有一个解决方案（因此发布了一个答案），但它屁股很蠢，我仍然没有解释为什么这是必要的（所以我会保存为更优雅的解决方案或完整的解释）。

原来发行57129对ASF的Bugzilla提出了我的问题是关于： https://bz.apache.org/bugzilla/show_bug.cgi?id=57129

然而，概括那里的情况下，WAR中的多个JAR文件包含不同版本的同一类文件。这意味着改变顺序会改变应用程序的行为 - 这不是理想的。

在我的情况下，有问题的类TokenDaoHbm只在WAR文件中存在一次。只是这样，如果在Spring实例化qualityAuditTokenService bean时Tomcat类加载器尚未加载product-dao-hibernate-2.0.1-SNAPSHOT JAR文件，那么您将得到一个NoSuchBeanDefinitionException异常。当然，Spring和/或Tomcat必须知道所有类必须在bean实例化开始之前加载？

<Resources> 
    <PreResources className="org.apache.catalina.webresources.FileResourceSet" 
       base="${catalina.base}/webapps/ROOT/WEB-INF/lib/product-dao-hibernate-2.0.1-SNAPSHOT.jar" 
       webAppMount="/WEB-INF/lib/product-dao-hibernate-2.0.1-SNAPSHOT.jar" /> 
</Resources>

如果任何人都可以进一步阐明：

因此，要解决我的问题，我根据马克·托马斯在ASF错误张贴的意见放在下面我的应用程序的context.xml在WAR在此我很乐意将它们标记为已接受的答案。

来源

2016-04-26 14:46:36

奇怪的Tomcat 8部署行为

回答

相关问题