[
https://issues.apache.org/jira/browse/NIFI-8276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-8276.
------------------------------------
Resolution: Cannot Reproduce
NiFi 1.18.0 included a major upgrade to Azure client libraries, which may help
address connection issues in some environments.
> PutAzureEventHub throws TimeoutException
> ----------------------------------------
>
> Key: NIFI-8276
> URL: https://issues.apache.org/jira/browse/NIFI-8276
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.11.4
> Reporter: Sergio Ignacio
> Priority: Critical
> Attachments: Connection_inactive.txt, TimeoutException_stacktrace.txt
>
>
> We use the processor PutAzureEventHub (version 1.11.4) to insert messages.
> When it starts, it works fine. After a while, it returns this error:
> java.util.concurrent.CompletionException:
> com.microsoft.azure.eventhubs.TimeoutException: Entity(***): Send operation
> timed out at 2021-02-26T06:59:45.382-03:00[America/Argentina/Buenos_Aires].,
> errorContext[NS: ***, PATH: ***, REFERENCE_ID: ***, LINK_CREDIT: ***]
>
> Also in the log, we found this message:
> onConnectionLocalClose hostname[***.servicebus.windows.net:5671],
> connectionId[***], errorCondition[amqp:connection:forced],
> errorDescription[The connection was inactive for more than the allowed 60000
> milliseconds and is closed by container 'LinkTracker'. TrackingId:***,
> SystemTracker:gateway5, Timestamp:2021-02-25T13:41:04]
>
> It seems that it does not retry to connect immediately when the connection
> was closed. This error occurs several times a day. Any ideas on how to
> resolve?
> In attachments, I added the errors with more details.
>
> Thanks!!
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
