You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Prasad Alokam (JIRA)" <ji...@apache.org> on 2019/03/28 23:53:00 UTC

[jira] [Commented] (NIFI-5999) Apache NiFi 1.8.0 and Apache NiFi Toolkit 1.8.0 are not working with IBM Java

    [ https://issues.apache.org/jira/browse/NIFI-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16804451#comment-16804451 ] 

Prasad Alokam commented on NIFI-5999:
-------------------------------------

We have faced issue with 1.8.0

TLS Tool kit and Registry failed to start with 
bash-4.4# java -version
_*openjdk version "1.8.0_201"*_
OpenJDK Runtime Environment (IcedTea 3.11.0) (Alpine 8.201.08-r0)
OpenJDK 64-Bit Server VM (build 25.201-b08, mixed mode) Mar 21, 2019 12:03

Works with this version 

bash-4.4# java -version
*openjdk version "1.8.0_191"*
OpenJDK Runtime Environment (IcedTea 3.10.0) (Alpine 8.191.12-r0)
OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)


> Apache NiFi 1.8.0 and Apache NiFi Toolkit 1.8.0 are not working with IBM Java
> -----------------------------------------------------------------------------
>
>                 Key: NIFI-5999
>                 URL: https://issues.apache.org/jira/browse/NIFI-5999
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.8.0
>         Environment: Apache NiFi 1.8.0
> Apache NiFi Toolkit 1.8.0
> RHEL 6.5/Ubuntu 16.04.2 LTS
> IBM JDK 1.8.0_191/IBM JDK 1.8.0_181
>            Reporter: Dnyaneshwar Pawar
>            Priority: Major
>              Labels: JDK
>             Fix For: 1.7.0
>
>         Attachments: IBMJDK_NiFi_Err1.png, IBMJDK_NiFi_Err2.png
>
>
> This issue is related to running Apache NiFi with IBM Java. Until release 1.7.0, Apache NiFi was working fine with the IBM Java, however, release 1.8.0, we observed the Jetty is not returning appropriate keystore provider for SSL setup.
> It's been observed that for IBM  Java, the provider returned is SUN instead of IBMJCE which causes the issue in loading the trust material. 
> Enclosing stack trace snaps taken on running environment. PFA. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)