You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Bryan Rosander (JIRA)" <ji...@apache.org> on 2017/04/26 15:00:09 UTC

[jira] [Updated] (NIFI-3744) Possible null pointer in PutHiveStreaming.cleanup() if PutHiveStreaming.setup() fails

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

Bryan Rosander updated NIFI-3744:
---------------------------------
    Description: 
callTimeoutPool is one of the last things instantiated in PutHiveStreaming.setup().  The cleanup code doesn't check for null before attempting to shutdown the callTimeoutPool, resulting an a NPE if callTimeoutPool is not initialized.

A NPE is also possible while iterating over allWriters.

  was:callTimeoutPool is one of the last things instantiated in PutHiveStreaming.setup().  The cleanup code doesn't check for null before attempting to shutdown the callTimeoutPool, resulting an a NPE if callTimeoutPool is not initialized.


> Possible null pointer in PutHiveStreaming.cleanup() if PutHiveStreaming.setup() fails
> -------------------------------------------------------------------------------------
>
>                 Key: NIFI-3744
>                 URL: https://issues.apache.org/jira/browse/NIFI-3744
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Bryan Rosander
>            Assignee: Bryan Rosander
>            Priority: Minor
>
> callTimeoutPool is one of the last things instantiated in PutHiveStreaming.setup().  The cleanup code doesn't check for null before attempting to shutdown the callTimeoutPool, resulting an a NPE if callTimeoutPool is not initialized.
> A NPE is also possible while iterating over allWriters.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)