[
https://issues.apache.org/jira/browse/NIFI-9758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501356#comment-17501356
]
David Handermann commented on NIFI-9758:
----------------------------------------
Thanks for raising this issue [~Fonseca]! I agree with [~asdaraujo] that
introducing support for dynamic properties that start with {{mail}} would
provide the most flexible approach.
> PutEmail processor dying when SMTP server does not respond
> ----------------------------------------------------------
>
> Key: NIFI-9758
> URL: https://issues.apache.org/jira/browse/NIFI-9758
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.14.0
> Environment: Windows Server 2016
> JDK 11
> Reporter: Javier Fonseca
> Priority: Major
> Labels: easyfix, features
>
> *Bug*
> PutEmail processor dyes after _"the socked connection is established, if the
> server response is lost for some reason (or if the server doesn't respond at
> all) the processor thread gets stuck forever._
> _Apparently this is kind of by design, since the default value of the
> mail.smtp.timeout property is infinite, as it can be see
> [here|https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html]._
> _I had a look at the PutEmail processor source code and unfortunately I don't
> think there is a way currently to set this in the processor configuration."_
> Processor must be terminated/restart in these cases.
>
> *Potential Solution*
> Add a configurable property TimeOut to set the __ value of the
> _mail.smtp.timeout_ property, allowing the processor to fail after certain
> amount of time.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
