[
https://issues.apache.org/jira/browse/GERONIMO-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696237#action_12696237
]
Thad West commented on GERONIMO-4287:
-------------------------------------
Any updates? This makes application specific logging much less attractive.
> geronimo.out and geronimo.log stop logging with application specific loggin
> is enabled and the app is undeployed
> ----------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-4287
> URL: https://issues.apache.org/jira/browse/GERONIMO-4287
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Logging
> Affects Versions: 2.1.2
> Environment: Java 1.5 Mac OS X 10.4.11 Intel
> Reporter: Adam Ruggles
>
> I using the following configuration:
> <gbean name="SupportLog4jConfiguration"
> class="org.apache.geronimo.system.logging.log4j.ApplicationLog4jConfigurationGBean">
> <attribute name="log4jFile">var/log/app-log.properties</attribute>
> <reference name="ServerInfo">
> <name>ServerInfo</name>
> </reference>
> </gbean>
> If I start geronimo and deploy my app the logging works fine, both for the
> application and geronimo (out and log). When I undeploy my application the
> geronimo logging no longer writes to the log files. In my log4j properties I
> am capturing generic com, org, and net appenders in my application specific
> logging. Redeploying my application does not fix the geronimo logs but the
> application logs still function.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
