[
https://issues.apache.org/jira/browse/NIFI-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16645905#comment-16645905
]
ASF GitHub Bot commented on NIFI-5645:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/3037
@mcgilman I've also tried different JNA versions to see if the issue has
been solved at the library. The latest 5.0.0 produced following test failure. I
haven't researched on this but it may be caused by some breaking-change:
```
[ERROR] org.apache.nifi.processors.windows.event.log.jna.ErrorLookupTest
Time elapsed: 0.154 s <<< ERROR!
java.lang.UnsatisfiedLinkError: Unable to load library 'kernel32': Native
library (darwin/libkernel32.dylib) not found in resource path
([file:/Users/koji/dev/nifi/nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-processors/target/surefire/surefirebooter3705181589607153497.jar])
```
The latest 4.x version 4.5.2 worked fine.
Although, just updating JNA version didn't addressed the issue, there has
been number of bug-fixes, so I updated the JNA version from 4.2.2 to 4.5.2.
> Auto reconnect ConsumeWindowsEventLog if no log is consumed for configured
> time period
> --------------------------------------------------------------------------------------
>
> Key: NIFI-5645
> URL: https://issues.apache.org/jira/browse/NIFI-5645
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.0.0
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Priority: Major
>
> While ConsumeWindowsEventLog is running, if Windows Event Log service is
> restarted, or ERROR_EVT_QUERY_RESULT_STALE (15011) is returned, the processor
> keeps running, but will not receive further log events.
> Current work-around is restarting the processor manually.
> We could implement auto-reconnect logic like below, so that the processor can
> recover from such situation automatically.
> * Add a new processor property, ''Inactive duration to reconnect", e.g. "3
> mins"
> * At onTrigger, check how long has it passed since the last message was
> received. If it exceeds the configured duration, reset the consumer
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
