Closed SlowMo24 closed 2 years ago
Problem OSHDB chose slf4j as abstraction-layer with simple-logger as default framework for logging.
Currently the following error-message is displayed when initializing an OSHDBIgnite:
OSHDBIgnite
Apr 25, 2019 10:21:50 AM java.util.logging.LogManager$RootLogger log WARNUNG: Failed to resolve default logging config file: config/java.util.logging.properties
because Ignite logs with java.util as default. Logs are therefore also not captured by our default logger.
Also clients get no notification on logs on the server (e.g. failures).
Possible solution Clients should be started with slf4j as described in the ignite-docs.
Clients should also get logs from servers, at least failures. Therefore possibly event subscription would have to be implemented (like for #105 ).
The current solution is "good enough" from our point of view. Out of scope for OSHDB.
Problem OSHDB chose slf4j as abstraction-layer with simple-logger as default framework for logging.
Currently the following error-message is displayed when initializing an
OSHDBIgnite
:because Ignite logs with java.util as default. Logs are therefore also not captured by our default logger.
Also clients get no notification on logs on the server (e.g. failures).
Possible solution Clients should be started with slf4j as described in the ignite-docs.
Clients should also get logs from servers, at least failures. Therefore possibly event subscription would have to be implemented (like for #105 ).