On 11/05/11 15:59, Michael Brunnbauer wrote:
re
This seems to be new with 3.4.4:
16:52:43 INFO SPARQL :: Throwable: Reader = 1, Writer = 1
java.util.ConcurrentModificationException: Reader = 1, Writer = 1
at
com.hp.hpl.jena.tdb.sys.ConcurrencyPolicyMRSW.policyError(ConcurrencyPolicyMRSW.java:132)
Got it from a SELECT submitted while an UPDATE was running.
I think earlier versions would delay the SELECT until the UPDATE was finished.
Is there a way to restore this behavior ?
This is not good. (tm)
It is likely the chnage is merely that the system notices the problem,
rather than was doing anything different. TDB has had some trackign
added to help warn of potential problems.
However, the locking works in other situations - could the same TDB
daatbase be shared between services in some way? What's the joseki
config file?
Andy
Regards,
Michael Brunnbauer
On Fri, May 06, 2011 at 10:24:28AM +0100, Andy Seaborne wrote:
This is release of Joseki to bring it into line with the current
versions of ARQ and of TDB and SDB.
Andy
Downloads:
http://sourceforge.net/projects/joseki/files/Joseki-SPARQL/Joseki-3.4.4/joseki-3.4.4.zip/download
and in the maven repository:
Maven details:
http://www.openjena.org/repo/org/joseki/joseki/3.4.4/
<dependency>
<groupId>org.joseki</groupId>
<artifactId>joseki</artifactId>
<version>3.4.4</version>
</dependency>
<repository>
<id>repo-jena</id>
<name>Jena Maven - Repository</name>
<layout>default</layout>
<url>http://openjena.org/repo</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
