gmane.comp.jakarta.log4j.devel

DO NOT REPLY [Bug 42213] log4j causing threads to stuck in weblogic

2008-10-07T19:01:30

https://issues.apache.org/bugzilla/show_bug.cgi?id=42213 Sachin gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sachinlohe< at >gmail.com Status|RESOLVED |REOPENED Resolution|DUPLICATE | --- Comment #5 from Sachin gmail.com> 2008-10-07 12:01:29 PST --- We have same environment and same issue. Sudhanshu/Anyone who want to answer : How was this issue resolved finally. Duplicate bug(41214) comment 22 mentioned that this may be jre1.5 solaris bug. "[STUCK] ExecuteThread: '93' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x00000001071bbea0 nid=0x5a0 runnable [0xfffffffe9a3fd000..0xfffffffe9a3ff6a8] at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:260) at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336) at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404) at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408) at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152) - locked <0xffffffff19c95178> (a java.io.OutputStreamWriter) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213) at org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:49) at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:311) at org.apache.log4j.DailyRollingFileAppender.subAppend(DailyRollingFileAppender.java:343) at org.apache.log4j.WriterAppender.append(WriterAppender.java:150) at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:222) - locked <0xfffffffefa9acfe8> (a org.apache.log4j.DailyRollingFileAppender) at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57) at org.apache.log4j.Category.callAppenders(Category.java:190) - locked <0xfffffffefa7ecfb0> (a org.apache.log4j.spi.RootCategory) at org.apache.log4j.Category.forcedLog(Category.java:375) at org.apache.log4j.Category.log(Category.java:868) at org.apache.commons.logging.impl.Log4JCategoryLog.debug(Log4JCategoryLog.java:165)

Bug report for Log4j [2008/10/05]

2008-10-06T06:08:17

