Logging question (was RE: [Mulgara-dev] dateTime information being corrupted)

[Paul Gearon]

I wish I could help, but I've had trouble with the logging system for some
years (starting in 2001).  I remember in 2004 someone telling me something
that I hadn't been doing, but I forget what that was now.  :-)

I always found it frustrating.  I complained long and hard about this, and
it took 3 years before anyone bothered to help me... and that was with
people I was in the same office with!  :-)

If you're desperate, you can always do what I often resorted to, and lift
the default logging level across the system.  That seemed to work.  If it
got too verbose, I'd insert System.out.println() statements.  :-)

(this is a hint for someone who knows how to do this to document it.... and
TEST that the documented advice works).

Paul

On 11/6/06, David Moll <DMoll at viewpointusa.com> wrote:
>
>  I figured out how to set logging up, I have some questions about specific
> configurations.
>
> I added the following section to the log4j-conf.xml:
>
>   <category name="org.mulgara.resolver.store.StatementStoreResolver">
>     <priority value="debug"/>
>   </category>
>
> Which should enable the logging in the following section:
>
>  > Based on this assumption, you've already started to use logging, so can
> you turn on debug logging in:
>  >
> src/jar/resolver-store/java/org/mulgara/resolver/store/StatementStoreResolver.java
>  >
>  > Line 359 does this following log:
>  > logger.debug("Inserting statement: [" + statements.getSubject() + " "
>  >                                                 +
> statements.getPredicate() + " "
>  >                                                 + statements.getObject()
> + "] in " + model);
>  >
>  > This should tell you if the problem is the statement you retrieved (the
> log will contain the wrong value).  Or the statement you insert
>  > (the log will contain the correct value).
>
> However, I'm not getting anything from StatementStoreResolver.java, even
> when doing a manual insert into Mulgara.  I can turn debugging on for
> DatabaseSession.java, which inundates me with information, so I know
> that logging is work, I'm just never seeing any messages from
> StatementStoreResolver.
>
> ~Dave
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mulgara.org/pipermail/mulgara-dev/attachments/20061107/6eea90ff/attachment.htm>