You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Tsuyoshi Ito (JIRA)" <ji...@apache.org> on 2010/06/22 09:39:54 UTC
[jira] Created: (CLEREZZA-245) read/write locks are not set in
different projects
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.
[jira] Commented: (CLEREZZA-245) read/write locks are not set in
different projects
Posted by "Tommaso Teofili (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881185#action_12881185 ]
Tommaso Teofili commented on CLEREZZA-245:
------------------------------------------
Hi Tsuyoshi, could you be more precise about the nature of the issue?
> 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.
[jira] Closed: (CLEREZZA-245) read/write locks are not set in
different projects
Posted by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reto Bachmann-Gmür closed CLEREZZA-245.
---------------------------------------
Resolution: Fixed
this refers to a type of bug rather than a concrete occurrence. it has been fixed in several places now. Please post issue whenever you have a respective exception (including stack-trace)
> 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.
[jira] Commented: (CLEREZZA-245) read/write locks are not set in
different projects
Posted by "Tsuyoshi Ito (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CLEREZZA-245) read/write locks are not set in
different projects
Posted by "Manuel Innerhofer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883158#action_12883158 ]
Manuel Innerhofer commented on CLEREZZA-245:
--------------------------------------------
set locks in usermanager and usermanager.webinterface
> 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.