Default logLevel DEBUG or INFO? about ixmp

[danielhuppmann]

Sorry, I believe that the output in your screenshot is determined in the compiled ixmp.jar, and this is distinct from the _LOGGER.setLevel(). Not sure why this was changed in the first place before the latest release.

We will rework the Java logging in the next release.

[tzipperle]

Make sense, because I could not get access via the python logging root handler...

[gidden]

@zikolach and @fonfon would it be possible to access and set the log level in java from python as well?

[zikolach]

@gidden you can do it by programmatically by calling e.g.:

org.apache.log4j.Logger.getLogger(Platform.class.getPackage().getName()).setLevel(org.apache.log4j.Level.DEBUG)

Alternatively I can add a (static) method to Platform class for setting it. But we have bundled log4j.properties file with some predefined settings:

log4j.appender.FA=org.apache.log4j.DailyRollingFileAppender
log4j.appender.FA.file=D:/tmp/GasmAgeServlet-app.log
log4j.rootLogger=FA, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d %5p %c:%L - %m%n
log4j.logger.at.ac.iiasa.kolp.cleanage.servlet.DatabaseHelper=info
log4j.logger.at.ac.iiasa.ixmp.servlet.AuthDbFilter=info
log4j.logger.at.ac.iiasa.ixmp.servlet.RestServlet=debug

which I would replace with

log4j.rootLogger=WARN, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d %5p %c:%L - %m%n
log4j.logger.org.flywaydb.core.internal=warn

as default

[khaeru]

Hi @tzipperle —going to close this now since the code is substantially changed and I don't suspect this can occur anymore. Now, the top-level ("ixmp") logger is configured here:

ixmp/ixmp/__init__.py

Lines 44 to 48 in 59e99e4

	# Configure the 'ixmp' logger: write messages to std out, defaulting to level
	# WARNING and above
	log = logging.getLogger(__name__)
	log.addHandler(logging.StreamHandler())
	log.setLevel(logging.WARNING)

The Java backend, at the point when any new Platform is instantiated, uses either a user argument or copies this value:

ixmp/ixmp/backend/jdbc.py

Lines 212 to 216 in 59e99e4

	# Extract a log_level keyword argument before _create_properties().
	# By default, use the same level as the 'ixmp' logger, whatever that
	# has been set to.
	ixmp_logger = logging.getLogger('ixmp')
	log_level = kwargs.pop('log_level', ixmp_logger.getEffectiveLevel())

After this, the mp.set_log_level() method can be used to control the log messages emitted from Java. At any time or point, the "ixmp" logger can be manipulated in the usual Python way.

If any similar issue is still happening with the newest code, please open a new issue.