GitHub user joewitt opened a pull request:
https://github.com/apache/nifi/pull/856
NIFI-2519 aligned processor to leverage the subethasmtp threading model
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/joewitt/incubator-nifi NIFI-2519
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/856.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #856
----
commit c4d750993b46e72506d7e19a5c5591ad1dc3f3b9
Author: Oleg Zhurakousky <o...@suitcase.io>
Date: 2016-08-10T14:19:17Z
NIFI-2519 Fixed and refactored ListenSMTP processor
- Removed message queueing which could result in data loss
- Fixed life-cycle issues that coudl put processor in an unstable state
- Fixed PropertyDescriptor translation for Time units and Byte sizes
- Fixed broken tests
- Added additional tests
NIFI-2519 added default for SMTP_MAXIMUM_CONNECTIONS
NIFI-2519 addressed PR comments, polishing
- fixed intermittent deadlock on processor stop and added test for it
- the attributes that can not be extracted from the message but available
via MessageContext are written into the outgoing FlowFile
- other minor fixes
NIFI-2519 addressed lates PR comments
NIFI-2519 added better messaging when server closes the connection
NIFI-2519 some polishing and additional tests to validate deadlocks
NIFI-2519 address latest PR comments
fixed deadlock condition for when the consumer is stopped while server is
distributing messages
fixed MAX message size issue ensuring it is validated
set max connections to SMTPServer
polished pom
added L&N
NIFI-2519 PR comments
- fixed LICENSE
- Added usage of LimitingInputStream
- simplified SmtpConsumer by removing hasMessage operation
commit b7e65001471e83103ebfdfc85b4bdf0fa90820fa
Author: joewitt <joew...@apache.org>
Date: 2016-08-14T05:10:47Z
NIFI-2519 aligned threading model with subethastmp
----
---
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.
---
