[ https://issues.jboss.org/browse/JBAS-9441?page=com.atlassian.jira.plugin.... ] Joe Mihalich updated JBAS-9441: ------------------------------- Description: In 6.1.0, using a log4j RollingFileAppender (we actually subclass it, but I'm sure it's an issue with at least all FileAppenders), I get this error when it tries to switch from the bootstrap logger to the jboss-logging.xml loggers: org.jboss.logging.service : Removing bootstrap log handlers [STDERR] log4j:ERROR No output stream or file set for the appender named [null]. I have a forum thread going here for this. http://community.jboss.org/thread/171093. My jboss-logging.xml file is attached in the forum thread. Reapplying the 6.0 Final patch from here, fixes the problem: https://issues.jboss.org/browse/JBAS-8791 was: In 6.1.0, using a log4j RollingFileAppender (we actually subclass it), I get this error when it tries to switch from the bootstrap logger to the jboss-logging.xml loggers: org.jboss.logging.service : Removing bootstrap log handlers [STDERR] log4j:ERROR No output stream or file set for the appender named [null]. I have a forum thread going here for this. http://community.jboss.org/thread/171093. My jboss-logging.xml file is attached in the forum thread. Reapplying the 6.0 Final patch from here, fixes the problem: https://issues.jboss.org/browse/JBAS-8791 Forum Reference: http://community.jboss.org/thread/171093 (was: http://community.jboss.org/thread/171093) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9441?page=com.atlassian.jira.plugin.... ] Chris Dollar commented on JBAS-9441: ------------------------------------ I am having problems using the log4j JMS appender with 6.0 and 6.1, so perhaps the two problems are related? http://community.jboss.org/thread/170963 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9441?page=com.atlassian.jira.plugin.... ] Joe Mihalich edited comment on JBAS-9441 at 8/18/11 12:40 PM: -------------------------------------------------------------- Hi, drop our jar file into your server/<config>/lib directory. The jar only has one class in it...the one that you're getting the CNFE. Attached the jar to the ticket. I'd think you'd get this by using any of the log4j File Appenders in the shipped jboss-logging.xml file too... was (Author: jmihalich1): Hi, drop our jar file into your server/<config>/lib directory. The jar only has one class in it...the one that you're getting the CNFE. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9441?page=com.atlassian.jira.plugin.... ] Joe Mihalich edited comment on JBAS-9441 at 8/18/11 12:46 PM: -------------------------------------------------------------- Hi Shelly, drop our jar file into your server/<config>/lib directory. The jar only has one class in it...the one that you're getting the CNFE. Attached the jar to the ticket. I'd think you'd get this by using any of the log4j File Appenders in the shipped jboss-logging.xml file too... Edit: Sorry, I noticed now that there are no log4j file based rolling file appenders in the shipped jboss-logging.xml...only email, jms, etc based ones. was (Author: jmihalich1): Hi Shelly, drop our jar file into your server/<config>/lib directory. The jar only has one class in it...the one that you're getting the CNFE. Attached the jar to the ticket. I'd think you'd get this by using any of the log4j File Appenders in the shipped jboss-logging.xml file too... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9441?page=com.atlassian.jira.plugin.... ] Joe Mihalich edited comment on JBAS-9441 at 8/18/11 1:01 PM: ------------------------------------------------------------- Hmmm, this appears to be specific to our log4j appender. We don't set the "file" parameter/property (that's what the error we get is complaining about) because we build the file name dynamically based on the other properties we pass in. Using the DailyRollingFileAppender from the 8791 ticket, that works because it's passing in the file param/property. I'd like to understand why the patch from Jira 8791 fixes this though. Our appender works fine in jboss 4.2.3, and 6.0/6.1 with that patch. Thanks, Joe was (Author: jmihalich1): Hmmm, this appears to be specific to our log4j appender. We don't set the "file" parameter/property (that's what the error we get is complaining about) because we build the file name dynamically based on the other properties we pass in. I'd like to understand why the patch from Jira 8791 fixes this though. Our appender works fine in jboss 4.2.3, and 6.0/6.1 with that patch. Thanks, Joe -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9441?page=com.atlassian.jira.plugin.... ] Shelly McGowan commented on JBAS-9441: -------------------------------------- Of the 3 jars provided in the attachment of JBAS-8791, the logging-service-metadata.jar (v 1.0.0.CR10) remained the same in 6.1.0. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira