Re: GetMongo GC Overflow

2016-03-01 Thread Bryan Bende
Hello,

I'm not that familiar with MongoDB, but from looking at the existing
GetMongo processor, it seems to create a FlowFile per Document and only
calls session.commit() once at the very end, which could possibly be a
problem when producing a very significant amount of flow files.

When you mentioned writing your own processor, did you do this as your own
project? or were you modifying the one in apache nifi and rebuilding the
whole project?

There should be some information in nifi_home/logs/nifi-app.log that
indicates why it didn't start up. If you could provide the error messages
and stack traces it would help us figure out what went wrong.

Thanks,

Bryan


On Tue, Mar 1, 2016 at 9:08 AM, ajansing  wrote:

> Running Mac OS X 10.10.5
>  Apache Maven 3.3.9
>  java version "1.8.0_72"
>  Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
>
> I've been trying to figure out how to use the GetMongo processor to output
> to a PutHDFS processor.
>
> Some things I think I've figured out:
>
> *Limit* acts exactly as .limit() for Mongo, where all it does it give you
> the first *n* elements in a collections.
> *Batch* isn't a command in Mongo (that I know of) and I can't see how this
> entry does anything for the processor.
>
> I'm working with a collection in the millions and I can't just simply leave
> the limit blank because the JVM runs out of memory. I tried to write my own
> processor and got it to compile under the *mvn clean install*, but when I
> copy the .nar file from the '...nar/target' directory to the
> 'nifi-0.6.0/lib' folder and then try to 'sh nifi.sh run' or 'start', to
> nifi
> refuses to finish booting up and terminates itself.
>
> Taking  GetMongo.java
> <
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/java/org/apache/nifi/processors/mongodb/GetMongo.java
> >
> and it's respective other files. I modified them and changed the following
> method:
>
>
> @Override
> public void onTrigger(final ProcessContext context, final
> ProcessSession
> session) throws ProcessException {
> final ProcessorLog logger = getLogger();
> final MongoCollection collection =
> getCollection(context);
> int count = (int)collection.count();
> int next = context.getProperty(BATCH_SIZE).asInteger();
> int current = next;
> while(count >= current){
> try {
> final FindIterable it =
>
> collection.find().skip(current).limit(context.getProperty(LIMIT).asInteger());
>
> final MongoCursor cursor = it.iterator();
> try {
> FlowFile flowFile = null;
> while (cursor.hasNext()) {
> flowFile = session.create();
> flowFile = session.write(flowFile, new
> OutputStreamCallback() {
> @Override
> public void process(OutputStream out) throws
> IOException {
> IOUtils.write(cursor.next().toJson(), out);
> }
> });
>
> session.getProvenanceReporter().receive(flowFile,
> context.getProperty(URI).getValue());
> session.transfer(flowFile, REL_SUCCESS);
> }
>
> session.commit();
>
> } finally {
> cursor.close();
> }
> } catch (final RuntimeException e) {
> context.yield();
> session.rollback();
> }
> current = current + next;
> }
> }
>
>
> I also modified the test and abstracts so Maven would compile.
>
> Any thoughts?
>
> I'm trying to make a processor that can traverse over an entire collection
> in the millions; and later /any/ size.
>
> If anyone has already made one and can share, that'd be great too! Thanks!
>
>
>
> --
> View this message in context:
> http://apache-nifi-developer-list.39713.n7.nabble.com/GetMongo-GC-Overflow-tp7729.html
> Sent from the Apache NiFi Developer List mailing list archive at
> Nabble.com.
>


[GitHub] nifi pull request: NIFI-1420 Adding Splunk bundle

2016-03-01 Thread JPercivall
Github user JPercivall commented on the pull request:

https://github.com/apache/nifi/pull/233#issuecomment-190970047
  
Whenever an SSL context is being created (done 4 times in multiple 
different classes) "SSLContextService.ClientAuth.REQUIRED" is used. Should we 
offer configuration options for this? For PutSplunk and GetSplunk I can 
understand it because we are requiring the server to provide authorization but 
maybe someone using ListenSplunkForwader doesn't need it to verify who's 
sending the data.


