myGrid

Enable default log4j logging to (rotated) file

Details

  • Type: Refinement Refinement
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.4, 1.5, 1.5.1
  • Fix Version/s: 1.6
  • Component/s: Taverna Core
  • Labels:
    None

Description

As it is difficult for our users to copy/paste tracebacks etc. from the console window, it would be much easier if we ship Taverna with a default log4j setting that writes to say $HOME/.taverna/logs/taverna.log and rotates the log when needed, to avoid clogging up the file system with useless logs.

The log could say "Taverna 1.5.0.1 blah blah" on startup as well, and including some links to the profile, sending this logfile to the mailing list (and to Jira!) should be a much easier way to report bugs.

We should provide the default log4j.properties as with the mygrid.properties so that the user can edit the file.

Issue Links

Activity

Hide
Stian Soiland-Reyes added a comment - 2007-01-16 15:56

The bundled log4j.properties now writes to $HOME/.taverna/logs/taverna.log using the RollingFileAppender.

The bundled log4j.properties is written out in commented form (similar to mygrid.properties) to $HOME/.taverna/conf/

The default log4j properties write everyting INFO and higher from Taverna-ish modules to the file, but only WARN and higher to the console.

Show
Stian Soiland-Reyes added a comment - 2007-01-16 15:56 The bundled log4j.properties now writes to $HOME/.taverna/logs/taverna.log using the RollingFileAppender. The bundled log4j.properties is written out in commented form (similar to mygrid.properties) to $HOME/.taverna/conf/ The default log4j properties write everyting INFO and higher from Taverna-ish modules to the file, but only WARN and higher to the console.

People

Vote (0)
Watch (0)

Dates

  • Created:
    2007-01-11 11:02
    Updated:
    2007-04-27 16:22
    Resolved:
    2007-01-17 09:37