Hi, If you are already using slf4j, the migration from log4j to logback should be seamless; as in just a drop-in replacement of log4j.properties for logback.xml.
Do you get any logs in your run? If not, then probably you might want to confirm if logback.xml is indeed present in the classpath while execution. If classpath is fine, then you might want to check if the logback.xml is proper. You can try official translator [1] for migrating log4j.properties to logback.xml just to reconfirm your conversion was fine. [1]: http://logback.qos.ch/translator From: Bryan Baugher [mailto:[email protected]] Sent: 06 November 2014 21:28 To: user Subject: Set default log levels in a topology jar Hi everyone, We recently switched to Storm 0.9.2 which moved to logback. We use the slf4j API and provide a log4j.properties in our topology jar but noticed the log levels set in the log4j.properties were not being honored. I read in the doc for log4j-over-slf4j[1] that 'Note that as a result of this migration, log4j configuration files will no longer be picked up.' So I converted my log4j.properties to logback.xml and re-deployed the topology but the log levels still don't seem to be honored. Does anyone have any suggestions on things I should try? [1] - http://www.slf4j.org/legacy.html ______________________________________________________________________ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.
