[Mulgara-dev] Query Logging - Maybe

Benjamin Hysell BenH at viewpointusa.com
Mon May 21 12:37:11 UTC 2012 

Everyone,

I’m still dogging this issue, I came in this morning and had a crash, see attached error log.  I’m learning my way through this log but something that caught my eye:

PSOldGen        total 5592448K, used 5592447K [0x0000000600000000, 0x0000000755560000, 0x0000000755560000)
  object space 5592448K, 99% used [0x0000000600000000,0x000000075555fff8,0x0000000755560000)
PSPermGen       total 24704K, used 24443K [0x00000005fae00000, 0x00000005fc620000, 0x0000000600000000)
  object space 24704K, 98% used [0x00000005fae00000,0x00000005fc5def98,0x00000005fc620000)

Is Mulgara keeping everything in memory, and could this be causing an issue?  I just upgraded the machine from 12gb to 32gb (it would have been 48gb, but Win2k8r2 standard limits the amount of ram available to the operating system to 32gb, you need enterprise to unlock up to 2tb of ram).

I’m also seeing these still pop up in the command window:
IDLE org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoi
nt at 68dbde9b
IDLE org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoi
nt at 4347a400

Any thoughts on where I could be pointed to start digging into this?

I setup the log4j as per Alex’s advice below so far the only item it kicked up is:

2012-05-21 01:51:45,909 WARN  [qtp1729094329-1818] http.TqlServlet - Error closing: TransactionalAnswer closed
org.mulgara.query.TuplesException: TransactionalAnswer closed
                at org.mulgara.resolver.TransactionalAnswer.notClosed(TransactionalAnswer.java:341)
                at org.mulgara.resolver.TransactionalAnswer.close(TransactionalAnswer.java:119)
                at org.mulgara.protocol.http.TqlServlet.doResponseList(TqlServlet.java:220)
                at org.mulgara.protocol.http.ProtocolServlet.handleUpdateQuery(ProtocolServlet.java:641)
                at org.mulgara.protocol.http.ProtocolServlet.doPost(ProtocolServlet.java:227)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
                at org.mulgara.protocol.http.ProtocolServlet.service(ProtocolServlet.java:202)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
                at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:527)
                at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:423)
                at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
                at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:930)
                at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:358)
                at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
                at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:866)
                at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
                at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
                at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113)
                at org.eclipse.jetty.server.Server.handle(Server.java:351)
                at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:594)
                at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:1042)
                at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:558)
                at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:211)
                at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:424)
                at org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoint.run(BlockingChannelConnector.java:291)
                at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436)
                at java.lang.Thread.run(Unknown Source)


From: mulgara-dev-bounces at mulgara.org [mailto:mulgara-dev-bounces at mulgara.org] On Behalf Of Benjamin Hysell
Sent: Sunday, May 13, 2012 9:19 PM
To: Mulgara Developers
Subject: Re: [Mulgara-dev] Query Logging

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> [mailto:mulgara-dev-bounces at mulgara.org]<mailto:[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/20120521/db13b019/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hs_err_pid760.log
Type: application/octet-stream
Size: 28593 bytes
Desc: hs_err_pid760.log
URL: <http://lists.mulgara.org/pipermail/mulgara-dev/attachments/20120521/db13b019/attachment-0001.obj>

More information about the Mulgara-dev mailing list