+---------------------------------------------------------------------------+ | Bugzilla Bug ID | | +---------------------------------------------------------------------+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned | | | OPN=Reopened VER=Verified (Skipped Closed/Resolved) | | | +-----------------------------------------------------------------+ | | | Severity: BLK=Blocker CRI=Critical REG=Regression MAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement TRV=Trivial | | | | +-------------------------------------------------------------+ | | | | Date Posted | | | | | +--------------------------------------------------+ | | | | | Description | | | | | | | |13099|Opn|Nor|2002-09-27|DOMConfigurator ignores category factory setting | |17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads | |20395|Inf|Enh|2003-06-01|PreparedStatementAppender Enhancement | |23329|Ass|Enh|2003-09-22| element in XML config should support reso| |25355|Ass|Enh|2003-12-09|allow to require "TLS/SSL only" for outgoing mails| |26084|Inf|Nor|2004-01-13|Log Event detail panel does not show special chara| |27363|Inf|Enh|2004-03-02|JNI based SyslogAppender | |27367|Inf|Enh|2004-03-02|NetSendAppender | |28647|Ass|Enh|2004-04-28|Add "Flush on Level" capability to FileAppender | |29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM| |29304|New|Nor|2004-05-30|Starting XMLSocketAppender from config file | |29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe| |29735|New|Nor|2004-06-22|Receiver list display error when receiver has no | |30055|New|Nor|2004-07-12|Problem with registering Appenders with the same n| |30407|Inf|Maj|2004-07-30|Externally rolled file problem | |30888|New|Maj|2004-08-27|Chainsaw mixes files in same panel | |30890|New|Min|2004-08-27|Newly opened log file should get focus | |30892|New|Min|2004-08-27|Log files cannot be closed | |31089|New|Nor|2004-09-07|Does not accept ISO8601 dates in focus field | |31178|Inf|Cri|2004-09-11|Exception using Chainsaw for simple debugging | |31179|Ass|Enh|2004-09-11|Implement Chainsaw as Eclipse stand-alone applicat| |33278|New|Min|2005-01-27|NPE thrown durring daily log file rollover | |33493|Inf|Enh|2005-02-10|contribution to log4j: servlet diagnostic context | |33717|New|Nor|2005-02-23|Leaving out %throwable in ConversionPattern adds t| |34440|New|Nor|2005-04-13|sandbox:IMAppender - comma-seperated recipient lis| |34491|Ver|Nor|2005-04-18|Missing include in build.jms target results in mis| |34651|New|Enh|2005-04-27|allow for a header on top of every rolled file | |34738|New|Nor|2005-05-04|Chainsaw does not remember what Columns are select| |34945|Inf|Nor|2005-05-17|ThrowableInformation has dubious Stack Trace extra| |34974|Inf|Cri|2005-05-19|Exception when running a Pluglet | |35180|New|Min|2005-06-02|Multiple lines "XML files (*.xml)" in drop down li| |35239|Inf|Nor|2005-06-06|NullPointerException when saving displayed events | |35563|Inf|Enh|2005-06-30|Syslog appender parametrability | |35996|Inf|Enh|2005-08-03|Add support for ant-like in log4j.xml | |36435|New|Enh|2005-08-31|Log4J RollingFileAppender under OpenVMS does not f| |36654|Inf|Min|2005-09-14|Provide better error messages for "Please initiali| |36789|Inf|Nor|2005-09-23|Empty control flow statement in org.apache.log4j.l| |36860|New|Enh|2005-09-29|[jmx] Add ability to create a logger MBean for a n| |37349|Ass|Nor|2005-11-03|DBAppender not working with jTDS driver | |37638|New|Nor|2005-11-25|logging doesn't fall back with FallbackErrorHandle| |37734|Inf|Nor|2005-12-01|Customize Event ID and Event Category with NTEVent| |37762|Ass|Enh|2005-12-02|RSSAppender or other approach. | |38061|New|Nor|2005-12-28|Problem configuring an errorHandler using a proper| |38363|Ass|Nor|2006-01-24|SecurityException during log output | |38394|Ver|Enh|2006-01-26|PropertySetter fails to print stacktrace if error | |38395|Ver|Reg|2006-01-26|Unable to set threshold on appender via config fil| |38406|Ver|Nor|2006-01-26|jdk1.4 dependencies in log4j 1.3 alpha | |38513|New|Nor|2006-02-05|[PATCH] Suggested unit test for JMSAppender | |38582|Ass|Nor|2006-02-08|Chainsaw does not include Receiver JavaDoc in dist| |38590|Inf|Nor|2006-02-09|no space on device fails another instance | |38883|Opn|Nor|2006-03-07|LogFilePatternReceiver fails to process multi-line| |38884|New|Nor|2006-03-07|null pointer exception displaying logs if number o| |39690|Inf|Cri|2006-05-31|Initialization fail in J2EE Environment | |39691|Ass|Nor|2006-05-31|DBAppender doesn't log long events | |40068|New|Nor|2006-07-18|Add support for attach-on-demand API to chainsaw | |40124|New|Min|2006-07-27|startup (JWS) does not initialize ignored elements| |40251|Opn|Min|2006-08-14|Hard coded JMX domain name for MBean instances | |40382|Inf|Maj|2006-09-01|Sysappender hangs during boot time on HP | |40385|Inf|Maj|2006-09-01|SocketServer cannot find config file when passed a| |40472|New|Nor|2006-09-11|SettingsManager calls loadSettings with global set| |40533|New|Nor|2006-09-18|Chainsaw not showing all logging statements | |40570|Inf|Blk|2006-09-21|RollingFileAppender does not rollover when the fil| |40611|New|Trv|2006-09-27|Bad subclass example; NullPointerException in Logg| |40736|Inf|Nor|2006-10-11|log4j delete permission denied | |40889|Inf|Nor|2006-11-03|repeated entries in log after failure | |40990|Inf|Nor|2006-11-17|Cannot bind port or ip address for outgoing UDP so| |41006|Inf|Enh|2006-11-20|Contributing XMLSocketHubReceiver | |41214|Ass|Maj|2006-12-19|Deadlock with RollingFileAppender | |41311|Inf|Min|2007-01-06|Please make TimeBasedRollingPolicy non-final? | |41316|New|Nor|2007-01-08|NPE when using RollingFileAppender in Tomcat. | |41547|Inf|Nor|2007-02-05|PropertyConfigurator and layout.contentType | |41799|New|Enh|2007-03-09|SyslogAppender should enable to customize Log4j.Le| |41882|Inf|Nor|2007-03-18|IE7 problems with Log4J web site | |41937|New|Nor|2007-03-23|Logs from some panels missing in custom expression| |41980|Inf|Maj|2007-03-29|Log4j stop updating log file- version log4j-1.2.8 | |42171|New|Nor|2007-04-19|SocketHubReceiver duplicates messages | |42189|Ass|Nor|2007-04-22|Add simple bridge for java.util.logging, with basi| |42516|Inf|Nor|2007-05-24|Log4j failed to log file when packaged in Eclipse | |42664|New|Enh|2007-06-14|JUL Appender | |42842|Opn|Nor|2007-07-09|Create a PUBLIC identifier for the log4j DTD | |42883|Opn|Nor|2007-07-12|'Welcome' and 'Drag & Drop' panels can't be hidden| |42933|Inf|Maj|2007-07-18|IllegalStateException thrown from FileAppender.clo| |43061|Opn|Enh|2007-08-08|Flush appender regularty | |43148|Ass|Nor|2007-08-16|LogFilePatternReceiver depends on jakarta-oro, cou| |43277|New|Nor|2007-08-31|Add LogMF.entering, .exiting and .throwing methods| |43282|Ass|Nor|2007-08-31|Add OSGi packaging info to log4j and companions | |43313|Inf|Nor|2007-09-05|log4j 1.2.16 release considerations and discussion| |43403|Inf|Nor|2007-09-16|PatternLayout: new format modifer: prefix if non-e| |43619|New|Enh|2007-10-13|Simple proposal for pluggable sys-props resolvers | |43637|Inf|Nor|2007-10-16|SocketAppender.append(LoggingEvent) calls the Erro| |43728|Inf|Cri|2007-10-29|Log file loss when specified file is locked by ano| |43736|Ass|Nor|2007-10-30|Chainsaw does not honor encoding when loading XML | |43820|New|Enh|2007-11-08|[PATCH] Layered Configurator Patch | |43879|Inf|Nor|2007-11-16|FileAppender writes Header multiple times | |43911|Inf|Nor|2007-11-20|logfiles not getting rolled over with RollingFileA| |43923|Inf|Min|2007-11-21|JBOSS specific information in javadocs | |44038|Inf|Cri|2007-12-07|log4j is susceptible to exceptions thrown by Excep| |44219|Inf|Nor|2008-01-13|'WARNING' for a log level is silently ignored/chan| |44308|Inf|Enh|2008-01-28|[Patch] JMX component for managing Logger configur| |44357|New|Enh|2008-02-05|List of property keys | |44370|Inf|Reg|2008-02-06|MANIFEST.MF broken in log4j-1.2.15.jar | |44386|Opn|Nor|2008-02-10|NTEventLogAppender.dll for windows 64 | |44526|Inf|Nor|2008-03-04|segmentation fault occuring when PropertyConfigura| |44557|Inf|Nor|2008-03-07|no close call to Appender after replacing the root| |44644|New|Nor|2008-03-20|Default ContentType for Layout is text/html which | |44649|Inf|Nor|2008-03-20|JMS Hangs when a Root Appender | |44700|Inf|Nor|2008-03-28|Log4J locks rolled log files | |44727|Inf|Nor|2008-04-01|Add missing Logger#isErrorEnabled and isWarningEna| |44834|Inf|Nor|2008-04-17|SimpleSocketServer looses buffered logs, produces | |44839|Inf|Nor|2008-04-17|SyslogAppender logging to a UNIX domain socket | |44932|New|Enh|2008-05-05|improve DailyRollingFileAppender handling of rotat| |44934|Inf|Enh|2008-05-05|add helper method to DailyRollingFileAppender to g| |44945|New|Nor|2008-05-06|SyslogAppender not working | |45029|Ass|Nor|2008-05-18|Additional unit tests for Filters in extras compan| |45042|New|Nor|2008-05-19|Need a reliable way to detect misconfiguration | |45068|New|Enh|2008-05-22|Ability to copy contents from log-entries | |45109|New|Nor|2008-05-31|SMTPAppender uses wrong property for mail server | |45165|Ass|Enh|2008-06-09|Multifile Appender | |45224|Inf|Nor|2008-06-17|Log 4j giving nullpointer when reloading applicat| |45231|Inf|Nor|2008-06-18|Clear appenders call on logger calls a helper whic| |45236|Inf|Cri|2008-06-19|Wriring output to an out-dated file. | |45304|New|Nor|2008-06-29|using log4j with OAS for some reasone all the logg| |45305|Inf|Nor|2008-06-29|using log4j with OAS for some reasone all the logg| |45375|New|Enh|2008-07-10|Building log4j core without manually installing li| |45481|New|Trv|2008-07-25|Source contains unused imports | |45482|Inf|Min|2008-07-25|Source contains unused variables | |45493|New|Maj|2008-07-28|Log4j file getting overwritten | |45629|New|Nor|2008-08-13|TopicConnection is not closed | |45660|New|Enh|2008-08-20|NDC could remove Hashtable entry if Stack gets emp| |45704|New|Maj|2008-08-28|Failed to load logging.xml for JRE 1.5.0_16 and We| |45753|New|Nor|2008-09-06|Code contribution | |45781|New|Nor|2008-09-11|RollingFileAppender under Windows does not rotate | |45782|New|Enh|2008-09-11|Add a new appender that zip's rolled files | |45855|New|Enh|2008-09-21|Add site/apt documentation for JULBridgeLogManager| |45915|New|Cri|2008-09-30|DeadLock occured in AsyncAppender | |45932|New|Nor|2008-10-01|Log4j JMX MBeans not cleaned up | |45934|New|Enh|2008-10-02|FileAppender should use virtual-machine shutdown h| |45939|New|Nor|2008-10-02|Cannot drop HierarchyDynamicMBean from LoggerRepos| |45941|Inf|Enh|2008-10-03|Custom PatternLayout | +-----+---+---+----------+--------------------------------------------------+ | Total 139 bugs | +---------------------------------------------------------------------------+

