[
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
Log4j File Appenders do not work in jboss 6.1.0-Final
-----------------------------------------------------
Key: JBAS-9441
URL:
https://issues.jboss.org/browse/JBAS-9441
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Logging
Affects Versions: 6.1.0
Environment: Probably all OS's.
Reporter: Joe Mihalich
Assignee: David Lloyd
Attachments: jboss-logging.xml, vue-log4j.jar
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
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira