I'm afraid I don't even know really know what NiFi is, but essentially it should be pretty obvious from your classpath what is happening, and it may or may not involve NiFi directly. In the past, SLF4J would complain if there was more than one logging binding available, so its possible there is only one, particularly if you dont know you are supplying it. You'll then need to configure it appropriately to your (/its) needs, or perhaps even change to an entirely different logging implemetnation of your choice. Log4J historically did default to debug level if not configured, so if that is being supplied elsewhere then it might be your issue, you've introduced another element and might need to supply appropriate configuration for it (/update the existing configuration if there is some).
On 11 April 2017 at 14:49, Vince Cole <[email protected]> wrote: > OK thanks, will ask the NiFi guys > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/qpid-jms-client-writing-passwords-to-the-log-tp7662189p7662193.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
