[Pellet-users] Pellet logging

[Robert Davey]

Hi everyone,

In the end, we implemented the code posted by Alan, albeit in a more
Java-ey fashion :)

Grabbing the loggers from the KnowledgeBase, the KB's ABox, and the KB's
Taxonomy instances and setting the Level to Level.OFF solved the issue
for us.  I can post simple code if anyone is interested.

Many thanks!

Rob

On Tue, 2007-09-04 at 08:13 -0400, Evren Sirin wrote:
> On 8/31/07 7:06 AM, Robert Davey wrote:
> > Hi William,
> >
> > Thanks for the suggestion, but we are using the Manchester OWLAPI, not
> > Jena.  This is also not relevant to Eclipse as we want to turn off
> > logging to Tomcat's catalina.out 
> I think William's point is still relevant at this setting because 
> probably log4j is reading the configuration options from a different 
> file than you edited. Pellet comes with only warning and error logging 
> enabled by default. It should be another log4j configuration file that 
> is overriding these settings and the most common case is the 
> configuration file in jena.jar which enables info logging. Tomcat could 
> have other jar files in its classpath with similar configuration files 
> and I would suggest looking at Tomcat documentation for more information 
> about logging configuration.
> 
> Cheers,
> Evren
> 
> > - when we have multiple clients
> > accessing these Reasoner resources, there's going to be some penalty to
> > recording all these outputs.
> >
> > Cheers
> >
> > Rob
> >
> > On Fri, 2007-08-31 at 11:38 +0100, william fitzgerald wrote:
> >   
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> I am not sure if this relates to you but ...
> >>
> >> if these are occurring using eclipse IDE you need to make sure the
> >> pellet jar file is before the jena jar file when adding the to you path.
> >>
> >>
> >> Robert Davey wrote:
> >>     
> >>> Hi all,
> >>>
> >>> We're trying to turn off the logging feature of Pellet, especially the
> >>> quite large output you get when classifying for the first time.  We
> >>> tried changing the rootLogger options in the log4j.properties file
> >>> (substituting 'warn, stderr' for 'off') but this seems to make no
> >>> difference.  Is there a way to turn off output for Pellet completely?
> >>>
> >>> Cheers
> >>>
> >>> Rob
> >>>
> >>>       
> >> - --
> >> William M. Fitzgerald,
> >> PhD Student,
> >> Telecommunications Software & Systems Group,
> >> ArcLabs Research and Innovation Centre,
> >> Waterford Institute of Technology,
> >> WIT West Campus,
> >> Carriganore,
> >> Waterford.
> >> Office Ph: +353 51 302937
> >> Mobile Ph: +353 87 9527083
> >> Web: www.williamfitzgerald.org
> >>
> >>
> >>
> >> -----BEGIN PGP SIGNATURE-----
> >> Version: GnuPG v1.4.6 (GNU/Linux)
> >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >>
> >> iD8DBQFG1++mIcwlebz1MmwRAqw3AJ9Qy6IwjBnA7L7s4i6F1b6ndGpd3gCg+LlL
> >> h04QcOhJE9/jMHeHxIxIVVU=
> >> =eUES
> >> -----END PGP SIGNATURE-----
> >>     
> 
-- 
---------------------------------------
Dr. Rob Davey
NCYC / Institute of Food Research
Computational Biology / John Innes Centre
Norwich Research Park
Norwich, Norfolk, NR4 7HU

http://www.comparagrid.org/
http://cbr.jic.ac.uk/dicks/
---------------------------------------