DO NOT REPLY [Bug 45941] Custom PatternLayout

2008-10-03T13:15:52

https://issues.apache.org/bugzilla/show_bug.cgi?id=45941 Curt Arnold apache.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #1 from Curt Arnold apache.org> 2008-10-03 06:15:52 PST --- Please look at EnhancedPatternLayout in the extras companion. That is a back port of the PatternLayout from the abandoned log4j 1.3 development and supports user supplied conversion patterns and see if it does what you are wanting to do. If not, please describe what you want to do more concretely.

DO NOT REPLY [Bug 45941] New: Custom PatternLayout

2008-10-03T09:58:05

https://issues.apache.org/bugzilla/show_bug.cgi?id=45941 Summary: Custom PatternLayout Product: Log4j Version: unspecified Platform: PC URL: http://logging.apache.org/log4j/1.2/apidocs/org/apache/l og4j/PatternLayout.html OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Layout AssignedTo: log4j-dev< at >logging.apache.org ReportedBy: spamadore< at >gmail.com For the moment, you can only use predefined patternLayout here http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html An evolution could be to add a system to define our own layout basically a custom layout could be --------------------------------------------------------- public class MyPidLayout implements CustomConversionLayout{ char getConversionCharacter(){ return 'y'; } String getConversionValue(){ return properties.getProperty("Pid")); } } ---------------------------------------------------------- André Bergues

DO NOT REPLY [Bug 45939] New: Cannot drop HierarchyDynamicMBean from LoggerRepository

2008-10-02T16:43:58

https://issues.apache.org/bugzilla/show_bug.cgi?id=45939 Summary: Cannot drop HierarchyDynamicMBean from LoggerRepository Product: Log4j Version: 1.2 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Other AssignedTo: log4j-dev< at >logging.apache.org ReportedBy: hmak< at >vaultus.com HierarchyDynamicMBean registered too many times w/ LoggerRepository. This can occur when: 1. start MBeanServer 2. register new HierarchyDynamicMBean (HDMBean) to MBeanServer 3. unregister HDMBean from MBeanServer 4. stop MBeanServer 5. repeat (1) - (3) LoggerReposity will still broadcast to old HDMBean [in addition to new HDMBean]. There is no API to unregister the MBean.

