On 13/05/16 09:45, Sorin Gheorghiu wrote:
Hi Andy,
I found on the server a coredump reporting insufficient memory for the
JRE (see attach).
It is weird, fuseki allocates a 32Gb maximum Java heap size, but it uses
only 16Gb:
#
java -Xmx32G -jar fuseki-server.jar --update
--config=/etc/default/fuseki/config.ttl
-Xmx32G will not help. In fact it will slow the system down a bit.
TDB keeps cached files outside the heap.
As well *ulimit -c unlimited* didn't change anything. Do you have any
idea what could restrict more memory to use?
This is not a heap issue. The JVM crashed due to lack of system memory
trying to map a file on a 64 bitmachine,
As the size is 2,047,868,928 I'm not sure it's TDB - TDB uses 8M
increments. Maybe Lucene is using mmap files.
There is a list of possible reasons in the hs_err. The JVM should never
crash.
"ulimit -c unlimited" only affect core dumps.
There may be a system limit on memory mapped areas. I'm not sure which
ulimit flag this is. Set all the size ones to "unlimited" (but the OS
may ignore that).
As regards the fuseki server log, I added the file *log4j.properties *to
/opt/apache-jena-fuseki-2.3.1/run, but after a fuseki restart no logs
were generated (expected is a logfile like
/etc/fuseki/logs/fuseki.log?). Do I have to set up anything more?
The server logs by default. You may be not enabling the right logs -
set them all to INFO.
Logs come out to stdout ("fuseki-server") or to /logs/ ("fuseki"
service) depending on how you run the server.
Andy
Thank you,
Sorin
Andy
