[Mulgara-dev] Query Logging

[Benjamin Hysell]

See the attached error log running 2.1.13, maybe someone can see some insight.

My Mulgara server has 12 gb of memory and 11.9gb was mapped for Mulgara when the error messages started showing up.

-ben

From: mulgara-dev-bounces at mulgara.org [mailto:mulgara-dev-bounces at mulgara.org] On Behalf Of Alex Hall
Sent: Sunday, May 13, 2012 2:02 PM
To: Mulgara Developers
Subject: Re: [Mulgara-dev] Query Logging

On Fri, May 11, 2012 at 1:57 PM, Paul Gearon <gearon at ieee.org<mailto:gearon at ieee.org>> wrote:
<snip>
> 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.

If you're using the executable JAR file, it's set up by default to use a copy of conf/log4j-mulgara.xml embedded in the JAR file. To modify the logging configuration, save off a copy of that file somewhere and add its location as a URL to the command line using the -l (that's lower-case "L") flag, i.e.:

java -jar dist/mulgara-2.1.13.jar -l file:/path/to/log4j-mulgara.xml

You can then start mucking around with the Log4j configuration. I think a good place to start might be enabling debug logging in org.mulgara.resolver.DatabaseSession. IIRC, there's some gotcha where the threshold on the logfile appender defaults to INFO so you have to bump that up to DEBUG as well.

Alex


This E-Mail and any attachments thereto may contain confidential, privileged and ITAR controlled information. It is intended solely for the recipient(s) indicated. Any review, use, or distribution by anyone other than the intended recipient(s) is strictly prohibited. If you have received this E-Mail in error or are not the intended recipient, please notify the sender and delete all copies immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mulgara.org/pipermail/mulgara-dev/attachments/20120514/6a1fbf29/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hs_err_pid3824.log
Type: application/octet-stream
Size: 28611 bytes
Desc: hs_err_pid3824.log
URL: <http://lists.mulgara.org/pipermail/mulgara-dev/attachments/20120514/6a1fbf29/attachment-0001.obj>