springboot启动不能加载数据库驱动Failed to determine a suitable driver class

 SLF4J: Class path contains multiple SLF4J bindings.

 SLF4J: Found binding in [jar:file:/G:/sharp/repo/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]

 SLF4J: Found binding in [jar:file:/G:/sharp/repo/org/slf4j/slf4j-log4j12/1.7.25/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]

 SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

 SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]

   .   ____          _            __ _ _

  /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \

 ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \

  \\/  ___)| |_)| | | | | || (_| |  ) ) ) )

   '  |____| .__|_| |_|_| |_\__, | / / / /

  =========|_|==============|___/=/_/_/_/

  :: Spring Boot ::        (v2.1.0.RELEASE)

 2019-01-09 15:32:12.690  INFO 5044 --- [           main] c.sharp.forward.SharpServiceApplication  : Starting SharpServiceApplication on hh-PC with PID 5044 (G:\worksheet\sharp-service\target\classes started by Administrator in G:\worksheet\sharp-service)

 2019-01-09 15:32:12.696  INFO 5044 --- [           main] c.sharp.forward.SharpServiceApplication  : No active profile set, falling back to default profiles: default

 log4j:WARN No appenders could be found for logger (com.alibaba.dubbo.common.logger.LoggerFactory).

 log4j:WARN Please initialize the log4j system properly.

 log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

 2019-01-09 15:32:14.095  INFO 5044 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)

 2019-01-09 15:32:14.113  INFO 5044 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]

 2019-01-09 15:32:14.113  INFO 5044 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet Engine: Apache Tomcat/9.0.12

 2019-01-09 15:32:14.121  INFO 5044 --- [           main] o.a.catalina.core.AprLifecycleListener   : The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [D:\topbandSoft\java\jre1.8\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;D:/topbandSoft/java/jre1.8/bin/server;D:/topbandSoft/java/jre1.8/bin;D:/topbandSoft/java/jre1.8/lib/amd64;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Java\jre7;D:\topbandSoft\java\jdk1.8\bin;D:\topbandSoft\java\jdk1.8\jre\bin;D:\topbandSoft\git\Git\cmd;D:\topbandSoft\svn\bin;D:\topbandSoft\maven\apache-maven-3.3.9-bin\apache-maven-3.3.9\bin;C:\Program Files\bin;D:\topbandSoft\zookeeper/bin;D:\topbandSoft\zookeeper/conf;D:\putty\;D:\topbandSoft\eclipse4.8\eclipse;;.]

 2019-01-09 15:32:14.217  INFO 5044 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext

 2019-01-09 15:32:14.218  INFO 5044 --- [           main] o.s.web.context.ContextLoader            : Root WebApplicationContext: initialization completed in 1465 ms

 2019-01-09 15:32:14.241  INFO 5044 --- [           main] o.s.b.w.servlet.ServletRegistrationBean  : Servlet dispatcherServlet mapped to [/]

 2019-01-09 15:32:14.245  INFO 5044 --- [           main] o.s.b.w.servlet.FilterRegistrationBean   : Mapping filter: 'characterEncodingFilter' to: [/*]

 2019-01-09 15:32:14.246  INFO 5044 --- [           main] o.s.b.w.servlet.FilterRegistrationBean   : Mapping filter: 'hiddenHttpMethodFilter' to: [/*]

 2019-01-09 15:32:14.246  INFO 5044 --- [           main] o.s.b.w.servlet.FilterRegistrationBean   : Mapping filter: 'formContentFilter' to: [/*]

 2019-01-09 15:32:14.246  INFO 5044 --- [           main] o.s.b.w.servlet.FilterRegistrationBean   : Mapping filter: 'requestContextFilter' to: [/*]

 2019-01-09 15:32:14.288  WARN 5044 --- [           main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'userService': Unsatisfied dependency expressed through field 'userMapper'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'userMapper' defined in file [G:\worksheet\sharp-mapper\target\classes\com\sharp\forward\mapper\UserMapper.class]: Unsatisfied dependency expressed through bean property 'sqlSessionFactory'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'sqlSessionFactory' defined in class path resource [org/mybatis/spring/boot/autoconfigure/MybatisAutoConfiguration.class]: Unsatisfied dependency expressed through method 'sqlSessionFactory' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.zaxxer.hikari.HikariDataSource]: Factory method 'dataSource' threw exception; nested exception is org.springframework.boot.autoconfigure.jdbc.DataSourceProperties$DataSourceBeanCreationException: Failed to determine a suitable driver class

 2019-01-09 15:32:14.289  INFO 5044 --- [           main] o.apache.catalina.core.StandardService   : Stopping service [Tomcat]

 2019-01-09 15:32:14.372  INFO 5044 --- [           main] ConditionEvaluationReportLoggingListener : 

 Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.

 2019-01-09 15:32:14.374 ERROR 5044 --- [           main] o.s.b.d.LoggingFailureAnalysisReporter   : 

 ***************************

 APPLICATION FAILED TO START

 ***************************

 Description:

 Failed to configure a DataSource: 'url' attribute is not specified and no embedded datasource could be configured.

 Reason: Failed to determine a suitable driver class

 Action:

 Consider the following:

     If you want an embedded database (H2, HSQL or Derby), please put it on the classpath.

     If you have database settings to be loaded from a particular profile you may need to activate it (no profiles are currently active).

按照网上各种查找参考https://blog.csdn.net/yl123456654321/article/details/82912901

最终发现问题出在了没有将配置文件扫描进去，我把它排除了，我的pom.xml中资源的配置如下：

 <resources>

     <resource>

         <directory>src/main/java</directory>

         <includes>

             <include>**/*.yml</include>

             <include>**/*.properties</include>

             <include>**/*.xml</include>

         </includes>

         <filtering>false</filtering>

     </resource>

     <resource>

         <directory>${basedir}/src/main/resources</directory>

         <excludes>

                 <!-- <exclude>*.properties</exclude> -->

                  <!-- <exclude>application-dev.properties</exclude>  -->

             </excludes>

         <includes>

             <include>**/*.yml</include>

             <include>application.properties</include>

             <include>application-${profile.active}.properties</include>

             <include>**/*.xml</include>

         </includes>

         <filtering>false</filtering>

     </resource>

 </resources>

问题出在上面注释掉的exclude的配置上，这里理解过滤不正确，我把它排除在外了,参考https://blog.csdn.net/u014756827/article/details/52510899

<include>与<exclude>是用来圈定和排除某一文件目录下的文件是否是工程资源的。如果<include>与<exclude>划定的范围存在冲突时，以<exclude>划定的范围为准。大多数情况下，人们使用<include>和<exclude>是为了配合<filtering>实现过滤特定文件的需要。例如，在一个工程中，src/main/resources目录下都是工程的资源文件，并不需要<include>和<exclude>再进行划定。但如果我们需要对且仅对其中的jdbc.properties和mail.properties两个文件进行过滤的话，则需要借助<include>和<exclude>进行如下的配置：

     <resources>

         <!-- Filter jdbc.properties & mail.properties. NOTE: We don't filter applicationContext-infrastructure.xml,

             let it go with spring's resource process mechanism. -->

         <resource>

             <directory>src/main/resources</directory>

             <filtering>true</filtering>

             <includes>

                 <include>jdbc.properties</include>

                 <include>mail.properties</include>

             </includes>

         </resource>

         <!-- Include other files as resources files. -->

         <resource>

             <directory>src/main/resources</directory>

             <filtering>false</filtering>

             <excludes>

                 <exclude>jdbc.properties</exclude>

                 <exclude>mail.properties</exclude>

             </excludes>

         </resource>

     </resources>

其中第一段<resource>配置声明：在src/main/resources目录下，仅jdbc.properties和mail.properties两个文件是资源文件，然后，这两个文件需要被过滤。而第二段<resource>配置声明：同样在src/main/resources目录下，除jdbc.properties和mail.properties两个文件外的其他文件也是资源文件，但是它们不会被过滤。

注释掉以后，可以加载属性文件，就可以启动了

巴特西

springboot启动不能加载数据库驱动Failed to determine a suitable driver class

最新文章

热门文章