Re: ActiveMQ trust store issues

Thanks Michael! I'll try it out. On Wed, Jan 11, 2017 at 5:19 PM, Michael Moser wrote: > Joe, > > Have you seen https://issues.apache.org/jira/browse/NIFI-3230? You might > try the latest code on the master branch to see if it fixes your problem. > The JIRA ticket also offers a workaround by u

Re: ActiveMQ trust store issues

Joe, Have you seen https://issues.apache.org/jira/browse/NIFI-3230? You might try the latest code on the master branch to see if it fixes your problem. The JIRA ticket also offers a workaround by using a failover URI. -- Mike On Wed, Jan 11, 2017 at 8:20 PM, Joe Gresock wrote: > Hi folks, >

Re: MergeContent error on restart - not the most recent flow file in this session

I just realized that I had to recopy the lib folder from the new version (1.1.1), as all the stack traces were referencing 1.1.0 code. This change where I cannot link symbolically to the latest version of the software is already causing problems. I have to change my deployment and upgrade process

Re: MergeContent error on restart - not the most recent flow file in this session

Mark Payne wrote > I've not seen this issue, but I created a JIRA [1] to address it. Will try > to replicate it locally and see > if I can understand what is happening. When this happens, do you see the > processor continually > spewing this Exception, rolling back, and trying again? Thank you. I

Re: MergeContent error on restart - not the most recent flow file in this session

Hi Ben, I've not seen this issue, but I created a JIRA [1] to address it. Will try to replicate it locally and see if I can understand what is happening. When this happens, do you see the processor continually spewing this Exception, rolling back, and trying again? This error itself would not r

ActiveMQ trust store issues

Hi folks, I'm using PutJMS to try to send messages to an ActiveMQ broker over SSL. I verified that the trust store referenced in my ssl-context controller service does indeed contain the issuer DN of the broker's certificate, but I get the error "PKIX path building failed: sun.security.provider.c

MergeContent error on restart - not the most recent flow file in this session

This error occurred in NiFi 1.1.1 (single node) right after an upgrade from 1.1.0, so I thought it was due to the upgrade, but now I see that it happens if I restart as well and there is data in the flow. This MergeContent processor is sorting incoming FlowFiles into bins based on a correlation a

Re: Where does javax.net.debug output go?

No, we have not called setOut anywhere before now, and no customizations in logging.properties. I'll see if I can reproduce this with a vanilla installation of NiFi and I'll get back to you. On Wed, Jan 11, 2017 at 7:51 PM, Andy LoPresto wrote: > Have you had to call System.setOut() anywhere el

Re: Where does javax.net.debug output go?

Have you had to call System.setOut() anywhere else in the code base? Anything in your custom processors that redirects output streams? Any custom configurations in $JAVA_HOME/jre/lib/logging.properties? This isn’t something I’ve encountered before — we get questions about log threshold, but I’v

Re: Where does javax.net.debug output go?

CentOS 6.8 with openjdk version "1.8.0_111". I did also try running nifi directly using nifi.sh start, to the same effect. I was able to work around the issue by calling System.setOut(...) inside one of my custom processors, so I at least have the debugging info I need. However, it would still be

Re: Where does javax.net.debug output go?

Joe, Sorry you are experiencing difficulty with this. SSL debugging is a feature I use often. You should see this output in logs/nifi-bootstrap.log. Ensure you do not have another Java arg with a conflicting argument number in bootstrap.conf (although as you have put it as 16, I think you shoul

Where does javax.net.debug output go?

Hi folks, I'm trying to turn on SSL verbose logging using java.arg.16=-Djavax.net.debug=ssl,handshake in my bootstrap.conf (nifi version 1.1.0). As far as I can remember, this output goes to either stdout or stderr (I forget which). As a result, I'm trying to find the output in my nifi-bootstrap

Re: NiFi cannot start due to log permissions error

Andy LoPresto-2 wrote > The illegal key size error is almost certainly due to the length of the > keystore/truststore password, but the ideal solution is not to decrease > the password length, but rather to either install the Unlimited Strength > Jurisdiction Policy files if possible, and/or switch

Re: local NiFi and MiNiFi - yml generation errors

Hi Pushkar, In the tutorial you link to, it looks like before generating the template, you need to select just subsection of the flow shown. Currently MiNiFi does not support Input or Output ports in the root process group so if you were to create a template from the whole flow, it would be inval

Re: MiNiFi event-based scheduling?

All, Please review/merge pull request https://github.com/apache/nifi-minifi-cpp/pull/40 which adds event-based scheduling. Regards, Andy P.S. Thanks for the info Mark (missed your email earlier). I did notice the bored duration seemed to be implemented in minifi-cpp. Thankfully, we now have

local NiFi and MiNiFi - yml generation errors

Hi, I was using this tutorial to get started with NiFi and MiNiFi. At step 11 in the linked tutorial, I tried creating the yml for the given template. I couldn't find the config.sh file in the latest source of mini