使用springtest获取druid配置的DataSource时的资源文件出错

最新推荐文章于 2025-06-03 14:42:37 发布
原创 最新推荐文章于 2025-06-03 14:42:37 发布 · 1.1k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#druid #springtest #properties

本文探讨了Spring框架中属性占位符解析失败的问题，特别是在加载dataSource配置时遇到的Could not resolve placeholder 'db.druid.driverClassName'错误。通过修改配置，将驱动类名改为直接指定的方式，成功解决了这一问题。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

测试程序：

package com.mxx.test;

import org.junit.Test;
import org.junit.runner.RunWith;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.context.annotation.Configuration;
import org.springframework.test.context.ContextConfiguration;
import org.springframework.test.context.junit4.SpringJUnit4ClassRunner;

import javax.sql.DataSource;

@ContextConfiguration(locations = {"classpath:spring/spring-base.xml"})
@RunWith(SpringJUnit4ClassRunner.class)
public class JDBCTest {
    @Autowired
    private DataSource dataSource ;
    @Test
    public void testDataSource() {
        System.out.println(this.dataSource);
    }
}

spring-base.xml文件加载进了properties文件：

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:context="http://www.springframework.org/schema/context"
       xsi:schemaLocation="http://www.springframework.org/schema/beans
       http://www.springframework.org/schema/beans/spring-beans.xsd
       http://www.springframework.org/schema/context
       https://www.springframework.org/schema/context/spring-context.xsd">
    <!-- 1、配置扫描包 -->
    <context:component-scan base-package="com.mxx.ssm.dao,com.mxx.ssm.service,com.mxx.test,com.mxx.ssm.config"/>

    <!-- 2、加载配置文件-->
    <context:property-placeholder location="classpath:*.properties"  />
    <!-- 3、导入其他spring配置文件-->
    <import resource="spring-datasource.xml"/>
    <import resource="spring-mybatis.xml"/>
    <import resource="spring-shiro.xml"/>
    <import resource="spring-transaction.xml"/>
    <import resource="spring-shiro-cache.xml"/>
</beans>

错误输出：

Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder 'db.druid.driverClassName' in value "${db.druid.driverClassName}"
	at org.springframework.util.PropertyPlaceholderHelper.parseStringValue(PropertyPlaceholderHelper.java:178) ~[spring-core-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.util.PropertyPlaceholderHelper.replacePlaceholders(PropertyPlaceholderHelper.java:124) ~[spring-core-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.core.env.AbstractPropertyResolver.doResolvePlaceholders(AbstractPropertyResolver.java:237) ~[spring-core-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.core.env.AbstractPropertyResolver.resolveRequiredPlaceholders(AbstractPropertyResolver.java:211) ~[spring-core-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.context.support.PropertySourcesPlaceholderConfigurer.lambda$processProperties$0(PropertySourcesPlaceholderConfigurer.java:175) ~[spring-context-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.resolveStringValue(BeanDefinitionVisitor.java:296) ~[spring-beans-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.resolveValue(BeanDefinitionVisitor.java:217) ~[spring-beans-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.visitPropertyValues(BeanDefinitionVisitor.java:147) ~[spring-beans-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.visitBeanDefinition(BeanDefinitionVisitor.java:85) ~[spring-beans-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.beans.factory.config.PlaceholderConfigurerSupport.doProcessProperties(PlaceholderConfigurerSupport.java:225) ~[spring-beans-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.context.support.PropertySourcesPlaceholderConfigurer.processProperties(PropertySourcesPlaceholderConfigurer.java:182) ~[spring-context-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.context.support.PropertySourcesPlaceholderConfigurer.postProcessBeanFactory(PropertySourcesPlaceholderConfigurer.java:157) ~[spring-context-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:286) ~[spring-context-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:166) ~[spring-context-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:705) ~[spring-context-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:531) ~[spring-context-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:128) ~[spring-test-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:60) ~[spring-test-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.delegateLoading(AbstractDelegatingSmartContextLoader.java:275) ~[spring-test-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.loadContext(AbstractDelegatingSmartContextLoader.java:243) ~[spring-test-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:99) ~[spring-test-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:117) ~[spring-test-5.1.7.RELEASE.jar:5.1.7.RELEASE]
	... 24 more

java.lang.IllegalStateException: Failed to load ApplicationContext

	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:125)
	at org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:108)
	at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:118)
	at org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:83)
	at org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:246)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:227)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:289)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:291)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:246)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
	at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:190)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
	at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
	at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'dataSource' defined in class path resource [spring/spring-datasource.xml]: Could not resolve placeholder 'db.druid.driverClassName' in value "${db.druid.driverClassName}"; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder 'db.druid.driverClassName' in value "${db.druid.driverClassName}"
	at org.springframework.beans.factory.config.PlaceholderConfigurerSupport.doProcessProperties(PlaceholderConfigurerSupport.java:228)
	at org.springframework.context.support.PropertySourcesPlaceholderConfigurer.processProperties(PropertySourcesPlaceholderConfigurer.java:182)
	at org.springframework.context.support.PropertySourcesPlaceholderConfigurer.postProcessBeanFactory(PropertySourcesPlaceholderConfigurer.java:157)
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:286)
	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:166)
	at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:705)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:531)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:128)
	at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext(AbstractGenericContextLoader.java:60)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.delegateLoading(AbstractDelegatingSmartContextLoader.java:275)
	at org.springframework.test.context.support.AbstractDelegatingSmartContextLoader.loadContext(AbstractDelegatingSmartContextLoader.java:243)
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:99)
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:117)
	... 24 more
Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder 'db.druid.driverClassName' in value "${db.druid.driverClassName}"
	at org.springframework.util.PropertyPlaceholderHelper.parseStringValue(PropertyPlaceholderHelper.java:178)
	at org.springframework.util.PropertyPlaceholderHelper.replacePlaceholders(PropertyPlaceholderHelper.java:124)
	at org.springframework.core.env.AbstractPropertyResolver.doResolvePlaceholders(AbstractPropertyResolver.java:237)
	at org.springframework.core.env.AbstractPropertyResolver.resolveRequiredPlaceholders(AbstractPropertyResolver.java:211)
	at org.springframework.context.support.PropertySourcesPlaceholderConfigurer.lambda$processProperties$0(PropertySourcesPlaceholderConfigurer.java:175)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.resolveStringValue(BeanDefinitionVisitor.java:296)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.resolveValue(BeanDefinitionVisitor.java:217)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.visitPropertyValues(BeanDefinitionVisitor.java:147)
	at org.springframework.beans.factory.config.BeanDefinitionVisitor.visitBeanDefinition(BeanDefinitionVisitor.java:85)
	at org.springframework.beans.factory.config.PlaceholderConfigurerSupport.doProcessProperties(PlaceholderConfigurerSupport.java:225)
	... 36 more


