You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Chao Long (JIRA)" <ji...@apache.org> on 2019/04/10 03:13:00 UTC

[jira] [Created] (KYLIN-3945) Debug in local get error "Invalid 'log4jConfigLocation' parameter"

Chao Long created KYLIN-3945:
--------------------------------

             Summary: Debug in local get error "Invalid 'log4jConfigLocation' parameter"
                 Key: KYLIN-3945
                 URL: https://issues.apache.org/jira/browse/KYLIN-3945
             Project: Kylin
          Issue Type: Bug
    Affects Versions: v2.6.2
            Reporter: Chao Long
            Assignee: Chao Long


严重: Exception sending context initialized event to listener instance of class org.apache.kylin.rest.util.Log4jConfigListener
java.lang.IllegalArgumentException: Invalid 'log4jConfigLocation' parameter: class path resource [kylin-server-log4j.properties] cannot be resolved to URL because it does not exist
 at org.springframework.web.util.Log4jWebConfigurer.initLogging(Log4jWebConfigurer.java:158)
 at org.springframework.web.util.Log4jConfigListener.contextInitialized(Log4jConfigListener.java:49)
 at org.apache.kylin.rest.util.Log4jConfigListener.contextInitialized(Log4jConfigListener.java:36)
 at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5157)
 at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5680)
 at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
 at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1707)
 at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1697)
 at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
 at java.util.concurrent.FutureTask.run(FutureTask.java)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)