DO NOT REPLY [Bug 45934] FileAppender should use virtual-machine shutdown hook that flushes buffer automatically

2008-10-02T11:51:20

https://issues.apache.org/bugzilla/show_bug.cgi?id=45934 --- Comment #1 from Martin Burger rtin-burger.de> 2008-10-02 04:51:20 PST --- Created an attachment (id=22667) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22667) Patch to FileAppender.java that produces implementation of proposed feature. The attached patch implements the proposed feature using a shutdown thread. It adds a new optional option "ShutdownHook" (default: false). If this option is set to true and option "BufferedIO" is set to true as well, the shutdown hook will be registered in method setFile(...). Note: The test suite runs without any error after applying the patch, at least on my system.

DO NOT REPLY [Bug 45934] New: FileAppender should use virtual-machine shutdown hook that flushes buffer automatically

2008-10-02T11:40:57

https://issues.apache.org/bugzilla/show_bug.cgi?id=45934 Summary: FileAppender should use virtual-machine shutdown hook that flushes buffer automatically Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Appender AssignedTo: log4j-dev< at >logging.apache.org ReportedBy: m< at >rtin-burger.de If org.apache.log4j.FileAppender buffers output (option BufferedIO set to true), then the underlying WriterAppender's field immediateFlush will set to false. So, the FileAppender will skip flushing and it is very likely that the last few log events will not be recorded on disk when the application exits. To avoid the loss of these events, an optional virtual-machine shutdown that flushes automatically at the end should be used.

DO NOT REPLY [Bug 45932] New: Log4j JMX MBeans not cleaned up

2008-10-01T20:43:01

https://issues.apache.org/bugzilla/show_bug.cgi?id=45932 Summary: Log4j JMX MBeans not cleaned up Product: Log4j Version: 1.2 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Other AssignedTo: log4j-dev< at >logging.apache.org ReportedBy: hmak< at >vaultus.com LogManager.resetConfiguration() does not drop the JMX MBeans created by HierarchyDynamicMBean. When executed twice, the following MBeanServer mbs = ...; Properties props = ...; HierarchyDynamicMBean hdm = new HierarchyDynamicMBean(); mbs.registerMBean(hdm, new ObjectName("log4j:hiearchy=default")); Enumeration iter = (Enumeration) LogManager.getLoggerRepository().getCurrentLoggers(); while (iter.hasMoreElements()) { hdm.addLoggerMBean(iter .nextElement() .getName()); } LogManager.resetConfiguration(); PropertyConfigurator.configure(props); throws org.apache.log4j.jmx.LoggerDynamicMBean Could not add appenderMBean for [F]. javax.management.InstanceAlreadyExistsException: log4j:appender=F at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:452) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1410) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:936) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:337) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:497) at org.apache.log4j.jmx.LoggerDynamicMBean.registerAppenderMBean(Unknown Source) at org.apache.log4j.jmx.LoggerDynamicMBean.handleNotification(Unknown Source) at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221) at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184) at org.apache.log4j.jmx.HierarchyDynamicMBean.addAppenderEvent(Unknown Source) at org.apache.log4j.Hierarchy.fireAddAppenderEvent(Hierarchy.java:192) at org.apache.log4j.Category.addAppender(Category.java:162) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:614) at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415) at org.apache.log4j.PropertyConfigurator.configure(PropertyConfigurator.java:349) ...

DO NOT REPLY [Bug 45704] Failed to load logging.xml for JRE 1.5.0_16 and Webstart

2008-10-01T14:16:31

https://issues.apache.org/bugzilla/show_bug.cgi?id=45704 --- Comment #4 from Nick Ebbutt ebbutt.net> 2008-10-01 07:16:31 PST --- There is now a bug report relating to this issue on Sun's site http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6753651

DO NOT REPLY [Bug 45915] New: DeadLock occured in AsyncAppender

2008-09-30T09:31:25

https://issues.apache.org/bugzilla/show_bug.cgi?id=45915 Summary: DeadLock occured in AsyncAppender Product: Log4j Version: 1.2 Platform: HP OS/Version: HP-UX Status: NEW Severity: critical Priority: P2 Component: Appender AssignedTo: log4j-dev< at >logging.apache.org ReportedBy: keiichi.fujito< at >hp.com Unfortunately, our system which uses log4j 1.2.15. encountered the same bug that was reported in Bug#: 38137 Comment #16. This bug seems not to be discussed for the final fix for several months… Is this bug going to fix in near future? Here is the thread dump: Found one Java-level deadlock: ============================= "Thread-1": waiting to lock monitor 6000000000587e40 (object 9fffffffcb409a68, a java.util.ArrayList), which is held by "pool-1-thread-41460" "pool-1-thread-41460": waiting to lock monitor 6000000000588230 (object 9fffffffcb4d9b28, a org.apache.log4j.spi.RootLogger), which is held by "Thread-1" Java stack information for the threads listed above: =================================================== "Thread-1": at org.apache.log4j.AsyncAppender.append(AsyncAppender.java:163) - waiting to lock <9fffffffcb409a68> (a java.util.ArrayList) at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251) - locked <9fffffffcb409ac0> (a org.apache.log4j.AsyncAppender) at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66) at org.apache.log4j.Category.callAppenders(Category.java:206) - locked <9fffffffcb4d9b28> (a org.apache.log4j.spi.RootLogger) at org.apache.log4j.Category.forcedLog(Category.java:391) at org.apache.log4j.Category.log(Category.java:856) at kid.bs.common.log.KidLogger.log(KidLogger.java:429) at kid.bs.common.log.KidLogger.log(KidLogger.java:351) at kid.bs.job.KidExecuter.run(KidExecuter.java:1128) at java.lang.Thread.run(Thread.java:595) "pool-1-thread-41460": at org.apache.log4j.Category.callAppenders(Category.java:204) - waiting to lock <9fffffffcb4d9b28> (a org.apache.log4j.spi.RootLogger) at org.apache.log4j.Category.forcedLog(Category.java:391) at org.apache.log4j.Category.log(Category.java:856) at kid.bs.common.log.KidLogger.info(KidLogger.java:142) at kid.sr.batch.LoadingDaily.action(LoadingDaily.java:2111) - locked <9fffffffcbee6e28> (a java.lang.String) at kid.bs.job.thread.KidActionThread.newActionClass(KidActionThread.java:429) at kid.bs.job.thread.KidActionThread.jobExecute(KidActionThread.java:149) at kid.bs.job.thread.KidActionThread.run(KidActionThread.java:83) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) Found 1 deadlock.

