You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At least for the Data Service and Validator Service the application logging is not working anymore. The logging is fully filter out, even after setting the levels at debug level. It needs to be check for the CIM Mapping Service and Auto Alignment Service.
If last two are still working it can be related with the introduction of Websocket and EventBus (Reactive implementation).
Steps to reproduce
Start using the service using a Container Image and check the console logging of the container, no logging is found for the application, so nothing from the package 'org.lfenergy'. There should be a minimum of logging displayed.
When starting the service from a IDE or Maven it works correctly and the logging is displayed.
Expected behaviour
Application logging found in the console.
Actual behaviour
No application logging found in the console.
The text was updated successfully, but these errors were encountered:
After discussing it internally we will try to switch to log4j2.
If slf4j is used by others slf4j can be configure to also process the log4j2 lines.
And Quarkus has a LogManager for log4j2 also.
Subject of the issue
At least for the Data Service and Validator Service the application logging is not working anymore. The logging is fully filter out, even after setting the levels at debug level. It needs to be check for the CIM Mapping Service and Auto Alignment Service.
If last two are still working it can be related with the introduction of Websocket and EventBus (Reactive implementation).
Steps to reproduce
Start using the service using a Container Image and check the console logging of the container, no logging is found for the application, so nothing from the package 'org.lfenergy'. There should be a minimum of logging displayed.
When starting the service from a IDE or Maven it works correctly and the logging is displayed.
Expected behaviour
Application logging found in the console.
Actual behaviour
No application logging found in the console.
The text was updated successfully, but these errors were encountered: