Bug Note-Spring---Tomcat error: severe:one or more listeners failed to start.

Emmm, the spring framework has recently been learned almost, because recently to start the iteration of the Group Library Management System 2.0, there is less time to summarize the spring in action notes, so take the spring learning notes for a period of time ~ 1. Bug Description: Start the Tomcat times error when writing the spring code. 2. Bug information:

Connected to server [2017-11-16 09:28:36,551] Artifact Spring_10:war exploded:artifact are being deployed, please wait ... Nov 9:28:37 PM org.apache.catalina.loader.WebappClassLoaderBase validatejarfile info:validatejarfile (/home/ dela/ideaprojects/spring/spring_10/out/artifacts/spring_10_war_exploded/web-inf/lib/ Javax.servlet-api-3.1.0.jar)-jar not loaded. See Servlet Spec 3.0, section 10.7.2.
Offending Class:javax/servlet/servlet.class Nov 9:28:38 PM org.apache.catalina.deploy.WebXml setversion Warning:unknown version string [3.1].
Default version would be used. Nov 9:28:42 PM org.apache.catalina.startup.TaglibUriRule body info:tld skipped. Uri:http://www.springframework.org/tags is already defined Nov 9:28:42 PM Org.apache.catalina.startup.TaglibUriRule body Info:tld skipped. Uri:http://www.springframework.org/tags/form is already defined Nov 9:28:42 PM Org.apache.catalina.startup.TldConfig Execute Info:at least one JAR was scanned For TLDs yet contained no TLDs. Enable debug logging for the logger for a all list of JARs that were scanned but no TLDs were found in them.
Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
slf4j:failed to load Class "Org.slf4j.impl.StaticLoggerBinder". Slf4j:defaulting to No-operation (NOP) Logger implementation Slf4j:see http://www.slf4j.org/codes.html#
Staticloggerbinder for further details. Nov 9:28:43 PM org.apache.catalina.core.StandardContext startinternal **severe:one or more listeners failed to s Tart. Full details would be found in the appropriate container log file** Nov 9:28:43 PM Org.apache.catalina.core.Standa Rdcontext startinternal Severe:context [] startup failed due to previous errors [2017-11-16 09:28:43,528] Artifact Spring _10:war Exploded:error during artifact deployment. See server log for details.

3. Bug fixes:

This bug is pretty weird, it's weird in idea error message only one sentence: Severe:one or more listeners failed to start. Full details'll be found in the appropriate container log file, which prompts you to check the error log, but the error log under idea is empty! This is very awkwardness embarrassed, because only by this sentence, there is no way to locate the error where. (1) Find the error log

Asked Heng Yi before, he said if there is no error log under Idea, go to the logs directory under the Tomcat installation package to find, but however did not find, only a few long ago error log.

Later only to know that the error log in/home/dela/. Intellijidea2017.1/system/tomcat/unnamed_spring_10 (the name of the current project), which is the home directory. Intellijidea2017.1/system/tomcat, and then find the Tomcat name of the project and enter the logs directory to see the error log of the day.

I found the cause of the problem in Localhost.2017-11-16.log, the error message is as follows:

caused by:java.io.FileNotFoundException:Could not open ServletContext resource [/classpath*:d b-config.properties] At
    Org.springframework.web.context.support.ServletContextResource.getInputStream ( servletcontextresource.java:141) at
    Org.springframework.core.io.support.EncodedResource.getInputStream ( encodedresource.java:153) at
    org.springframework.core.io.support.PropertiesLoaderUtils.fillProperties ( propertiesloaderutils.java:98) at
    Org.springframework.core.io.support.PropertiesLoaderSupport.loadProperties (propertiesloadersupport.java:175) At
    Org.springframework.core.io.support.PropertiesLoaderSupport.mergeProperties ( propertiesloadersupport.java:156) at
    Org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory ( PROPERTYRESOURCECONFIGURER.JAVA:80)
    ... More

(2) Problem solving

because one of my XML files has a wrong path when loading the properties profile, and I put it in the Resources directory (but it's unclear why it won't be found in the resources directory) , cause the file cannot be loaded, put this file into Web-inf, through the/web-inf/db-config.properties can be accessed loaded!