Yes I can try to save the properties again and see what happens.
I've thought that the JVM hasn't enough memory to manage everything and
for this reason arise that exception (Maybe this is a really stupid
thing, but it's the first one that seems reasonable to me). I really
don't know why this happens and for this reason I've asked here.
Is there some kind of situation that should you suggest to avoid when I
do this kind of operations? Maybe following your tips I can avoid the
problem that I have.
Alessandro Suglia
On 07/04/14 11:45, Andy Seaborne wrote:
On 03/07/14 21:48, Alessandro Suglia wrote:
Good evening,
I'm trying to run a simple program whose aim is to save in a TDB index
some properties that I've downloaded from the DBpedia endpoint. After
some hours of operations I receive a SIGSEGV from the JVM on my
archlinux x64 workstation. Have you ever got something similar? Maybe
could it depends from the heap's maximum size of the JVM?
This is the log of the execution, I hope that could help:
http://codepad.org/ZUzYcXBR
Thank you in advance,
Alessandro Suglia
Alessandro,
This hasn't happened to me. Google/stackoveflow didn't immediate show
a similar situation though there is a long record of a few of
SIGSEGV/JVM_handle_linux_signal from time to time.
(I got a 500 out of Google just searching for that!)
Is it repeatable?
If is, maybe a different JVM.
If the JVM itself is crashing, then it's not Jena (no native code -
through obviously we might trigger some).
Andy
