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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
