On 25/05/11 11:38, Michael Brunnbauer wrote:
re
The problem was caused by an error in my servlet mapping. I used
<servlet-name>SPARQL service processor</servlet-name>
for my SPARQL update serviceRef instead of
<servlet-name>SPARQL/Update service processor</servlet-name>
>
The SPARQL update service was working anyway but throwed the
ConcurrentModificationException instead of waiting for a lock.
Is there any chance this broken setup has caused TDB corruption with
Joseki-3.4.3 ?
Going by some of the stacktraces you've shown, then yes. They are
caused by not locking correctly.
Thanks for letting everyone know the root cause.
Andy
cu,
brunni
