[
https://issues.apache.org/jira/browse/NIFI-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062952#comment-16062952
]
ASF GitHub Bot commented on NIFI-4099:
--------------------------------------
GitHub user lfrancke opened a pull request:
https://github.com/apache/nifi/pull/1941
NIFI-4099
- Code cleanup (consistent formatting, naming etc.)
- Update of SNMP4J from 1.10.1 to 2.5.6
- Fixes restartability issue because snmpTarget was not recreated
- Updates SNMPUtils to not use Reflection (initialized from a static list
of method names) to create a FlowFile
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lfrancke/nifi NIFI-4099
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1941.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 #1941
----
commit 9a692ba9491623ecf191244b7986a022140a022d
Author: Lars Francke <[email protected]>
Date: 2017-06-26T10:01:19Z
Changes for NIFI-4099
- Code cleanup (consistent formatting, naming etc.)
- Update of SNMP4J from 1.10.1 to 2.5.6
- Fixes restartability issue because snmpTarget was not recreated
- Updates SNMPUtils to not use Reflection (initialized from a static list
of method names) to create a FlowFile
----
> SNMP processors cannot be restarted with SNMPv3 & security
> ----------------------------------------------------------
>
> Key: NIFI-4099
> URL: https://issues.apache.org/jira/browse/NIFI-4099
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.4.0
> Reporter: Lars Francke
> Assignee: Lars Francke
> Labels: snmp
>
> The SNMP processors currently fail when stopped & started again because
> snmpTarget is not set to null and only if it is are the user credentials
> added to the current USM/Engine.
> So what happens is that SNMP4j complains that there is no username.
> I'll provide a patch that fixes this.
> In addition I'd like to update SNMP4J from the version that's being used 1.x
> (from 2009) to 2.5.6 from 2017. And I'd love to also do a code cleanup run.
> I'd prefer to have it all in one patch (it still won't be large) but if
> really needed I can separate it out into three patches.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
