Answers to: debug log on ivy server for application

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Mon, 22 Aug 2016 11:19:26 -0400

and another hint. the configuration changes in the log4jxml are not instantly applied to a running engine. the engine must be re-booted to change it's logger settings

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Mon, 22 Aug 2016 11:17:10 -0400

I guess that the category name is case sensitive. If so the name should be switched to : runtimelog.EventDashboard2.EventDashBoard2

Comment by Stelt0 on Reguel Wermelinger's answer

Stelt0 — Mon, 22 Aug 2016 10:09:34 -0400

Yes, I tried to configure it that way, but nothing happens.

this is my configuration:

appender name="RuntimeLog" class="org.apache.log4j.DailyRollingFileAppender"> 
  param name="File" value="${user.dir}/logs/EventDashBoard2.log"/> 
  param name="DatePattern" value="'.'yyyy-MM-dd"/> 
  layout class="org.apache.log4j.IvyLog4jLayout"> 
  param name="DateFormat" value="HH:mm:ss"/>
  /layout> 
/appender>

category name="runtimelog.EventDashBoard2.EventDashBoard2" class="ch.ivyteam.log.Logger">
  appender-ref ref="RuntimeLog"/> 
  priority value="DEBUG"/>
/category>

for this application and process:

Answer by Reguel Wermelinger

Reguel Wermelinger — Fri, 19 Aug 2016 10:24:10 -0400

You can change the debug level of the runtime log for an application: see http://developer.axonivy.com/doc/latest/EngineGuideHtml/monitoring.html#d5e4535

But there is no way to control the core engine logs to only show outputs if the logging API is used from a certain application.

See http://answers.axonivy.com/tags/logging/ for more information