DO NOT REPLY [Bug 44219] 'WARNING' for a log level is silently ignored/changed to DEBUG

2008-09-29T16:46:20

https://issues.apache.org/bugzilla/show_bug.cgi?id=44219 Maxx free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maxxyme< at >free.fr

DO NOT REPLY [Bug 45704] Failed to load logging.xml for JRE 1.5.0_16 and Webstart

2008-09-29T09:26:46

https://issues.apache.org/bugzilla/show_bug.cgi?id=45704 --- Comment #3 from Nick Ebbutt ebbutt.net> 2008-09-29 02:26:46 PST --- Good observation, I didn't spot that. It looks like it will make this bug a fair bit more difficult to fix. There is no convenient method on DocumentBuilder to pass a URL instance in directly. I wonder if creating a relative URL based on the URL instance you get under webstart would even work, given how broken the webstart URL instance seems. The fix I suggested does at least appear to make things work if there is a self-contained config.xml, which I am guessing is probably the majority of cases, but it would be good to find a perfect solution to this. Right now the best workaround I can think of is to take the xml config out of the jar, and make it available via http so it can be downloaded from the web app codebase. This could have advantages anyway, since that way to change the logging config you don't have to rebuild the jars, just change the log.xml on the server. I guess a fair few apps might do it this way already

Bug report for Log4j [2008/09/28]

2008-09-29T06:08:16

+---------------------------------------------------------------------------+ | Bugzilla Bug ID | | +---------------------------------------------------------------------+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned | | | OPN=Reopened VER=Verified (Skipped Closed/Resolved) | | | +-----------------------------------------------------------------+ | | | Severity: BLK=Blocker CRI=Critical REG=Regression MAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement TRV=Trivial | | | | +-------------------------------------------------------------+ | | | | Date Posted | | | | | +--------------------------------------------------+ | | | | | Description | | | | | | | |13099|Opn|Nor|2002-09-27|DOMConfigurator ignores category factory setting | |17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads | |20395|Inf|Enh|2003-06-01|PreparedStatementAppender Enhancement | |23329|Ass|Enh|2003-09-22| element in XML config should support reso| |25355|Ass|Enh|2003-12-09|allow to require "TLS/SSL only" for outgoing mails| |26084|Inf|Nor|2004-01-13|Log Event detail panel does not show special chara| |27363|Inf|Enh|2004-03-02|JNI based SyslogAppender | |27367|Inf|Enh|2004-03-02|NetSendAppender | |28647|Ass|Enh|2004-04-28|Add "Flush on Level" capability to FileAppender | |29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM| |29304|New|Nor|2004-05-30|Starting XMLSocketAppender from config file | |29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe| |29735|New|Nor|2004-06-22|Receiver list display error when receiver has no | |30055|New|Nor|2004-07-12|Problem with registering Appenders with the same n| |30407|Inf|Maj|2004-07-30|Externally rolled file problem | |30888|New|Maj|2004-08-27|Chainsaw mixes files in same panel | |30890|New|Min|2004-08-27|Newly opened log file should get focus | |30892|New|Min|2004-08-27|Log files cannot be closed | |31089|New|Nor|2004-09-07|Does not accept ISO8601 dates in focus field | |31178|Inf|Cri|2004-09-11|Exception using Chainsaw for simple debugging | |31179|Ass|Enh|2004-09-11|Implement Chainsaw as Eclipse stand-alone applicat| |33278|New|Min|2005-01-27|NPE thrown durring daily log file rollover | |33493|Inf|Enh|2005-02-10|contribution to log4j: servlet diagnostic context | |33717|New|Nor|2005-02-23|Leaving out %throwable in ConversionPattern adds t| |34440|New|Nor|2005-04-13|sandbox:IMAppender - comma-seperated recipient lis| |34491|Ver|Nor|2005-04-18|Missing include in build.jms target results in mis| |34651|New|Enh|2005-04-27|allow for a header on top of every rolled file | |34738|New|Nor|2005-05-04|Chainsaw does not remember what Columns are select| |34945|Inf|Nor|2005-05-17|ThrowableInformation has dubious Stack Trace extra| |34974|Inf|Cri|2005-05-19|Exception when running a Pluglet | |35180|New|Min|2005-06-02|Multiple lines "XML files (*.xml)" in drop down li| |35239|Inf|Nor|2005-06-06|NullPointerException when saving displayed events | |35563|Inf|Enh|2005-06-30|Syslog appender parametrability | |35996|Inf|Enh|2005-08-03|Add support for ant-like in log4j.xml | |36435|New|Enh|2005-08-31|Log4J RollingFileAppender under OpenVMS does not f| |36654|Inf|Min|2005-09-14|Provide better error messages for "Please initiali| |36789|Inf|Nor|2005-09-23|Empty control flow statement in org.apache.log4j.l| |36860|New|Enh|2005-09-29|[jmx] Add ability to create a logger MBean for a n| |37349|Ass|Nor|2005-11-03|DBAppender not working with jTDS driver | |37638|New|Nor|2005-11-25|logging doesn't fall back with FallbackErrorHandle| |37734|Inf|Nor|2005-12-01|Customize Event ID and Event Category with NTEVent| |37762|Ass|Enh|2005-12-02|RSSAppender or other approach. | |38061|New|Nor|2005-12-28|Problem configuring an errorHandler using a proper| |38363|Ass|Nor|2006-01-24|SecurityException during log output | |38394|Ver|Enh|2006-01-26|PropertySetter fails to print stacktrace if error | |38395|Ver|Reg|2006-01-26|Unable to set threshold on appender via config fil| |38406|Ver|Nor|2006-01-26|jdk1.4 dependencies in log4j 1.3 alpha | |38513|New|Nor|2006-02-05|[PATCH] Suggested unit test for JMSAppender | |38582|Ass|Nor|2006-02-08|Chainsaw does not include Receiver JavaDoc in dist| |38590|Inf|Nor|2006-02-09|no space on device fails another instance | |38883|Opn|Nor|2006-03-07|LogFilePatternReceiver fails to process multi-line| |38884|New|Nor|2006-03-07|null pointer exception displaying logs if number o| |39690|Inf|Cri|2006-05-31|Initialization fail in J2EE Environment | |39691|Ass|Nor|2006-05-31|DBAppender doesn't log long events | |40068|New|Nor|2006-07-18|Add support for attach-on-demand API to chainsaw | |40124|New|Min|2006-07-27|startup (JWS) does not initialize ignored elements| |40251|Opn|Min|2006-08-14|Hard coded JMX domain name for MBean instances | |40382|Inf|Maj|2006-09-01|Sysappender hangs during boot time on HP | |40385|Inf|Maj|2006-09-01|SocketServer cannot find config file when passed a| |40472|New|Nor|2006-09-11|SettingsManager calls loadSettings with global set| |40533|New|Nor|2006-09-18|Chainsaw not showing all logging statements | |40570|Inf|Blk|2006-09-21|RollingFileAppender does not rollover when the fil| |40611|New|Trv|2006-09-27|Bad subclass example; NullPointerException in Logg| |40736|Inf|Nor|2006-10-11|log4j delete permission denied | |40889|Inf|Nor|2006-11-03|repeated entries in log after failure | |40990|Inf|Nor|2006-11-17|Cannot bind port or ip address for outgoing UDP so| |41006|Inf|Enh|2006-11-20|Contributing XMLSocketHubReceiver | |41214|Ass|Maj|2006-12-19|Deadlock with RollingFileAppender | |41311|Inf|Min|2007-01-06|Please make TimeBasedRollingPolicy non-final? | |41316|New|Nor|2007-01-08|NPE when using RollingFileAppender in Tomcat. | |41547|Inf|Nor|2007-02-05|PropertyConfigurator and layout.contentType | |41799|New|Enh|2007-03-09|SyslogAppender should enable to customize Log4j.Le| |41882|Inf|Nor|2007-03-18|IE7 problems with Log4J web site | |41937|New|Nor|2007-03-23|Logs from some panels missing in custom expression| |41980|Inf|Maj|2007-03-29|Log4j stop updating log file- version log4j-1.2.8 | |42171|New|Nor|2007-04-19|SocketHubReceiver duplicates messages | |42189|Ass|Nor|2007-04-22|Add simple bridge for java.util.logging, with basi| |42516|Inf|Nor|2007-05-24|Log4j failed to log file when packaged in Eclipse | |42664|New|Enh|2007-06-14|JUL Appender | |42842|Opn|Nor|2007-07-09|Create a PUBLIC identifier for the log4j DTD | |42883|Opn|Nor|2007-07-12|'Welcome' and 'Drag & Drop' panels can't be hidden| |42933|Inf|Maj|2007-07-18|IllegalStateException thrown from FileAppender.clo| |43061|Opn|Enh|2007-08-08|Flush appender regularty | |43148|Ass|Nor|2007-08-16|LogFilePatternReceiver depends on jakarta-oro, cou| |43277|New|Nor|2007-08-31|Add LogMF.entering, .exiting and .throwing methods| |43282|Ass|Nor|2007-08-31|Add OSGi packaging info to log4j and companions | |43313|Inf|Nor|2007-09-05|log4j 1.2.16 release considerations and discussion| |43403|Inf|Nor|2007-09-16|PatternLayout: new format modifer: prefix if non-e| |43619|New|Enh|2007-10-13|Simple proposal for pluggable sys-props resolvers | |43637|Inf|Nor|2007-10-16|SocketAppender.append(LoggingEvent) calls the Erro| |43728|Inf|Cri|2007-10-29|Log file loss when specified file is locked by ano| |43736|Ass|Nor|2007-10-30|Chainsaw does not honor encoding when loading XML | |43820|New|Enh|2007-11-08|[PATCH] Layered Configurator Patch | |43879|Inf|Nor|2007-11-16|FileAppender writes Header multiple times | |43911|Inf|Nor|2007-11-20|logfiles not getting rolled over with RollingFileA| |43923|Inf|Min|2007-11-21|JBOSS specific information in javadocs | |44038|Inf|Cri|2007-12-07|log4j is susceptible to exceptions thrown by Excep| |44219|Inf|Nor|2008-01-13|'WARNING' for a log level is silently ignored/chan| |44308|Inf|Enh|2008-01-28|[Patch] JMX component for managing Logger configur| |44357|New|Enh|2008-02-05|List of property keys | |44370|Inf|Reg|2008-02-06|MANIFEST.MF broken in log4j-1.2.15.jar | |44386|Opn|Nor|2008-02-10|NTEventLogAppender.dll for windows 64 | |44526|Inf|Nor|2008-03-04|segmentation fault occuring when PropertyConfigura| |44557|Inf|Nor|2008-03-07|no close call to Appender after replacing the root| |44644|New|Nor|2008-03-20|Default ContentType for Layout is text/html which | |44649|Inf|Nor|2008-03-20|JMS Hangs when a Root Appender | |44700|Inf|Nor|2008-03-28|Log4J locks rolled log files | |44727|Inf|Nor|2008-04-01|Add missing Logger#isErrorEnabled and isWarningEna| |44834|Inf|Nor|2008-04-17|SimpleSocketServer looses buffered logs, produces | |44839|Inf|Nor|2008-04-17|SyslogAppender logging to a UNIX domain socket | |44932|New|Enh|2008-05-05|improve DailyRollingFileAppender handling of rotat| |44934|Inf|Enh|2008-05-05|add helper method to DailyRollingFileAppender to g| |44945|New|Nor|2008-05-06|SyslogAppender not working | |45029|Ass|Nor|2008-05-18|Additional unit tests for Filters in extras compan| |45042|New|Nor|2008-05-19|Need a reliable way to detect misconfiguration | |45068|New|Enh|2008-05-22|Ability to copy contents from log-entries | |45109|New|Nor|2008-05-31|SMTPAppender uses wrong property for mail server | |45165|Ass|Enh|2008-06-09|Multifile Appender | |45224|Inf|Nor|2008-06-17|Log 4j giving nullpointer when reloading applicat| |45231|Inf|Nor|2008-06-18|Clear appenders call on logger calls a helper whic| |45236|Inf|Cri|2008-06-19|Wriring output to an out-dated file. | |45304|New|Nor|2008-06-29|using log4j with OAS for some reasone all the logg| |45305|Inf|Nor|2008-06-29|using log4j with OAS for some reasone all the logg| |45375|New|Enh|2008-07-10|Building log4j core without manually installing li| |45481|New|Trv|2008-07-25|Source contains unused imports | |45482|Inf|Min|2008-07-25|Source contains unused variables | |45493|New|Maj|2008-07-28|Log4j file getting overwritten | |45629|New|Nor|2008-08-13|TopicConnection is not closed | |45660|New|Enh|2008-08-20|NDC could remove Hashtable entry if Stack gets emp| |45704|New|Maj|2008-08-28|Failed to load logging.xml for JRE 1.5.0_16 and We| |45753|New|Nor|2008-09-06|Code contribution | |45781|New|Nor|2008-09-11|RollingFileAppender under Windows does not rotate | |45782|New|Enh|2008-09-11|Add a new appender that zip's rolled files | |45855|New|Enh|2008-09-21|Add site/apt documentation for JULBridgeLogManager| +-----+---+---+----------+--------------------------------------------------+ | Total 134 bugs | +---------------------------------------------------------------------------+

