[
https://issues.apache.org/jira/browse/CLEREZZA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881679#action_12881679
]
Tsuyoshi Ito commented on CLEREZZA-245:
---------------------------------------
when iterating over a graph or writing into a graph a read resp. writeLock has
to be set. Condition: other threads are also using the same graph
Lock lock = graph.getLock().readLock();
lock.lock();
try {
Iterator<Triple> triples = graph.filter(null, null, null);
if (triples.hasNext()) {
triple.next();
}
} finally {
lock.unlock();
}
or
writeLock when storing triples into a graph, which is used by others.
check projects if all read and write locks are set where appropriate.
e.g. hierarchyService
> read/write locks are not set in different projects
> --------------------------------------------------
>
> Key: CLEREZZA-245
> URL: https://issues.apache.org/jira/browse/CLEREZZA-245
> Project: Clerezza
> Issue Type: Bug
> Reporter: Tsuyoshi Ito
> Priority: Critical
>
> please check all services and methods if read/write locks are set correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
