You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/11/10 18:05:11 UTC
[jira] [Commented] (IGNITE-1884) .Net: JNI local ref can't be
accessed from another thread
[ https://issues.apache.org/jira/browse/IGNITE-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998908#comment-14998908 ]
ASF GitHub Bot commented on IGNITE-1884:
----------------------------------------
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/215
IGNITE-1884 .Net: JNI local ref can't be accessed from another thread
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-1884
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/215.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #215
----
commit 8e4f189eac993ed95b493fa4ce9724346f13e775
Author: Pavel Tupitsyn <pt...@gridgain.com>
Date: 2015-11-10T17:04:02Z
IGNITE-1884 .Net: JNI local ref can't be accessed from another thread
----
> .Net: JNI local ref can't be accessed from another thread
> ---------------------------------------------------------
>
> Key: IGNITE-1884
> URL: https://issues.apache.org/jira/browse/IGNITE-1884
> Project: Ignite
> Issue Type: Bug
> Components: interop
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Blocker
> Fix For: 1.5
>
>
> Documentation: https://docs.oracle.com/javase/7/docs/technotes/guides/jni/spec/design.html
> {code}
> Local references are only valid in the thread in which they are created. The native code must not pass local references from one thread to another.
> {code}
> We have two places where we DO pass local JNI reference to another thread:
> * CacheParallelLoadStoreAdapter
> * CacheTestStore.LoadCache
> And, potentially (due to user code):
> * UnmanagedCallbacks.DataStreamerStreamReceiverInvoke
> For some reason it has worked for us before.
> But renamings in IGNITE-1881 have caused test execution order to change, and these store tests cause process crash.
> To reproduce, BinaryBuilderSelfTest (former PortableApiSelfTest) has to be executed before store tests. All other tests can be excluded. 100% repro rate: "FATAL ERROR in native method: Bad global or local ref passed to JNI".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)