DO NOT REPLY [Bug 45704] Failed to load logging.xml for JRE 1.5.0_16 and Webstart

2008-09-26T23:45:05

https://issues.apache.org/bugzilla/show_bug.cgi?id=45704 --- Comment #2 from Curt Arnold apache.org> 2008-09-26 16:45:04 PST --- Passing the stream instead of the URL would result in relative URL's in entity references not properly resolving. That is if you had a configuration file that looked like: ]> &A1; if you only passed the stream, the parser would not know where to locate A1.xml. If you passed a URL or a InputSource, then the parser would know how the resolve A1.xml. Will have to look through the code, but it would seem the answer would be to pass the URL down through the stack instead of trying to convert the URL to a string and then back.

DO NOT REPLY [Bug 45704] Failed to load logging.xml for JRE 1.5.0_16 and Webstart

2008-09-26T20:43:13

https://issues.apache.org/bugzilla/show_bug.cgi?id=45704 Nick Ebbutt ebbutt.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nick< at >ebbutt.net --- Comment #1 from Nick Ebbutt ebbutt.net> 2008-09-26 13:43:12 PST --- I think this can be solved just by modifying line 762 in DOMConfigurator, in the method public void doConfigure(final URL url, LoggerRepository repository) Instead of parser.parse(url.toString()) it seems to work OK if we use parser.parse(url.openConnection().getInputStream()). The reason is that the url obtained via URL.toString() was broken for webstart apps in a jdk security patch for 1.5.0_16 and 1.6_07, to obscure the path to jar files in the webstart cache. openConnection still works I built a patch with this fix and it seemed to work OK for our webstart apps See my blog for more details, http://www.objectdefinitions.com/odblog/2008/fix-for-log4j-bug-45704-failed-to-load-loggingxml-for-jre-150_16-and-webstart/ Nick

