we experienced very similar behaviour with nearly the same usecase. i reported
one bug which was in our case temporarily solved by turning off context index.
recently i found other very similar issue, which is not reportwd yet as i cant
figure out the cause. look pls into catalina.out whether
Hi,
as long as I understand the error and behaviour it causes (I experienced this
error few times before so I'm familiar), it can end with two scenarios, but
both are considered as blocker/critical bugs:
1. You didn't recieve results which you should recieve (all data indicate the
query is
Thank you Marek,
I'll give it a try, I cleaned the repository without updating the conf a
couple of hours ago and the issue haven't appeared yet, but as you say this
may lead to issues in the future so why not.
Thanks
2013/3/28 Marek Šurek marek_su...@yahoo.co.uk
Hi,
as long as I understand
Hi Stefano,
We are sorry to hear that you experience problems!
We gave a try to reproduce this issue with synthetic data consisting of
1M statements and 100 owl:sameAs links between random entities,
performing thousands of small updates in the background of heavy
long-running queries and
Hello all,
I am new to this list and to OWLIM-SE and was wondering if anyone could offer
advice for loading a large triple store. I am trying to load 670M triples into
a repository using the openrdf-sesame workbench under tomcat6 on a single linux
VM with 64-bit hardware and 64GB of memory.
Hi,
if you want to see progress in loading, there is and option to use standard
curl command instead of openrdf-workbench. It gives you some information what
is already loaded.
To load files into owlim(from .trig file), run this command in your linux shell
:
curl -X POST -H
