openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Co (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-355) OpenJPA Log4J factory incorrectly handles logging level
Date Fri, 07 Sep 2007 07:43:30 GMT

     [ 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.


Mime
View raw message