FWIW, the https://issues.apache.org/jira/browse/NIFI-3255 issue has been resolved and is available in the current master. ... View more

Yes, you can see there are two properties in ConsumeJMS processor User Name and Password. So you can provide them there. ... View more

Ok, based on your additional info that was just posted you are having a connection issue to localhost:1419 Have you explicitly change it from the default port of 1414? I know you have a config window that shows some kind of listener on on 1419, but I am not sure what that is. In any event, you're definitely having networking issue so, let's try this and see if you can connect to either 1419 and 1414 via telnet. From the terminal window execute the following: > telnet localhost 1419 Repeat the same for 1414 Let me know ... View more

What error are you getting now? Could you please post Also, it appears form your configuration that your queue name is 'Q1' but in NiFi config you're using 'queue://NiFiMQ' instead of 'queue://Q1' I am not MQ administrator and there is nothing specific to NiFi anyone on the MQ side needs to do. Do you have a plain Java program that is able to send/receive messages from MQ instance you have created. That would be the easiest way to debug. The information such as queue, channel, queueManager, transportType and many other is provided by MQ administrators and have no relevance to NiFi. ... View more

Andy What happened with your previous post on the same subject? https://community.hortonworks.com/questions/84466/nifi-disabled-controller-services-and-consumejms-f.html#answer-84556 Have you tried what I have suggested? Thank you Oleg ... View more

The exception messages and error reporting you see above probably needs to be reviewed and polished as they are inconclusive and not informative. Could you please look at the logs and post the stack trace related to the above. ... View more

Pradhuman Would you mind provide more information such as full stack trace etc. It's nearly impossible to diagnose the issue with information provided. Thanks Oleg ... View more

Just in case you are not familiar with dynamic properties look for a '+' sign in the top right corner of the configuration window for CS. Click on the '+' and enter the name of the property (i.e., transportType) and then value of '1'. ... View more

Andy, the error you see is due to the fact that the connection attempt is made over native transport protocol using JNI and the required native libraries are not present on the classpath. To avoid it you should rely on TCP transport type. NOTE: the dynamic property mentioned above 'transportType". It's values should be set to 1 (which denotes TCP). Keep in mind that the other two properties described above (channel and queueManager) are also required Also, the document you've provided describes JNDI configuration which we do not currently support. ... View more