[
https://issues.apache.org/jira/browse/GERONIMO-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jack Cai updated GERONIMO-4773:
-------------------------------
Attachment: GERONIMO-4773.patch
Turns out the root cause is because we moved to slf4j in 2.2 and removed the
log classes in kernel.
To eliminate the annoying warning message, one solution is to simply add a
log4j.properties config file to shutdown.jar.
Also, no reason now to keep the file
framework/modules/geronimo-kernel/src/main/resources/META-INF/services/org.apache.commons.logging.LogFactory,
as it points to a class that does not exist any more.
Please review the patch. Built and tested.
> logger not initialized in shutdown command
> ------------------------------------------
>
> Key: GERONIMO-4773
> URL: https://issues.apache.org/jira/browse/GERONIMO-4773
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.2
> Reporter: Jack Cai
> Priority: Minor
> Attachments: GERONIMO-4773.patch
>
>
> When issue the shutdown command, the following warning messages will be shown
> every time.
> {quote}
> log4j:WARN No appenders could be found for logger
> (org.apache.geronimo.kernel.basic.BasicKernel).
> log4j:WARN Please initialize the log4j system properly.
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
