JavaSpringTomcat:自定义数据源工厂被忽略

JavaSpringTomcat:自定义数据源工厂被忽略,java,mysql,spring,tomcat,jndi,Java,Mysql,Spring,Tomcat,Jndi,我正在从事一个项目,该项目要求在运行时解析数据库密码。通过在Tomcat配置中指定DataSourceFactory,我在本地有效地完成了这项工作。此过程防止任何凭证存储在纯文本配置文件中,并为我们提供自定义控件以在运行时解析密码。我在本地对此非常成功,但当我将解决方案移动到AWS上的真实/非嵌入式Tomcat实例时,我看到了以下错误: 无法在命名工厂上调用静态newInstance方法 类“org.apache.openjpa.jdbc.kernel.jdbcbbrokerfactory” 首

我正在从事一个项目,该项目要求在运行时解析数据库密码。通过在Tomcat配置中指定
DataSourceFactory
,我在本地有效地完成了这项工作。此过程防止任何凭证存储在纯文本配置文件中,并为我们提供自定义控件以在运行时解析密码。我在本地对此非常成功,但当我将解决方案移动到AWS上的真实/非嵌入式Tomcat实例时,我看到了以下错误:

无法在命名工厂上调用静态newInstance方法 类“org.apache.openjpa.jdbc.kernel.jdbcbbrokerfactory”

首先,关于这个错误消息有一些可疑的细节。第一(如下所示),tomcat配置文件中的my factory类被忽略,尽管其他凭据有效(例如用户名、密码等)

my
DataSourceFactory
的代码需要引用一个类来解析一个值。 以下是我对tomcat的xml配置:

<?xml version='1.0' encoding='UTF-8'?>
<Context useHttpOnly="false">
    <Resource auth="Container" name="mail/Session" type="javax.mail.Session"/>

    <Resource name="jdbc/jndi"
        auth="Container"
        scope="Shareable"
        type="javax.sql.DataSource"
        useLocalSessionState="true"
        cacheServerConfiguration="true"
        useServerPrepStmts="true"
        cachePrepStmts="true"
        cacheCallableStmts="true"
        elideSetAutoCommits="true"
        alwaysSendSetIsolation="false"
        enableQueryTimeouts="false"
        prepStmtCacheSize="250"
        prepStmtCacheSqlLimit="2048"
        maxActive="100"
        maxIdle="20"
        maxWait="10000"
        removeAbandoned="true"
        driverClassName="com.mysql.jdbc.Driver"
        url="${myURL}"
        username="${myUsername}"
        password="${myPasswordToResolve}"
        factory="my.class.CustomDatabaseConfigurationFactory"
        testOnBorrow="true"
        testWhileIdle="true"
        timeBetweenEvictionRunsMillis="20000"
        poolPreparedStatements="true"
        maxOpenPreparedStatements="50"
        validationQuery="select 1"
        validationInterval="60000"
        defaultTransactionIsolation="READ_COMMITTED"
    />

    <Valve className="org.apache.catalina.valves.CometConnectionManagerValve" />

    <Loader loaderClass="org.apache.catalina.loader.ParallelWebappClassLoader" />

    <Resource auth="Container"
        name="jms/JMSConnectionFactory"
        type="org.apache.activemq.pool.PooledConnectionFactory"
        description="JMS Connection Factory"
        factory="org.apache.activemq.jndi.JNDIReferenceFactory"
        brokerURL="my.URL"
        maxConnections="100"
        maximumActiveSessionPerConnection="50"
        expiryTimeout="10000"
    />
</Context>

实际上,当自定义数据工厂正在解决正确的密码时,这个问题永远不会发生

对于有此问题的其他人,有几件事:

除此之外,我在日志中没有看到任何与此相关的线索 配置错误的文件

这是一个死赠品,有东西没有被加载或伐木工人没有被正确设置。在我意识到log4j没有正确配置之后,我能够看到我的工厂实际上正在加载。后来,在看到结果后,我发现为数据库设置的密码不正确

虽然日志错误的级别太高,并且没有足够的详细信息,但是这个问题可以通过基本的调试方法解决,并且可以通过注意日志记录来避免

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [spring/dataaccess/openjpa/openjpa.xml]: Invocation of ini\
t method failed; nested exception is <openjpa-2.4.0-ep2.1-runknown fatal user error> org.apache.openjpa.persistence.ArgumentException: Could not invoke the static newInstance method on the named fact\
ory class "org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory".
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1514)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:521)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:191)
        at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1119)
        at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:924)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)
        at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:410)
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:306)
        at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5118)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5634)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:679)
        at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1966)
        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)
        at java.lang.Thread.run(Thread.java:748)