[
https://issues.apache.org/jira/browse/MINIFI-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023126#comment-16023126
]
ASF subversion and git services commented on MINIFI-207:
--------------------------------------------------------
Commit cbc12903ffb81bf16808f61a42e772d7c4676c06 in nifi-minifi-cpp's branch
refs/heads/master from Marc Parisi
[ https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;h=cbc1290 ]
MINIFI-207: Use recursive mutex that avoid thread safety concerns
This closes #102.
Signed-off-by: Aldrin Piri <ald...@apache.org>
> findProcessor in ProcessGroup not thread safe
> ---------------------------------------------
>
> Key: MINIFI-207
> URL: https://issues.apache.org/jira/browse/MINIFI-207
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++
> Affects Versions: cpp-0.1.0
> Reporter: marco polo
> Assignee: marco polo
> Fix For: cpp-0.3.0
>
>
> These functions do not use the mutex. the sets can be change the underlying
> tree upon insertion. Since flow cannot be guaranteed we should use the mutex
> here ( i.e. it can be called in any order since it is public ).
> add and remove connection call this function and lock the mutex themselves.
> An alternative might be to use a recursive mutex or dramatically reduce the
> critical section in add/remove connection. This appears more desirable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
