[
https://issues.apache.org/jira/browse/NIFI-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370369#comment-15370369
]
ASF GitHub Bot commented on NIFI-1899:
--------------------------------------
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/483
@ijokarumawak - thanks for looking at it.
So just for me to confirm:
PutEmail connects and tries to use SSL. This fails. It holds the socket
PutEmail connects again with plain text. This connection fails.
?
If so, isn't that the expected behavior of a single connection limit? The
client shouldn't hold for a server if it intends to do another connection?
On another note it seems the synchronized section introduced a serious bug
around concurrency. Seems like I created a deadlock. :-)
Looking at it at the moment.
> Create ListenSMTP & ExtractEmailAttachment processors
> -----------------------------------------------------
>
> Key: NIFI-1899
> URL: https://issues.apache.org/jira/browse/NIFI-1899
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Andre
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
