You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Adrian Co (JIRA)" <ji...@apache.org> on 2007/09/07 09:41:33 UTC
[jira] Created: (OPENJPA-355) OpenJPA Log4J factory incorrectly
handles logging level
OpenJPA Log4J factory incorrectly handles logging level
-------------------------------------------------------
Key: OPENJPA-355
URL: https://issues.apache.org/jira/browse/OPENJPA-355
Project: OpenJPA
Issue Type: Bug
Components: logging
Affects Versions: 1.0.0, 1.1.0
Reporter: Adrian Co
Priority: Minor
Setting the log4j level to DEBUG, is unable to display INFO, WARN or higher level logging level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-355) OpenJPA Log4J factory incorrectly
handles logging level
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Russell updated OPENJPA-355:
----------------------------------
Affects Version/s: (was: 1.1.0)
Remove 1.1.0 as an affected version.
> OpenJPA Log4J factory incorrectly handles logging level
> -------------------------------------------------------
>
> Key: OPENJPA-355
> URL: https://issues.apache.org/jira/browse/OPENJPA-355
> Project: OpenJPA
> Issue Type: Bug
> Components: logging
> Affects Versions: 1.0.0
> Reporter: Adrian Co
> Assignee: Craig Russell
> Priority: Minor
> Fix For: 1.0.1, 1.1.0
>
> Attachments: openjpa-355-trunk.patch
>
>
> Setting the log4j level to DEBUG, is unable to display INFO, WARN or higher level logging level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-355) OpenJPA Log4J factory incorrectly
handles logging level
Posted by "Patrick Linskey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Linskey updated OPENJPA-355:
------------------------------------
Fix Version/s: 1.0.1
> OpenJPA Log4J factory incorrectly handles logging level
> -------------------------------------------------------
>
> Key: OPENJPA-355
> URL: https://issues.apache.org/jira/browse/OPENJPA-355
> Project: OpenJPA
> Issue Type: Bug
> Components: logging
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Adrian Co
> Assignee: Craig Russell
> Priority: Minor
> Fix For: 1.0.1, 1.1.0
>
> Attachments: openjpa-355-trunk.patch
>
>
> Setting the log4j level to DEBUG, is unable to display INFO, WARN or higher level logging level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-355) OpenJPA Log4J factory incorrectly
handles logging level
Posted by "Adrian Co (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Co updated OPENJPA-355:
------------------------------
Attachment: openjpa-355-trunk.patch
Attach is a patch to fix the issue.
Either use _log.isEnabledFor(Level.FATAL) (in the patch)
or swap the comparison. (i.e. Level.WARN >= _log.getEffectiveLevel().toInt() )
Either one should work I think. :)
> OpenJPA Log4J factory incorrectly handles logging level
> -------------------------------------------------------
>
> Key: OPENJPA-355
> URL: https://issues.apache.org/jira/browse/OPENJPA-355
> Project: OpenJPA
> Issue Type: Bug
> Components: logging
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Adrian Co
> Priority: Minor
> Attachments: openjpa-355-trunk.patch
>
>
> Setting the log4j level to DEBUG, is unable to display INFO, WARN or higher level logging level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-355) OpenJPA Log4J factory incorrectly
handles logging level
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Russell resolved OPENJPA-355.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0
Assignee: Craig Russell
svn commit
Sending openjpa-lib/src/main/java/org/apache/openjpa/lib/log/Log4JLogFactory.java
Transmitting file data .
Committed revision 573653.
> OpenJPA Log4J factory incorrectly handles logging level
> -------------------------------------------------------
>
> Key: OPENJPA-355
> URL: https://issues.apache.org/jira/browse/OPENJPA-355
> Project: OpenJPA
> Issue Type: Bug
> Components: logging
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Adrian Co
> Assignee: Craig Russell
> Priority: Minor
> Fix For: 1.1.0
>
> Attachments: openjpa-355-trunk.patch
>
>
> Setting the log4j level to DEBUG, is unable to display INFO, WARN or higher level logging level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.