[logback-dev] [JIRA] Commented: (LBCORE-215) File Applender log twice in an EJB project on Glassfish 3.1.

Jose Guerra (JIRA) noreply-jira at qos.ch
Thu Jul 14 13:00:53 CEST 2011

    [ http://jira.qos.ch/browse/LBCORE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12060#action_12060 ] 

Jose Guerra commented on LBCORE-215:

Never mind !. I missed to reset the logger context. Now logger and logback 0.9.29 is working nicely on an EJB project.

> File Applender log twice in an EJB project on Glassfish 3.1.
> ------------------------------------------------------------
>                 Key: LBCORE-215
>                 URL: http://jira.qos.ch/browse/LBCORE-215
>             Project: logback-core
>          Issue Type: Bug
>          Components: Appender
>    Affects Versions: 0.9.29
>         Environment: Glassfish 3.1 +  JDK 1.6.24 - JEE 6 - Ubuntu 11.04 x86_64
>            Reporter: Jose Guerra
>            Assignee: Logback dev list
>            Priority: Critical
> Not sure what's going on but the thing is that the log file appender logs everything twice in a EJB project.
> I want an EJB jar file with its own log file to be deployed on Glassfish 3.1. I am getting the Classloader and the resource (logback.xml) located in a directory.  The URL to logback.xml is loaded up into Joran Configurator sucessfully. There are no configuration errors at all. The EJB starts to log in the file when it is deployed but every log output is twice !!.
> The weirdest thing is that if I create an web application, and I load up the configuration using the same approach(Joran Configurator), the logger works perfectly. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the logback-dev mailing list