Rundeck seems to ignore log4j.properties

[Nick Tkach]

Where are you supposed to modify the log level for at least service.log?  We're running into a startup problem related to the database (Oracle 12) and the WARN level (default) only indicates a problem, but no details.  I've tried literally changing the log level for everything in $RDECK_BASE/server/exp/WEB-INF/classes/log4j.properties to DEBUG and it seems to make no difference at all.


(snippet from service.log)
2017-01-24 11:14:30.550:INFO:oejs.Server:jetty-7.6.0.v20120127
2017-01-24 11:14:32.652:INFO:oejw.StandardDescriptorProcessor:NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet
2017-01-24 11:14:33.668:INFO:/:Initializing Spring root WebApplicationContext
2017-01-24 11:14:48,391 [main] ERROR context.GrailsContextLoaderListener  - Error initializing the application: Error creating bean with name 'transactionManagerPostProcessor': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Invocation of init method failed; nested exception is java.lang.NullPointerException
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManagerPostProcessor': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Invocation of init method failed; nested exception is java.lang.NullPointerException
    at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:733)
    at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:233)
    at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1214)
    at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:676)
    at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:455)
    at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
    at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90)
    at org.eclipse.jetty.server.Server.doStart(Server.java:261)
    at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
    at com.dtolabs.rundeck.RunServer.run(RunServer.java:120)
    at com.dtolabs.rundeck.RunServer.main(RunServer.java:80)
    at com.dtolabs.rundeck.ExpandRunServer.invokeMain(ExpandRunServer.java:690)
    at com.dtolabs.rundeck.ExpandRunServer.execute(ExpandRunServer.java:647)
    at com.dtolabs.rundeck.ExpandRunServer.run(ExpandRunServer.java:304)
    at com.dtolabs.rundeck.ExpandRunServer.main(ExpandRunServer.java:113)

[Nick Tkach]

To answer my own question, what I was looking for was controlling logging for the embedded jetty and needed to add to the Java startup args "-Dorg.eclipse.jetty.LEVEL=DEBUG".  Apparently Jetty has its own logging facade which can do all sorts of things, but setting the startup level is set with that.