Process finished with exit code -1

目前的解决方法：

db.druid.driver=org.gjt.mm.mysql.Driver

不再使用db.druid.driverClassName

全网最详细的Spring Boot 整合数据源Druid DataSource以及监控mysql数据库的性能
念兮为美
02-06 3989
全网最详细的Spring Boot 整合数据源Druid DataSource以及监控mysql数据库的性能
DruidDataSource一直closing，如何解决?
**My Coding Family**
02-05 759
通过限制数据源的动态刷新范围、优化配置文件管理以及检查版本兼容性，可以有效避免被频繁销毁的问题。如果问题仍然存在，可以通过添加日志和断点进一步定位触发刷新事件的具体原因。希望如上措施及解决方案能够帮到有需要的你。PS：如若遇到采纳如下方案还是未解决的同学，希望不要抱怨&&急躁，毕竟影响因素众多，我写出来也是希望能够尽最大努力帮助到同类似问题的小伙伴，即把你未解决或者产生新Bug黏贴在评论区，我们大家一起来努力，一起帮你看看，可以不咯。
druid作为数据库连接池的几种配置总结，通过debug去跟配置结果
神韵
08-08 1万+
整篇文章基于SpringBoot2.2.6编写。不同SpringBoot配置存在某些差异，后面会提。 默认的数据连接池 application.yml配置 spring: #数据源配置，使用默认的数据库连接池 datasource: driver-class-name: com.mysql.cj.jdbc.Driver url: jdbc:mysql://localhost:3306/essm_dev?useUnicode=true&characterEncoding=u
spring boot 两个yml文件 无法读取到配置信息
qq_38377190的博客
08-09 3992
最近在使用spring boot，想将application.yml中的数据库部分配置信息抽离出来。实现如下效果 抽离后发现，application-druid.yml配置信息读取不到。 网上查了一堆最后找到了原因。被自己蠢哭了。（这就是不熟悉spring boot的下场，学习嘞。） 觉得本文章对您有帮助，那么可以选择打赏。 打赏多少，您高兴就行，谢谢您对我的支持！ ~(@^_^@)...
spring properties的引入
Here I Am
11-01 169
Could not resolve placeholder ‘jdbc.driver‘ in string value “${jdbc.driver}“
qq_25073223的博客
11-01 1418
Could not resolve placeholder 'jdbc.driver' in string value "${jdbc.driver}"
java.lang.IllegalArgumentException: Could not resolve placeholder ‘jdbc.driver‘ in value “${jdbc.dri
qq_50721879的博客
08-01 2308
解决java.lang.IllegalArgumentException: Could not resolve placeholder 'jdbc.driver' in value "${jdbc.driver}和 Access denied for user 'Administrator'@'localhost' (using password: NO)的问题
SpringJPA+Druid配置多数据源
wtopps的专栏
08-07 592
SpringJPA配置多数据源
Spring Boot使用Druid和监控配置方法
08-30
spring.datasource.type=com.alibaba.druid.pool.DruidDataSource # 数据库驱动类名 spring.datasource.driver-class-name=com.mysql.jdbc.Driver # 数据库连接信息 spring.datasource.url=jdbc:mysql://localhost...
Spring Boot整合Druid与Dynamic-Datasource多数据源配置：从错误到完美解决
最新发布
weixin_45131680的博客
06-03 1384
摘要：本文分析了Spring Boot 2.7整合Druid连接池和Dynamic-Datasource时出现的DataSource returned null from getConnection()错误。主要原因为自动配置冲突、连接池类型未指定、多数据源配置错误。解决方案包含五个关键步骤：1）排除HikariCP和Druid自动配置；2）正确配置application.yml文件；3）删除手动创建的DataSource Bean；4）确保@DS注解与配置一致；5）处理跨数据源事务。通过调整依赖关系和配置
使用druid读取配置文件失败的解决方案
weixin_44046859的博客
06-27 2754
使用druid读取配置文件失败的解决方案
【踩坑记录】解决 Could not resolve placeholder 'xxx' in string value "${xxx}"
热门推荐
名侦探张六儿的博客
04-10 10万+
一般来说报Could not resolve placeholder 'xxx' in string value "${xxx}" 错误的原因都是由于项目中有多个地方的xml文件中用到了 <context:property-placeholder location="classpath:xxx.properties"/> 或者是 <bean id="propertyCon...
Could not resolve placeholder 'driverClasss' in string value "${driverClasss}"
Ethan_Fu的专栏
08-07 4032
spring配置：spring-datasource.xml                                          classpath*:/spring/jdbc.properties                         jdbc配置：jdbc.properites driverClassName=org.gjt.m
在spring配置文件中设置读取jdbc.properties配置文件的时候报错
复制乔布斯
07-13 1万+
日期： 2016-7-13 内容： spring配置问价出错； 1、 spring配置文件配置数据库连接： <beans xmlns="http://www.springframework.org/schema/beans" xmlns:context="http://www.springframework.org/schema/context" xmlns:xsi="
Could not resolve placeholder 'xxx' in value "${xxx}" 解决方法
weixin_44542124的博客
08-19 1万+
出现此异常其原因是因为spring配置文件中同时出现了两个或多个properties配置文件： 解决办法是在配置后面都加上ignore-unresolvable=”true”
spring-test
m0_59194246的博客
06-01 9140
1. 基于Spring的测试Spring Test主要解决了以下问题：– 在普通测试环境下，当需要使用Spring时，需要手动加载Spring配置，且手动从 Spring容器中获取对象，使用Spring Test后，只需要通过注解指定Spring配置类， 在Spring容器中的对象均可自动装配– 通过@Sql等注解，对数据库编程的测试提供了更好的支持使用Spring Test时需添加的依赖项为：spring-test ● 注意：你仍需另外添加测试的依赖项● 注意：需要与其它的spring-?
Could not resolve placeholder ‘name‘ in value “${name}“报错解决
wowolz的博客
10-27 9528
今天配置动态拉取Nacos Config，写完NacosController时启动Spring Cloud时报错： Could not resolve placeholder 'name' in value "${name}" 第一次尝试解决： 百度之后查询到以下原因： springboot启动时会检索 @Value 对应配置文件中的key，当该key不存在时就会报：Caused by: java.lang.IllegalArgumentException: Could not reso..
springboot 使用DruidDataSource 数据源
weixin_30698527的博客
08-09 2859
一、添加依赖 <dependency> <groupId>com.alibaba</groupId> <artifactId>druid</artifactId> <version>1.0.26</version> </dependency&gt...
java was datasource_使用Spring Boot配置Druid时dataSource无法被autowired
weixin_42300144的博客
02-20 1142
配置好了dataSource之后，想测试一下有没有配置成功package com.yang.Controller;import com.alibaba.druid.pool.DruidDataSource;import org.springframework.beans.factory.annotation.Autowired;import org.springframework.web.bind...
Spring Boot 集成Druid详细配置解析
当添加了`druid-spring-boot-starter`依赖后，Druid与Spring Boot的集成会变得非常简单，因为它已经内置了必要的配置，开发者只需要在配置文件中填写数据库的相关配置即可。 ### 结语 将Spring Boot与Druid连接池...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值