DO NOT REPLY [Bug 45896] Classloader problem when logging event (tomcat)

2008-09-26T16:12:44

https://issues.apache.org/bugzilla/show_bug.cgi?id=45896 jreeman gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #2 from jreeman gmail.com> 2008-09-26 09:12:44 PST --- oki the problem is not from log4j. I invalid this issue.

DO NOT REPLY [Bug 45896] Classloader problem when logging event (tomcat)

2008-09-26T11:13:06

https://issues.apache.org/bugzilla/show_bug.cgi?id=45896 --- Comment #1 from jreeman gmail.com> 2008-09-26 04:13:06 PST --- If you need some, don't hesitate to ask me more detailed informations on how reproduce the crash.

DO NOT REPLY [Bug 45896] New: Classloader problem when logging event (tomcat)

2008-09-26T11:09:38

https://issues.apache.org/bugzilla/show_bug.cgi?id=45896 Summary: Classloader problem when logging event (tomcat) Product: Log4j Version: 1.2 Platform: PC OS/Version: Linux Status: NEW Severity: blocker Priority: P1 Component: Other AssignedTo: log4j-dev< at >logging.apache.org ReportedBy: mimounl< at >gmail.com When using jboss cache and jgroups library I have this error in my logs : Sep 25, 2008 7:50:36 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive ROOT.war Sep 25, 2008 7:55:33 PM org.apache.catalina.startup.HostConfig checkResources INFO: Undeploying context [] Sep 25, 2008 7:55:33 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive ROOT.war Sep 25, 2008 7:55:34 PM org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load java.io.PrintWriter. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1246) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1206) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.apache.log4j.spi.LoggingEvent.(LoggingEvent.java:154) at org.apache.log4j.Category.forcedLog(Category.java:388) at org.apache.log4j.Category.log(Category.java:853) at org.apache.commons.logging.impl.Log4JLogger.error(Log4JLogger.java:193) at org.jgroups.protocols.MPING.run(MPING.java:362) at java.lang.Thread.run(Thread.java:619) Sep 25, 2008 7:55:34 PM org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.log4j.spi.VectorWriter. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1246) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1206) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.apache.log4j.spi.LoggingEvent.(LoggingEvent.java:154) at org.apache.log4j.Category.forcedLog(Category.java:388) at org.apache.log4j.Category.log(Category.java:853) at org.apache.commons.logging.impl.Log4JLogger.error(Log4JLogger.java:193) at org.jgroups.protocols.MPING.run(MPING.java:362) at java.lang.Thread.run(Thread.java:619) Sep 25, 2008 7:55:34 PM org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.log4j.spi.VectorWriter. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1246) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1206) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.apache.log4j.spi.LoggingEvent.(LoggingEvent.java:154) at org.apache.log4j.Category.forcedLog(Category.java:388) at org.apache.log4j.Category.log(Category.java:853) at org.apache.commons.logging.impl.Log4JLogger.error(Log4JLogger.java:193) at org.jgroups.protocols.Discovery$PingSenderTask$1.run(Discovery.java:389) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Sep 25, 2008 7:55:36 PM org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.log4j.spi.VectorWriter. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. I also add the issue in the jgroups bug tracker and they said that it's a log4j problem : https://jira.jboss.org/jira/browse/JGRP-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12431338 They recommand to put log4j and jgroups in the tomcat/lib directory but it's very annoying to that because until now all the library management was centralized in the webapp itself, this way it was easy to upgrade library version etc... I tried to migrate the log4j version to 1.2.15 in my pom.xml but it's doesn't work. I saw here that some people are the same migration problem : http://yoavs.blogspot.com/2008/05/caution-log4j-1215-brings-in-bunch-of.html and decided to continue to use the 1.2.14 version.

DO NOT REPLY [Bug 45886] SysLog Appender does not take in to account Identity

2008-09-25T10:22:01

https://issues.apache.org/bugzilla/show_bug.cgi?id=45886 Juan Amiguet gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID --- Comment #3 from Juan Amiguet gmail.com> 2008-09-25 03:22:01 PST --- Enhancement not needed, same result can be obtained by configuration. The solution proposed to append the identity to the pattern and then switch off the facility logging works. A sample configuration then is. # Syslog is set to be a SyslogAppender. log4j.appender.Syslog=org.apache.log4j.net.SyslogAppender # Syslog uses PatternLayout. log4j.appender.Syslog.layout=org.apache.log4j.PatternLayout log4j.appender.Syslog.layout.ConversionPattern=: %-5p %c{2} [%t,%M:%L] %m%n # Set Syslog properties. log4j.appender.Syslog.SyslogHost=localhost log4j.appender.Syslog.Facility=LOCAL3 #Facility printing must be set to off to avoid the Identity from ending up in the message body. log4j.appender.Syslog.FacilityPrinting=false

DO NOT REPLY [Bug 45886] SysLog Appender does not take in to account Identity

2008-09-25T10:07:01

DO NOT REPLY [Bug 45886] SysLog Appender does not take in to account Identity

2008-09-25T09:30:34

https://issues.apache.org/bugzilla/show_bug.cgi?id=45886 Curt Arnold apache.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #1 from Curt Arnold apache.org> 2008-09-25 02:30:34 PST --- A reference would be great for this. I don't think it is in the IETF RFC's and a web search for "syslog identity" didn't come up with any obvious matches. Is the identity transmitted in the message packet? If so, could the desired objective be accomplished by adding the identity into a pattern layout?