Cannot disable logging via configuration file

[bennylut]

Hi, just came across your libraries - awsome stuff!

I wish to use the HostResolutionRequestInterceptor from the burningwave:tools repository.
When doing so, I have a lot of information printed to my log that I wish to remove:

2023-04-13 09:35:18.190 [main] - org.burningwave.core.assembler.StaticComponentContainer - (StaticComponentContainer.java:369) - 

	Configuration values for static components:

		background-executor.all-tasks-monitoring.enabled=\
			true
...

I followed the documentation and created a resource file burningwave.static.properties, which includes:

managed-logger.repository=autodetect
managed-logger.repository.enabled=false
buffer-handler.default-buffer-size=1024
buffer-handler.default-allocation-mode=ByteBuffer::allocateDirect
banner.hide=true

After creating this file the banner is not shown anymore but the logs are still printed, so I tried to configure the log level to OFF on StaticComponentContainer using logback:

// very crud just to check that it works..
(LoggerFactory.getLogger(StaticComponentContainer::class.java) as ch.qos.logback.classic.Logger).level = Level.OFF

But that still does not work..

Is there anything I am missing?
Thanks!

[Roberto-Gentili]

Could you post the logged lines?

[bennylut]

Sure,
Thanks

2023-04-13 04:12:49.861 [main] - org.burningwave.core.assembler.StaticComponentContainer - (StaticComponentContainer.java:368) - Instantiated org.burningwave.core.SimpleManagedLoggerRepository
2023-04-13 04:12:49.863 [main] - org.burningwave.core.assembler.StaticComponentContainer - (StaticComponentContainer.java:369) - 

	Configuration values for static components:

		background-executor.all-tasks-monitoring.enabled=\
			true
		background-executor.all-tasks-monitoring.interval=\
			30000
		background-executor.all-tasks-monitoring.logger.enabled=\
			false
		background-executor.all-tasks-monitoring.minimum-elapsed-time-to-consider-a-task-as-probable-dead-locked=\
			300000
		background-executor.all-tasks-monitoring.probable-dead-locked-tasks-handling.policy=\
			log only
		background-executor.queued-task-executor[0].name=\
			Low priority tasks
		background-executor.queued-task-executor[0].priority=\
			1
		background-executor.queued-task-executor[1].name=\
			Normal priority tasks
		background-executor.queued-task-executor[1].priority=\
			5
		background-executor.queued-task-executor[2].name=\
			High priority tasks
		background-executor.queued-task-executor[2].priority=\
			10
		background-executor.task-creation-tracking.enabled=\
			${background-executor.all-tasks-monitoring.enabled}
		banner.additonal-informations=\
			${Implementation-Title} ${Implementation-Version}
		banner.additonal-informations.retrieve-from-manifest-file-with-implementation-title=\
			Burningwave Core
		banner.file=\
			org/burningwave/banner.bwb
		banner.hide=\
			true
		buffer-handler.default-allocation-mode=\
			ByteBuffer::allocateDirect
		buffer-handler.default-buffer-size=\
			0.5Kb
		group-name-for-named-elements=\
			Burningwave
		iterable-object-helper.default-values-separator=\
			;
		iterable-object-helper.parallel-iteration.applicability.default-minimum-collection-size=\
			2
		iterable-object-helper.parallel-iteration.applicability.max-runtime-thread-count-threshold=\
			autodetect
		iterable-object-helper.parallel-iteration.applicability.output-collection-enabled-types=\
			java.util.concurrent.ConcurrentHashMap$CollectionView;\
			java.util.Collections$SynchronizedCollection;\
			java.util.concurrent.CopyOnWriteArrayList;\
			java.util.concurrent.CopyOnWriteArraySet;\
			java.util.concurrent.BlockingQueue;\
			java.util.concurrent.ConcurrentSkipListSet;\
			java.util.concurrent.ConcurrentSkipListMap$EntrySet;\
			java.util.concurrent.ConcurrentSkipListMap$KeySet;\
			java.util.concurrent.ConcurrentSkipListMap$Values;
		jvm.driver.init=\
			true
		managed-logger.repository=\
			org.burningwave.core.SimpleManagedLoggerRepository
		managed-logger.repository.enabled=\
			true
		managed-logger.repository.logging.debug.disabled-for=\
			org.burningwave.core.io.FileSystemItem;\
			org.burningwave.core.classes.MemoryClassLoader;\
			org.burningwave.core.classes.PathScannerClassLoader;
		managed-logger.repository.logging.warn.disabled-for=\
			org.burningwave.core.assembler.ComponentContainer$ClassLoader;\
			org.burningwave.core.classes.MemoryClassLoader;\
			org.burningwave.core.classes.PathScannerClassLoader;
		modules.export-all-to-all=\
			true
		resource-releaser.enabled=\
			true
		synchronizer.all-threads-monitoring.enabled=\
			false
		synchronizer.all-threads-monitoring.interval=\
			90000
		thread-supplier.default-daemon-flag-value=\
			true
		thread-supplier.default-thread-priority=\
			5
		thread-supplier.max-detached-thread-count=\
			${thread-supplier.max-poolable-thread-count}
		thread-supplier.max-detached-thread-count.elapsed-time-threshold-from-last-increase-for-gradual-decreasing-to-initial-value=\
			30000
		thread-supplier.max-detached-thread-count.increasing-step=\
			autodetect
		thread-supplier.max-poolable-thread-count=\
			autodetect
		thread-supplier.poolable-thread-request-timeout=\
			6000

[Roberto-Gentili]

As you can see in the log the managed-logger.repository.enabled is set to true: Burningwave is not loading the configuration file

[bennylut]

Thanks for the response, It does not seems to be the case, as can be seen, the banner.hide configuration were taken from the configuration file (set to true).
I double checked and set banner.hide=false in the configuration file and the banner is reappearing

In addition, I tried to override the configuration programmatically via the following code:

StaticComponentContainer.Configuration.Default.add(mapOf("managed-logger.repository.enabled" to "false"))

which yield the same results (also did not work)..

[Roberto-Gentili]

Try to increase the priority of your configuration file by setting the property priority-of-this-configuration

[bennylut]

@Roberto-Gentili, It worked, thank you! I set the priority to 1000 :)