On 27/01/13 11:21, Michael Brunnbauer wrote:
hi all
the following exception occured during a SPARQL update on jena-fuseki-0.2.5
with jdk-7u11-linux-x64. The system has been doing SPARQL updates without
problem with jena-fuseki-0.2.5 since October and with jdk-7u11-linux-x64 since
Jan 15. I have updated the 32bit glibc yesterday but it should not be involved
as this is a 64bit version of Java. I guess only Oracle can do something here ?
Yes - sorry - nothing Fuseki can do. It is very frustrating when java
goes bad.
Memory mapped IO is returning errors.
You could go back an earlier JDK7 or use a JDK6.
But it might also be that your hardware is decaying or (unlikely but
possible) it's an OS bug that 7u11 happens to provoke.
Andy
00:43:16 INFO Fuseki :: [10654] POST
http://ts.foaf-search.net:3030/crawl/update
00:43:53 WARN SPARQL_Update$HttpActionUpdate :: Transaction still active in
endWriter - no commit or abort seen (forced abort)
00:43:53 WARN Fuseki :: [10654] RC = 500 : a fault occurred in a
recent unsafe memory access operation in compiled Java code
java.lang.InternalError: a fault occurred in a recent unsafe memory access
operation in compiled Java code
at
com.hp.hpl.jena.tdb.base.file.BlockAccessBase.check(BlockAccessBase.java:118)
at
com.hp.hpl.jena.tdb.base.file.BlockAccessMapped.read(BlockAccessMapped.java:93)