---
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.
---


[GitHub] nifi pull request: NIFI-1420 Adding Splunk bundle

2016-03-01 Thread JPercivall
Github user JPercivall commented on the pull request:

https://github.com/apache/nifi/pull/233#issuecomment-190934511
  
I observed a couple of interesting interactions when testing the PutSplunk 
processor. I'm not sure whether it is a problem with the processor, the Splunk 
Java SDK, Splunk Enterprise or my Splunk configurations:
* I set up the PutSplunk processor to communicate via UDP and created a UDP 
data input using the UI for Splunk Enterprise. The PutSplunk is transmitting 
messages at ~1 per second. While it's transmitting no new events are created 
yet in Splunk Enterprise (verified by viewing a real time view of the past 30 
seconds). I stop the PutSplunk processor and then run a search in Splunk UI to 
see if any events came in on that port. There is one event that is registered 
at when I started the processor and contains effectively all (didn't count the 
seconds I was sending) the data that was generated. I'm not sure why all the 
UDP messages are grouped together. When I set PutSplunk to send messages every 
20 seconds the UDP messages are treated as their own event.
* I set up PutSplunk to communicate via TCP using SSL. I looked for options 
to create a Data Input in Splunk Enterprise using TCP and SSL but couldn't find 
anything definitive (and all my searches turned up results for the Forwarder). 
I enabled SSL in Splunk Web by going to the general settings and notice that 
SSL properties are in the inputs.conf and server.conf files. I attempt to send 
data using PutSplunk using SSL to the TCP data input. The event is received and 
I see it in the Splunk UI in real time. The only problem being that it's still 
encoded (see image). Typically when I get errors with SSL there is some obscure 
error relating to truncation attacks or Cipher Suites but I didn't seem to get 
any errors.
![screen shot 2016-03-01 at 5 21 54 
pm](https://cloud.githubusercontent.com/assets/11302527/13444066/2357d1e2-dfd2-11e5-8150-9684b7299a6d.png)




---
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.
---


Controller Settings

2016-03-01 Thread Edgardo Vega
Why are Maximum time driven thread count and maximum event driven thread
count and for that matter data flow name not in nifi.properties?

I have always been told that Maximum time driven thread count should be a
multiple of the number of cpu/cores on machine. It should be easy for a
automation tool like puppet / ansible / etc to set these values. I am okay
with exposing it via the ui, but not easily being able to do this via
automation has definitely causes some problems.

Just trying to start the conversation about making it easier to automate
the deployment of nifi.

Cheers,

Edgardo


[GitHub] nifi pull request: NIFI-1180: Modify PutS3Object to enable encrypt...

2016-03-01 Thread alopresto
Github user alopresto commented on the pull request:

https://github.com/apache/nifi/pull/246#issuecomment-190851300
  
I do not have AWS S3 credentials to run the integration tests myself but 
the code looks good to me. +1


---
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.
---


Re: OnStopped annotation

2016-03-01 Thread Mark Payne
Pierre,

This feels to me like it could potentially be a classpath issue. The 
nifi-api.jar file is on the
root class path (exists in $NIFI_HOME/lib). If there is a different class 
definition in your processor,
then it will not find the annotation.

If you are deploying your processor as a NAR, though, the maven nar plugin 
should prevent you
from bundling the nifi-api.jar into the nar. It may be worth while though to 
poke around and make sure
that you don't have two copies of the OnStopped annotation class defined in the 
classpath, though.

Thanks
-Mark



> On Mar 1, 2016, at 12:15 PM, Pierre Villard  
> wrote:
> 
> Nice! I used your nifi-ide-integration project to launch Nifi from my IDE
> and I reproduced the issue just by starting/stopping the processor (with a
> breakpoint in ReflectionUtils). I'll try to find some time to reproduce it
> in a unit test if this can help to find the issue.
> 
> Pierre
> 
> 2016-03-01 13:56 GMT+01:00 Oleg Zhurakousky :
> 
>> Pierre
>> 
>> You can simplify your interactive debugging and do it right from IDE
>> https://github.com/olegz/nifi-ide-integration/
>> Just make sure that versioning in Gradle reflects current version.
>> I’ll update as well when I get a chance.
>> 
>> Oleg
>> 
>> On Mar 1, 2016, at 4:47 AM, Pierre Villard > > wrote:
>> 
>> No it is not in a unit test, I remotely attached my Eclipse in debug mode
>> to my deployed Nifi instance.
>> I can try to code a unit test and reproduce the issue using the example you
>> gave.
>> 
>> 2016-02-29 18:22 GMT+01:00 Oleg Zhurakousky > >:
>> 
>> I meant could you share the test code (via github)
>> 
>> On Feb 29, 2016, at 12:18 PM, Oleg Zhurakousky <
>> ozhurakou...@hortonworks.com> wrote:
>> 
>> Ok, so you are invoking ‘quietlyInvokeMethodsWithAnnotations’ in your
>> test code?
>> If so could you your test code where you invoke it? I have a hunch, but
>> want to look before I speculate.
>> 
>> Cheers
>> Oleg
>> On Feb 29, 2016, at 11:58 AM, Pierre Villard <
>> pierre.villard...@gmail.com> wrote:
>> 
>> I just wanted to test the processors with local SNMP set-up and I
>> noticed
>> that modification of properties in my processor didn't have any effect.
>> So I switched to debug, added a processor, started it, and stopped it
>> just
>> after. Conclusion: my close() method is never called.
>> I correctly go through quietlyInvokeMethodsWithAnnotations() in
>> ReflectionUtils but since the method is not seen as annotated, the close
>> method is not called.
>> 
>> Thanks,
>> Pierre
>> 
>> 2016-02-28 22:24 GMT+01:00 Oleg Zhurakousky <
>> ozhurakou...@hortonworks.com>:
>> 
>> I am puzzled as I can’t see how can it not work.
>> Are there steps to reproduce it? I am trying to read into your initial
>> email and suspecting you were doing some sort of testing, so want to
>> make
>> sure I am doing the same thing. . . .
>> 
>> Oleg
>> On Feb 28, 2016, at 2:46 PM, Pierre Villard <
>> pierre.villard...@gmail.com>
>> wrote:
>> 
>> No I am not under testing framework, all my unit tests are OK. I
>> wanted
>> to
>> perform some additional tests and deployed Nifi with the new
>> processors.
>> 
>> You can find the method here [1] if you want to have a look.
>> Thanks for your help.
>> 
>> [1]
>> 
>> 
>> 
>> https://github.com/pvillard31/nifi/blob/NIFI-1537/nifi-nar-bundles/nifi-snmp-bundle/nifi-snmp-processors/src/main/java/org/apache/nifi/snmp/processors/AbstractSNMPProcessor.java#L212-L243
>> 
>> 2016-02-28 17:11 GMT+01:00 Oleg Zhurakousky <
>> ozhurakou...@hortonworks.com>:
>> 
>> Also, reading Aldrin’s response and assuming you are using Test
>> mocks I
>> would probably recommend to not use them for tests that require full
>> lifecycle test of the component until we actually improve it.
>> Instead you can code straight agains FlowController essentially
>> executing
>> as a full blown NiFi minus UI. Here is an example:
>> 
>> 
>> 
>> https://github.com/apache/nifi/pull/210/files#diff-7be646c38c5447f7824e444343633829R92
>> 
>> Cheers
>> Oleg
>> 
>> On Feb 28, 2016, at 11:07 AM, Oleg Zhurakousky <
>> ozhurakou...@hortonworks.com>
>> wrote:
>> 
>> Pierre
>> Can you paste the method definition? Just want to look at the
>> signature
>> and see if there is something obvious
>> 
>> Sent from my iPhone
>> 
>> On Feb 28, 2016, at 10:26, Pierre Villard <
>> pierre.villard...@gmail.com
>> > wrote:
>> 
>> Hi,
>> 
>> I am working on SNMP processors [1] and I'm almost ready for a PR...
>> but I
>> have an issue I can't explain. In my processors, I have implemented a
>> method close() with the @OnStopped annotation but it seems the
>> 

Re: OnStopped annotation

2016-03-01 Thread Pierre Villard
Nice! I used your nifi-ide-integration project to launch Nifi from my IDE
and I reproduced the issue just by starting/stopping the processor (with a
breakpoint in ReflectionUtils). I'll try to find some time to reproduce it
in a unit test if this can help to find the issue.

Pierre

2016-03-01 13:56 GMT+01:00 Oleg Zhurakousky :

> Pierre
>
> You can simplify your interactive debugging and do it right from IDE
> https://github.com/olegz/nifi-ide-integration/
> Just make sure that versioning in Gradle reflects current version.
> I’ll update as well when I get a chance.
>
> Oleg
>
> On Mar 1, 2016, at 4:47 AM, Pierre Villard  > wrote:
>
> No it is not in a unit test, I remotely attached my Eclipse in debug mode
> to my deployed Nifi instance.
> I can try to code a unit test and reproduce the issue using the example you
> gave.
>
> 2016-02-29 18:22 GMT+01:00 Oleg Zhurakousky  >:
>
> I meant could you share the test code (via github)
>
> On Feb 29, 2016, at 12:18 PM, Oleg Zhurakousky <
> ozhurakou...@hortonworks.com> wrote:
>
> Ok, so you are invoking ‘quietlyInvokeMethodsWithAnnotations’ in your
> test code?
> If so could you your test code where you invoke it? I have a hunch, but
> want to look before I speculate.
>
> Cheers
> Oleg
> On Feb 29, 2016, at 11:58 AM, Pierre Villard <
> pierre.villard...@gmail.com> wrote:
>
> I just wanted to test the processors with local SNMP set-up and I
> noticed
> that modification of properties in my processor didn't have any effect.
> So I switched to debug, added a processor, started it, and stopped it
> just
> after. Conclusion: my close() method is never called.
> I correctly go through quietlyInvokeMethodsWithAnnotations() in
> ReflectionUtils but since the method is not seen as annotated, the close
> method is not called.
>
> Thanks,
> Pierre
>
> 2016-02-28 22:24 GMT+01:00 Oleg Zhurakousky <
> ozhurakou...@hortonworks.com>:
>
> I am puzzled as I can’t see how can it not work.
> Are there steps to reproduce it? I am trying to read into your initial
> email and suspecting you were doing some sort of testing, so want to
> make
> sure I am doing the same thing. . . .
>
> Oleg
> On Feb 28, 2016, at 2:46 PM, Pierre Villard <
> pierre.villard...@gmail.com>
> wrote:
>
> No I am not under testing framework, all my unit tests are OK. I
> wanted
> to
> perform some additional tests and deployed Nifi with the new
> processors.
>
> You can find the method here [1] if you want to have a look.
> Thanks for your help.
>
> [1]
>
>
>
> https://github.com/pvillard31/nifi/blob/NIFI-1537/nifi-nar-bundles/nifi-snmp-bundle/nifi-snmp-processors/src/main/java/org/apache/nifi/snmp/processors/AbstractSNMPProcessor.java#L212-L243
>
> 2016-02-28 17:11 GMT+01:00 Oleg Zhurakousky <
> ozhurakou...@hortonworks.com>:
>
> Also, reading Aldrin’s response and assuming you are using Test
> mocks I
> would probably recommend to not use them for tests that require full
> lifecycle test of the component until we actually improve it.
> Instead you can code straight agains FlowController essentially
> executing
> as a full blown NiFi minus UI. Here is an example:
>
>
>
> https://github.com/apache/nifi/pull/210/files#diff-7be646c38c5447f7824e444343633829R92
>
> Cheers
> Oleg
>
> On Feb 28, 2016, at 11:07 AM, Oleg Zhurakousky <
> ozhurakou...@hortonworks.com>
> wrote:
>
> Pierre
> Can you paste the method definition? Just want to look at the
> signature
> and see if there is something obvious
>
> Sent from my iPhone
>
> On Feb 28, 2016, at 10:26, Pierre Villard <
> pierre.villard...@gmail.com
> > wrote:
>
> Hi,
>
> I am working on SNMP processors [1] and I'm almost ready for a PR...
> but I
> have an issue I can't explain. In my processors, I have implemented a
> method close() with the @OnStopped annotation but it seems the
> annotation
> is not seen. When debugging and stopping my processor, I correctly go
> through quietlyInvokeMethodsWithAnnotations() in ReflectionUtils and
> my
> method close() appears without any annotation. I guess I am missing
> something simple. Any idea?
>
> [1] https://issues.apache.org/jira/browse/NIFI-1537
>
>
>
>
>
>
>
>
>
>


[GitHub] nifi pull request: NIFI-1464, NIFI-78, NIFI-1487 Refactored Proces...

2016-03-01 Thread markap14
Github user markap14 commented on a diff in the pull request:

https://github.com/apache/nifi/pull/210#discussion_r54588819
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core-api/src/main/java/org/apache/nifi/controller/ProcessorNode.java
 ---
@@ -99,4 +108,96 @@ public ProcessorNode(final Processor processor, final 
String id,
  */
 public abstract void verifyCanStart(Set 
ignoredReferences);
 
+/**
+ *
+ */
+@Override
+public ScheduledState getScheduledState() {
+return this.scheduledState.get();
+}
+
+/**
+ * Returns the logical state of this processor. Logical state ignores
+ * transition states such as STOPPING and STARTING rounding it up to 
the
+ * next logical state of STOPPED and RUNNING respectively.
+ *
+ * @return the logical state of this processor [DISABLED, STOPPED, 
RUNNING]
+ */
+public ScheduledState getLogicalScheduledState() {
--- End diff --

Good. I like this approach.


---
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.
---


GetMongo GC Overflow

2016-03-01 Thread ajansing
Running Mac OS X 10.10.5
 Apache Maven 3.3.9
 java version "1.8.0_72"
 Java(TM) SE Runtime Environment (build 1.8.0_72-b15)

I've been trying to figure out how to use the GetMongo processor to output
to a PutHDFS processor.

Some things I think I've figured out:

*Limit* acts exactly as .limit() for Mongo, where all it does it give you
the first *n* elements in a collections.
*Batch* isn't a command in Mongo (that I know of) and I can't see how this
entry does anything for the processor.

I'm working with a collection in the millions and I can't just simply leave
the limit blank because the JVM runs out of memory. I tried to write my own
processor and got it to compile under the *mvn clean install*, but when I
copy the .nar file from the '...nar/target' directory to the
'nifi-0.6.0/lib' folder and then try to 'sh nifi.sh run' or 'start', to nifi
refuses to finish booting up and terminates itself.

Taking  GetMongo.java

  
and it's respective other files. I modified them and changed the following
method:


@Override
public void onTrigger(final ProcessContext context, final ProcessSession
session) throws ProcessException {
final ProcessorLog logger = getLogger();
final MongoCollection collection = getCollection(context);
int count = (int)collection.count();
int next = context.getProperty(BATCH_SIZE).asInteger();
int current = next;
while(count >= current){
try {
final FindIterable it =
collection.find().skip(current).limit(context.getProperty(LIMIT).asInteger());

final MongoCursor cursor = it.iterator();
try {
FlowFile flowFile = null;
while (cursor.hasNext()) {
flowFile = session.create();
flowFile = session.write(flowFile, new
OutputStreamCallback() {
@Override
public void process(OutputStream out) throws
IOException {
IOUtils.write(cursor.next().toJson(), out);
}
});

session.getProvenanceReporter().receive(flowFile,
context.getProperty(URI).getValue());
session.transfer(flowFile, REL_SUCCESS);
}

session.commit();

} finally {
cursor.close();
}
} catch (final RuntimeException e) {
context.yield();
session.rollback();
}
current = current + next;
}
}


I also modified the test and abstracts so Maven would compile.

Any thoughts?

I'm trying to make a processor that can traverse over an entire collection
in the millions; and later /any/ size.

If anyone has already made one and can share, that'd be great too! Thanks!



--
View this message in context: 
http://apache-nifi-developer-list.39713.n7.nabble.com/GetMongo-GC-Overflow-tp7729.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.


Re: OnStopped annotation

2016-03-01 Thread Pierre Villard
No it is not in a unit test, I remotely attached my Eclipse in debug mode
to my deployed Nifi instance.
I can try to code a unit test and reproduce the issue using the example you
gave.

2016-02-29 18:22 GMT+01:00 Oleg Zhurakousky :

> I meant could you share the test code (via github)
>
> > On Feb 29, 2016, at 12:18 PM, Oleg Zhurakousky <
> ozhurakou...@hortonworks.com> wrote:
> >
> > Ok, so you are invoking ‘quietlyInvokeMethodsWithAnnotations’ in your
> test code?
> > If so could you your test code where you invoke it? I have a hunch, but
> want to look before I speculate.
> >
> > Cheers
> > Oleg
> >> On Feb 29, 2016, at 11:58 AM, Pierre Villard <
> pierre.villard...@gmail.com> wrote:
> >>
> >> I just wanted to test the processors with local SNMP set-up and I
> noticed
> >> that modification of properties in my processor didn't have any effect.
> >> So I switched to debug, added a processor, started it, and stopped it
> just
> >> after. Conclusion: my close() method is never called.
> >> I correctly go through quietlyInvokeMethodsWithAnnotations() in
> >> ReflectionUtils but since the method is not seen as annotated, the close
> >> method is not called.
> >>
> >> Thanks,
> >> Pierre
> >>
> >> 2016-02-28 22:24 GMT+01:00 Oleg Zhurakousky <
> ozhurakou...@hortonworks.com>:
> >>
> >>> I am puzzled as I can’t see how can it not work.
> >>> Are there steps to reproduce it? I am trying to read into your initial
> >>> email and suspecting you were doing some sort of testing, so want to
> make
> >>> sure I am doing the same thing. . . .
> >>>
> >>> Oleg
>  On Feb 28, 2016, at 2:46 PM, Pierre Villard <
> pierre.villard...@gmail.com>
> >>> wrote:
> 
>  No I am not under testing framework, all my unit tests are OK. I
> wanted
> >>> to
>  perform some additional tests and deployed Nifi with the new
> processors.
> 
>  You can find the method here [1] if you want to have a look.
>  Thanks for your help.
> 
>  [1]
> 
> >>>
> https://github.com/pvillard31/nifi/blob/NIFI-1537/nifi-nar-bundles/nifi-snmp-bundle/nifi-snmp-processors/src/main/java/org/apache/nifi/snmp/processors/AbstractSNMPProcessor.java#L212-L243
> 
>  2016-02-28 17:11 GMT+01:00 Oleg Zhurakousky <
> >>> ozhurakou...@hortonworks.com>:
> 
> > Also, reading Aldrin’s response and assuming you are using Test
> mocks I
> > would probably recommend to not use them for tests that require full
> > lifecycle test of the component until we actually improve it.
> > Instead you can code straight agains FlowController essentially
> >>> executing
> > as a full blown NiFi minus UI. Here is an example:
> >
> >>>
> https://github.com/apache/nifi/pull/210/files#diff-7be646c38c5447f7824e444343633829R92
> >
> > Cheers
> > Oleg
> >
> > On Feb 28, 2016, at 11:07 AM, Oleg Zhurakousky <
> > ozhurakou...@hortonworks.com>
> >>> wrote:
> >
> > Pierre
> > Can you paste the method definition? Just want to look at the
> signature
> > and see if there is something obvious
> >
> > Sent from my iPhone
> >
> > On Feb 28, 2016, at 10:26, Pierre Villard <
> pierre.villard...@gmail.com
> > > wrote:
> >
> > Hi,
> >
> > I am working on SNMP processors [1] and I'm almost ready for a PR...
> >>> but I
> > have an issue I can't explain. In my processors, I have implemented a
> > method close() with the @OnStopped annotation but it seems the
> >>> annotation
> > is not seen. When debugging and stopping my processor, I correctly go
> > through quietlyInvokeMethodsWithAnnotations() in ReflectionUtils and
> my
> > method close() appears without any annotation. I guess I am missing
> > something simple. Any idea?
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-1537
> >
> >
> >
> >>>
> >>>
> >
>
>