You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2014/11/07 12:35:33 UTC

[jira] [Updated] (MESOS-1056) JNI wrapper does not check for exceptions

     [ https://issues.apache.org/jira/browse/MESOS-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam B updated MESOS-1056:
--------------------------
    Labels: newbie  (was: )

> JNI wrapper does not check for exceptions
> -----------------------------------------
>
>                 Key: MESOS-1056
>                 URL: https://issues.apache.org/jira/browse/MESOS-1056
>             Project: Mesos
>          Issue Type: Bug
>          Components: java api
>    Affects Versions: 0.16.0
>            Reporter: Nathan Howell
>            Priority: Minor
>              Labels: newbie
>
> If you run a Java framework built against Protocol Buffers 2.5.0 but compiled Mesos against 2.4.1 it will cause segfault in jni_GetByteArrayElements.
> This is triggered if org.apache.mesos.Protos.FrameworkInfo.toByteArray throws an exception, which is (unfortunately) by-design according to https://code.google.com/p/protobuf/issues/detail?id=493. The JNI wrapper, most notably construct<FrameworkInfo>(...), does not check if an env->ExceptionOccurred after invoking FrameworkInfo.toByteArray and this angers the JVM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)