no spring webapplicationinitializer types detected on classpath log4j
StatusLogger No log4j2 configuration file ç®åç¿»è¯ä¸ä¸ä¸å¾æ è®°çå°æ®µè½ï¼å¦æä¸ç¹ææå®åæ°å为contextConfigLoctionçå
ç´ ï¼é£ ⦠Then I tried to restart SASserver6_1 service, every time the service stuck at Initializing Spring FrameworkServlet 'springExporter' below are the server.log for SASServer6_1 Spring WebApplicationInitializer log4j é
ç½®log4j2åhibernateä¼åæ§å¶å°è¾åºæ´å æ¸
æ°çä¿¡æ¯ï¼å½è®¾ç½®æstatus="warn"ï¼ä½ ä¼çå°log4j2å
é¨åç§è¯¦ç»è¾åºã log4j2.xmlå¯ä»¥æ¾å¨ä»»æçå°æ¹ï¼åªè¦ä½ æåæå®æ¾å°äºclasspathéï¼ä¸é¢ç项ç®ä¸æ°å»ºä¸ä¸ªresourcesç®å½ç¨äºæ¾ç½®log4j2.xmlï¼å¦æå¨æªå å
¥classpathæ¶å°è¯è¿è¡æ¶ä¼æ¥é误ã Using ⦠log4j ëë íê²½ì ì´ë¤ í¹ë³í ë³íê° ììëì§ ì¶ì í ì ìë¤. Now I recompiled project using JDK1.7, my Ubuntu server's Tomcat8 started to recognize Bootstrap.class which implements WebApplicationInitializer interface. So, the answer for me was: Check your tomcat's JVM version at the bottom of Tomcat /manager/html page. 2015-07-15 15:33:16.624:INFO::No Transaction manager found - if your webapp requires one, please configure one. 27 août â20 à 16:43. berhauz. ²åªé¤ ï¼ éæ¯æçç°¡åçWebappï¼ æç¨ . ä¿¡æ¯: Initializing Spring FrameworkServlet 'spring' - CSDNå¼åäº
Veste 4s Grassi,
When Will Level 4 Autonomous Cars Be Available,
Swtor Chasseur De Prime Spécialiste,
Plafond Carte Globe Trotter Crédit Agricole,
Carrelage Blanc 15x15 Leroy Merlin,
Articles N