You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2007/08/11 03:41:42 UTC
[jira] Created: (GERONIMO-3400) Log4JService Env and JVM info is no
longer being logged
Log4JService Env and JVM info is no longer being logged
-------------------------------------------------------
Key: GERONIMO-3400
URL: https://issues.apache.org/jira/browse/GERONIMO-3400
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: Logging
Affects Versions: 2.0, 2.0.x, 2.1
Reporter: Donald Woods
Assignee: Donald Woods
Priority: Minor
Fix For: 2.0.x, 2.1
When the log4j.rootLogger was switched to ERROR instead of INFO, we lost the server startup logging in Log4JService that logs some useful environment and Java information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3400) Log4JService Env and JVM info is no
longer being logged
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated GERONIMO-3400:
-----------------------------------
Fix Version/s: (was: 2.0.x)
2.0.1
Updated Fixed For field
> Log4JService Env and JVM info is no longer being logged
> -------------------------------------------------------
>
> Key: GERONIMO-3400
> URL: https://issues.apache.org/jira/browse/GERONIMO-3400
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Logging
> Affects Versions: 2.0, 2.0.x, 2.1
> Reporter: Donald Woods
> Assignee: Donald Woods
> Priority: Minor
> Fix For: 2.0.1, 2.1
>
>
> When the log4j.rootLogger was switched to ERROR instead of INFO, we lost the server startup logging in Log4JService that logs some useful environment and Java information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3400) Log4JService Env and JVM info is no
longer being logged
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods closed GERONIMO-3400.
----------------------------------
Resolution: Fixed
Committed revision 564818 in trunk (2.1)
Committed revision 564819 in branches/2.0 (2.0.1)
> Log4JService Env and JVM info is no longer being logged
> -------------------------------------------------------
>
> Key: GERONIMO-3400
> URL: https://issues.apache.org/jira/browse/GERONIMO-3400
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Logging
> Affects Versions: 2.0, 2.0.x, 2.1
> Reporter: Donald Woods
> Assignee: Donald Woods
> Priority: Minor
> Fix For: 2.0.x, 2.1
>
>
> When the log4j.rootLogger was switched to ERROR instead of INFO, we lost the server startup logging in Log4JService that logs some useful environment and Java information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.