New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSGI can't use Logger #20039
Comments
wezell
added a commit
that referenced
this issue
Mar 5, 2021
dsilvam
pushed a commit
that referenced
this issue
Mar 10, 2021
Tested with the Cronjob example plugin |
Passed Internal QA: Job plugin still logging after redeployment. |
Uploaded and started
Stopped and undeployed
Started again
|
Fixed, tested on release-21.04 // Postgres |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
If you register an OSGI plugin, and in that use the dotCMS class
Logger
it will log output - but only the first time it is loaded. If you then undeploy the plugin and then redeploy it, logging will no longer work. This is because we are using the class as a key for the map of loggers and the original class that registered the logger is no longer available in the classpath and throws an error when theclazz.getName
is called.We need to use Strings as the keys to the logger map. This will make it more resilient to class loading issues.
The text was updated successfully, but these errors were encountered: