[
https://issues.apache.org/jira/browse/IMPALA-8250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778865#comment-16778865
]
ASF subversion and git services commented on IMPALA-8250:
---------------------------------------------------------
Commit b74d63222875482c7efe38b8b2e5ff091a94fb6a in impala's branch
refs/heads/master from Philip Zeyliger
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=b74d632 ]
IMPALA-8250: Fix a handful of JNI usage errors.
Running Impala with LIB_HDFS_OPTS=-Xcheck:jni revealed a case of "FATAL
ERROR in native method: Bad global or local ref passed to JNI" as well
as 'WARNING in native method: JNI FindClass received a bad class
descriptor "Lorg/apache/impala/common/Pair;"' This commit fixes these.
There are additional JNI warnings that I'm working through
as well as a fundamental question about how to avoid these
systematically.
Kudos to Lars Volker and Sahil Takiar who co-found these issues.
Change-Id: Id3b8bccee20cc882cffa4439e550e1f48347d3a6
Reviewed-on: http://gerrit.cloudera.org:8080/12582
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Impala crashes with -Xcheck:jni
> -------------------------------
>
> Key: IMPALA-8250
> URL: https://issues.apache.org/jira/browse/IMPALA-8250
> Project: IMPALA
> Issue Type: Task
> Reporter: Philip Zeyliger
> Priority: Major
>
> The JVM has a checker for JNI usage, and Impala (and libhdfs) have some
> violations. This ticket captures figuring that out. At least one of the
> issues can crash Impala.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
