It would be great if this “ugly text noise” would vanish asap, since its hard to simply ignore it if it appears everywhere in the logs and make everything more complicated and always causing the impression to everyone who has to look at (and don’t know already) there is a big problem underneath.
(Take two…) There are two loggers at play when running KNIME in batch mode; first is the ‘standard’ Java logger, and then sometime later the log4j logger comes online.
You can tell both of these loggers to not emit anything related to the CXF Blueprint unless it is a highest-level error message (these messages appear to be coming from a level below that - WARN/WARNING.) I’m attaching a configuration file for each logger; in your Knime.ini file add these two lines:
-Djava.util.logging.config.file=/some/absolute/path/silence_blueprint_log.properties
-Dlog4j.configuration=/some/absolute/path/silence_blueprint_log4j.xml
silence_blueprint_logger_configs.zip (2.7 KB)
3 Likes
Hi KNIME Team,
By any chance is this CFX Blueprint error logs resolved with KNIME 4.2 as the eclipse version has been upgraded?
Thanks
Ravikiran
I still see this error in batch mode for v4.2.
1 Like
Maybe solved in 4.3 
Hi everyone,
is this the error you guys are referring to? Has anyone managed to have a solution too as unfortunately, I’m in the same scenario even with the latest version of KNIME.
BUMP! Is nobody using KNIME in btach mode on windows then? Because this seems to be a showstopper for me