Re: PutS3Object error

You should not need to modify your hosts file. Can you try using the AWS CLI tools to list the bucket from the same machine running NiFi? Something like: aws s3 ls s3://nifibucket/ If that is working, you should have all the required network connectivity. Also, would you please describe any

Re: PutS3Object error

John, When you configure the PutS3Object processor, you should configure the Bucket Name as just 'nifibucket' (without quotes), and set the Region to 'eu-west-1'. You do not need the long-form ' nifibucket.s3-eu-west-1.amazonaws.com', I think that might be what is confusing it. Thanks, James

Re: Does NiFi ConsumeJMS Processor supports OpenJMS?

Nirmal Did some digging and the NPE is due to the fact that we are invoking a default constructor for whatever connection factory class is provided (i.e., ‘org.exolab.jms.client.JmsConnectionFactory’). And that works for most major JMS providers, however for OpenJMS after looking at the code

Re: Processors on the fly for many sensor devices

Good morning Davy, I have all (barring tests that fail) code in place to fulfill NIFI-2615 [1]. I plan on wrapping up the testing of it today and submitting a P/R. One thing to call out is that at present it is it's own module. However, I plan on adding it to the NiFi Standard Processor bundle

Re: nifi is running out of memory

Thanks Joe for checking. Yes, I got past it and I was successfully able to demo it to the team :) Now, the next challenge is to drive the performance out of nifi for the high throughput. On Mon, Oct 31, 2016 at 7:08 PM, Joe Witt wrote: > Krish, > > Did you ever get past