[Mulgara-dev] Query Logging

Paul Gearon gearon at ieee.org
Fri May 11 17:57:12 UTC 2012


On Fri, May 11, 2012 at 12:35 PM, Benjamin Hysell <BenH at viewpointusa.com> wrote:
> I’m still back on version 2.1.8 and tried to jump up and upgrade to 2.1.13,
> however one of my queries is giving Mulgara an issues and I’m having a hard
> time tracking it down while my whole system is running.  If I take down all
> the non-offending applications and just run the one app I think is causing
> my problem I can’t reproduce the issue, hence I’d like to try to log which
> queries are giving me issues and what else is going on in the system when
> the issue appears.

I can only think of a couple of things that have changed that affect
the query path. Most of them are bug fixes, so I'd be upset to learn
if any of them were the problem. The only other one was a hack where
properties can now have a + or * modifier (similar to SPARQL 1.1).
It's a hack on the SPARQL 1.0 syntax so it's possible something isn't
right with it. You wouldn't happen to have either of those characters
in your query, would you?

Other than that, what do you mean when you say "issues"? Are you
getting back unexpected data, or does it hang, or give an exception?

> I know there is a logging system buried in Mulgara, but I’m not sure how to
> tap into it.  Is there anywhere someone can point me that would give me a
> start on how to turn it on and configure it?  I’m hoping for a simple primer
> and then maybe contact the list once I know a little something about it.  I
> scoured the wiki but either I missed it or I couldn’t find it.

Logging never seemed to work the way I wanted it to, so I can't give
you a definitive answer, sorry. However, it's supposedly set up using
conf/log4j-mulgara.xml, so you can try modifying that.

Paul


More information about the Mulgara-dev mailing list