Trouble shooting using logfiles

The different ROB-EX components all use the Logback framework for logging. Each component has its own logfile located in a folder as part of the installed location of the component.

For more info on the logback.xml format, see the logback manual.

The following contains use-full packages where logging can be increased to DEBUG/TRACE, in order to troubleshoot a particular problem. TRACE is the highest level potentially producing very high volumes of logging data.

ROB-EX Scheduler Multiuser Server log-file

  <!-- Setting this to DEBUG generates a log row with field level changes written to the database   -->
  <logger name="EntityUpdateLog" level="DEBUG" />

  <!-- Enable DEBUG or TRACE logging to print SQL queries to the log -->
  <logger name="org.jooq" level="INFO" />

  <!-- Enable TRACE logging for HEAVY debug of the whole server -->
  <logger name="gantt.server" level="INFO" />

  <!-- Enable TRACE logging for HEAVY debug of the client registry -->
  <logger name="gantt.server.registry" level="INFO" />
  <logger name="gantt.server.clireg" level="INFO" />

  <!-- Enable TRACE logging for HEAVY debug of the event store -->
  <logger name="gantt.server.eventstore" level="INFO" />

  <!-- Enable TRACE logging for HEAVY debug of authentication or active directory -->
  <logger name="gantt.server.auth" level="INFO" />
  <logger name="gantt.server.auth.ad" level="INFO" />

  <!-- Enable TRACE logging for HEAVY debug of Portal (Server CQ) -->
  <logger name="gantt.cq" level="INFO" />
  <logger name="gantt.server.cq" level="INFO" />

  <!-- Enable TRACE logging for HEAVY debug of Gateway functionality -->
  <logger name="gantt.server.gateway" level="INFO" />

ROB-EX Scheduler Desktop Client/Integration Client log-file

<!-- SCHEDULING -->

	<!-- Change to TRACE to debug scheduling graph creation -->
	<logger name="debug.schedulePopulator" level="INFO" />

	<!-- Change to TRACE to debug scheduling -->
	<logger name="debug.scheduler" level="INFO" />
	<logger name="debug.scheduleOnResource" level="INFO" />
	<logger name="debug.scheduleResourceWorkload" level="INFO" />

<!-- DATA CALCULATION -->
	<!-- Change to TRACE to debug operation all operation/workload calculation -->
	<logger name="debug.worktimeCalculator" level="INFO" />

	<!-- Remove debug info about contraint arcs being created -->
	<logger name="gantt.basemodel.basic" level="INFO" />

	<!-- Change to TRACE for heavy debugging all basemodel data in robex -->
	<logger name="gantt.basemodel" level="INFO" />

<!-- REST WEB SERVICE -->
	<!-- Change to TRACE for heavy debugging of rest services -->
	<logger name="gantt.rest" level="INFO" />

<!-- CQ SERVICES (WEB PLANNER ON PlannerIC) -->
	<!-- Change to TRACE for heavy debugging of All CQ services-->
	<logger name="gantt.cq" level="INFO" />
	<!-- Change to TRACE for heavy debugging of CQ Query service (what data is sent to web client)-->
	<logger name="gantt.cq.gateway.query.impl" level="INFO" />
	<!-- Change to TRACE for heavy debugging of RObex specific CQ functionality (auth, entities etc.)-->
	<logger name="gantt.cq.robex" level="INFO" />
	<!-- Change to TRACE for heavy debugging of job execution (mostly web planner for now) -->
	<logger name="gantt.utils.jobs" level="INFO" />

<!-- MULTIUSER/CLIENT COMMUNICATION -->
	<!-- Change to TRACE for heavy debugging multiuser communication -->
	<logger name="gantt.server" level="INFO" />
	<logger name="gantt.multiuser" level="INFO" />