We are experiencing potential memory leak on our sesame server remotely accessed during some write operations. Read queries do not keep memory allocated. Monitoring with jconsole, some write operations leave something like 100MB in the memory "Old gen".

Tested with OWLIM-SE-5.4.6863 + Sesame 2.7.8, GRAPHDB-SE-6.1.RC1 + Sesame 2.7.8, GRAPHDB-SE-6.1.RC1 + Sesame 2.7.14. Configuration OWLIM with 1GB cache-memory and tomcat with 8GB heap memory.

Tried to close connections, sessions, repositorymanager and so on without any improvement.

What should I look at to find out the cause?

Thank you in advance

William Sandri

Business Process Engineering S.r.l. www.bpeng.com

asked 23 Feb '15, 06:40

wsandri's gravatar image

wsandri
16112
accept rate: 0%

I kept investigating and created several heapdumps. Comparing them, it turns out that there is one instance of com.ontotext.trree.big.collections.j that keeps growing.

(26 Feb '15, 10:55) wsandri
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×18
×14
×4

Asked: 23 Feb '15, 06:40

Seen: 5,342 times

Last updated: 26 Feb '15, 10:55

powered by BitNami OSQA