http://blog.gmane.org/gmane.comp.jakarta.log4j.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20558 <pre>Hi, my first OSS patch ever ;-) Tomek --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe&lt; at &gt;logging.apache.org For additional commands, e-mail: log4j-dev-help&lt; at &gt;logging.apache.org</pre> Tomek Kaczynski 2013-05-17T11:44:51 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20518 <pre>Right now we have, as seen in M3 output: [INFO] Apache Log4j 2 [INFO] Apache Log4j API [INFO] Apache Log4J Core [INFO] Apache Log4j 1.x Compatibility API [INFO] Apache Log4j SLF4J Binding [INFO] Apache Log4j to SLF4J Adapter [INFO] Apache Log4j Commons Logging Bridge [INFO] Apache Log4j Flume NG Bridge [INFO] Apache Log4j Web Adapters [INFO] Apache Log4j Tag Library [INFO] Apache Log4J JMX GUI [INFO] log4j-samples [INFO] flume-common [INFO] flume-remote [INFO] flume-embedded The last four should be renamed, which means changing the artifact IDs, to match the log4j prefix. I ran into some odd problems when I tried to do that and gave up. Gary </pre> Gary Gregory 2013-05-16T17:31:21 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20487 <pre>Hi, https://issues.apache.org/bugzilla/show_bug.cgi?id=45753 it has a BurstFilter for companions, but later I saw some comments by Ralph it arrived in log4j 2. So I think we should close this issue and refer people to log4j 2 in this case. Any objections? Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de </pre> Christian Grobmeier 2013-05-16T09:47:08 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20479 <pre>Hi all, just made a snapshot for the upcoming log4j extras 1.2.17 release which I plan to start soon. https://repository.apache.org/content/repositories/snapshots/log4j/apache-log4j-extras/1.2.17-SNAPSHOT/ Most important I fixed the duplicate classes issue. Maybe Jess, if you are reading this, can you confirm your problems are solved? Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de </pre> Christian Grobmeier 2013-05-16T09:00:45 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20450 <pre>Guys, Background: Since I'm the lead developer on a Jackson Mapper module (https://github.com/FasterXML/jackson-datatype-jsr310), I'm actively involved on their development mailing list. Jackson 1.9 is, well, old. Specifically, 1.9.0 is two years old. 1.9 is the last minor version of the 1.x family. There will continue to be bug fixe releases—for now—about every 4-6 months. The last patch release was in January. Jackson 2.x is the current version with rapid release periods. 2.0 Is about a year old, 2.1 was released in October and 2.2 was released last month. Only major bugs will be fixed in 1.9.x. Minor bug fixes and all new features will go in 2.x. Jackson 1.x and 2.x use different Java packages. This has both advantages and disadvantages. One advantage is that frameworks and libraries, like Spring Framework, can easily support both versions because they can coexist on the same class path during compilation and testing. One disadvantage is that if some library is using 1.x and some other library is using 2.x and you create an application that depends on both libraries, you'll have to pull BOTH versions of Jackson on to your class path. Ugh. Log4j 2 is "brand new" (it's not even released yet). Typically, I would argue that new projects should not use old versions of their dependencies. In Log4j 2's case, I tend to lean the same direction. It doesn't seem wise to tie ourselves to Jackson 1.x so late in its life when Jackson 2.x is already mature and Log4j 2 isn't even released yet. As a Java 8, Spring 4, Jackson 2 user, I know I wouldn't love having to also have Jackson 1 on my class path (if I were using JSON configuration). I would suggest that we should either support both or we should only support 2.x, but only supporting 1.x feels wrong to me. Supporting both wouldn't be a major challenge. The way Spring does it is to have two Jackson* classes and Jackson2* classes with identical APIs. Depending on which version you are already using, you use the appropriate class. In this case, I would approach it like this: - Rename JSONConfiguration to Jackson1JSONConfiguration, and (using CheckStyle's import control) ensure that only this class imports Jackson 1.x - Create a similar class named Jackson2JSONConfiguration, and ensure that only this class imports Jackson 2.x - Alter JSONConfigurationFactory to detect which version is on the class path and return the appropriate JSON configuration, preferring 2.x if both are on the class path Thoughts?</pre> Nick Williams 2013-05-15T18:00:17 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20422 <pre>Hi, we have had Apache Companions Extras. Now we don't have subcomponents. What is the new name now? Is it log4j extras or is it log4j companions? I am asking because we need a location for the website and I would like to fix the docs from the website. Basically I have a slight tendency to log4j extras 1.2.17 (note new version naming too) Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de </pre> Christian Grobmeier 2013-05-15T11:00:28 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20418 <pre>https://issues.apache.org/bugzilla/show_bug.cgi?id=54975 Bug ID: 54975 Summary: File size is not reset if delete a content of the log file Product: Log4j Version: 1.2.17 Hardware: PC Status: NEW Severity: normal Priority: P2 Component: Other Assignee: log4j-dev&lt; at &gt;logging.apache.org Reporter: vadyans&lt; at &gt;gmail.com Classification: Unclassified If I delete all content of the log file and save the result, file size is not reset to "0" and there is a NULL string in a log. This issue occurs intermittently. </pre> bugzilla< at >apache.org 2013-05-15T09:50:25 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20407 <pre>FYI to whomever has time to fix this: [WARNING] Javadoc Warnings [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\AbstractLogEventWrapperEntity.java:58: warning - Tag &lt; at &gt;link: reference not found: ThreadContext.ContextStack [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\AbstractLogEventWrapperEntity.java:90: warning - Tag &lt; at &gt;link:illegal character: "64" in "&lt; at &gt;Transient" [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\AbstractLogEventWrapperEntity.java:229: warning - Tag &lt; at &gt;link:illegal character: "64" in "&lt; at &gt;Transient" [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\AbstractLogEventWrapperEntity.java:212: warning - Tag &lt; at &gt;link:illegal character: "64" in "&lt; at &gt;Transient" [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\AbstractLogEventWrapperEntity.java:90: warning - Tag &lt; at &gt;link: reference not found: &lt; at &gt;Transient [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\AbstractLogEventWrapperEntity.java:212: warning - Tag &lt; at &gt;link: reference not found: &lt; at &gt;Transient [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\AbstractLogEventWrapperEntity.java:229: warning - Tag &lt; at &gt;link: reference not found: &lt; at &gt;Transient [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\converter\ContextStackAttributeConverter.java:32: warning - Tag &lt; at &gt;link: reference not found: ThreadContext.ContextStack [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\converter\ContextStackJsonAttributeConverter.java:34: warning - Tag &lt; at &gt;link: reference not found: ThreadContext.ContextStack [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\nosql\NoSQLConnection.java:70: warning - Tag &lt; at &gt;link: reference not found: true [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\nosql\NoSQLConnection.java:70: warning - Tag &lt; at &gt;link: reference not found: true [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\nosql\NoSQLConnection.java:70: warning - Tag &lt; at &gt;link: reference not found: true [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\converter\ContextStackAttributeConverter.java:32: warning - Tag &lt; at &gt;link: reference not found: ThreadContext.ContextStack [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\converter\ContextStackJsonAttributeConverter.java:34: warning - Tag &lt; at &gt;link: reference not found: ThreadContext.ContextStack [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\converter\package-info.java:25: warning - Tag &lt; at &gt;link: reference not found: ContextMapAttributeConverter [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\converter\package-info.java:25: warning - Tag &lt; at &gt;link: reference not found: ContextStackAttributeConverter [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\converter\package-info.java:25: warning - Tag &lt; at &gt;link: reference not found: ContextMapJsonAttributeConverter [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\converter\package-info.java:25: warning - Tag &lt; at &gt;link: reference not found: ContextStackJsonAttributeConverter [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\nosql\package-info.java:31: warning - Tag &lt; at &gt;link: reference not found: NoSQLObject [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\nosql\package-info.java:31: warning - Tag &lt; at &gt;link: reference not found: NoSQLConnection [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\nosql\package-info.java:31: warning - Tag &lt; at &gt;link: reference not found: NoSQLProvider [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\converter\ContextStackAttributeConverter.java:32: warning - Tag &lt; at &gt;link: reference not found: ThreadContext.ContextStack [WARNING] C:\svn\org\apache\log4j2\trunk\core\src\main\java\org\apache\logging\log4j\core\appender\db\jpa\converter\ContextStackJsonAttributeConverter.java:34: warning - Tag &lt; at &gt;link: reference not found: ThreadContext.ContextStack Gary </pre> Gary Gregory 2013-05-15T02:07:49 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20397 <pre>Since I'm now a committer I have an &lt; at &gt;apache.org address. Since it's a forwarding address, I'm having it forward to my Google Apps email address (the address I'm sending from now). I'd like to subscribe to the list with my &lt; at &gt;apache.org address. I've set up my &lt; at &gt;apache.org address as an additional "From" address in GMail. If I send an email from GMail to my $work address and select my &lt; at &gt;apache.org address is my from address, it shows up as "from" my &lt; at &gt;apache.org address when I receive the email on the other end. But when I tried to subscribe by sending an email from my &lt; at &gt;apache.org address to log4j-dev-subscribe&lt; at &gt;logging.apache.org, it replied that my GMail address was already subscribed. Does anyone have any experience with this? How do you subscribe your &lt; at &gt;apache.org addresses? Nick</pre> Nick Williams 2013-05-14T22:38:43 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20393 <pre>I created LOG4J2-10 as one of the first requirements I had for Log4j 2. OSGi support is very important in some environments. In fact, it is an area that I have wanted to explore in my own operational environment. As part of a side project at work I found a product called Paremus Service Fabric [1] which is essentially an OSGi service container. In discussing the product with the folks at Paremus I mentioned my desire to have better OSGi support in Log4j 2 and asked them if they could help since it at that time (and I think it is still true) we had very little OSGi expertise on the Log4j 2 team. They told me they would see what they could do. Well recently Tim Ward has started taking a look at what we are doing. Tim works for Paremus and has been recently working with the Hibernate team to help them achieve similar goals. Tim is also a committer and PMC member on Apache Aries and is the co-author of Enterprise OSGi in Action. I wanted to give Tim this introduction so that you will understand that I asked for his help and am grateful that he has taken the time to lend us a hand. As such I plan to look at the patches he provides from the perspective of what would be best for our OSGi users. At the same time we also need to not lose focus on what is best for our non-OSGi users. This may make the build and release more complicated but I really think we need to make sure the needs of both of these user sets are being met. Ralph [1] http://www.paremus.com</pre> Ralph Goers 2013-05-14T18:57:11 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20357 <pre>The PMD inspector says the following if statement contains "Useless parentheses." if ((isEventTimestamp &amp;&amp; isLiteralValue) || (isEventTimestamp &amp;&amp; isPattern) || (isLiteralValue &amp;&amp; isPattern)) { LOGGER.error("The pattern, literal, and isEventTimestamp attributes are mutually exclusive."); return null; } I'm all for removing useless parentheses; unfortunately, I don't see how these are useless. The way I see it, if isLiteralValue is false, with parentheses it will (correctly) continue to evaluate after the first grouped condition but without parentheses it would (incorrectly) short circuit after the first use of isLiteralValue. Am I missing something here? Or is this a PMD bug? Nick</pre> Nick Williams 2013-05-13T15:09:15 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20355 <pre>Hi, All Because of a bug already reported by me (LOG4J2-246&lt;https://issues.apache.org/jira/browse/LOG4J2-246&gt;), I had to write an Appender containing a fix/workaround. Obvious approach for me would be inherittance from AbstractOutputStreamAppender and overriding method append. However I couldn't do that because: manager.write(bytes); and manager.flush(); are package visible only + few other visibility issues. So I would suggest to use more protected visibility than package as well as 'template method' pattern, especially in classes like AbstractOutputStreamAppender. In order to finalize my story I have to say that the final solution was to put a copied AbstractOutputStreamAppender and new Appender in namespace org.apache..... which is definitely not nice. So, can you please consider making changes that would make lives of extensions writers a little bit easier ? Regards, Tomek ------------------------------------------------- &lt; at &gt;Override public void append(final LogEvent event) { final byte[] bytes = getLayout().toByteArray(event); boolean failedOnSize = false; readLock.lock(); try { if (bytes.length &gt; 0) { if (bytes.length &lt;= udpSizeLimit) { manager.write(bytes); if (this.immediateFlush || event.isEndOfBatch()) { manager.flush(); } } else { failedOnSize = true; } } } catch (final AppenderRuntimeException ex) { error("Unable to write to stream " + manager.getName() + " for appender " + getName()); throw ex; } finally { readLock.unlock(); } if (failedOnSize) { handleFailedSize(event, bytes); } }---------------------------------------------- </pre> Tomek Kaczynski 2013-05-13T12:07:01 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20346 <pre>Hello folks, this is just a short heads up that I am going to present Logging on the "Java Forum Stuttgart": http://www.java-forum-stuttgart.de/de/Abstracts+Slot+7.html#art470 I will focus on log4j 2 and its new great features and want to look into the async appenders as well. Besides i will give an introduction into how we operate at all and of course that we are offering Chainsaw and Receivers too. With the recent growing of log4j and the great contributions, I believe we'll get some interest. Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de </pre> Christian Grobmeier 2013-05-13T09:28:04 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20319 <pre>+---------------------------------------------------------------------------+ | 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 | | | | | | | | 4913|Opn|Min|2001-11-16|org.apache.log4j.helpers.FileWatchdog should allow| |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|New|Enh|2003-09-22|&lt;logger&gt; element in XML config should support reso| |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 | |28059|Opn|Enh|2004-03-30|DOMConfigurator.configure(java.io.InputStream) | |29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM| |29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe| |30055|New|Nor|2004-07-12|Problem with registering Appenders with the same n| |30888|Inf|Maj|2004-08-27|Chainsaw mixes files in same panel | |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 | |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|Inf|Nor|2005-05-04|Chainsaw does not remember what Columns are select| |34974|Inf|Cri|2005-05-19|Exception when running a Pluglet | |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 &lt;property&gt; 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| |37638|New|Nor|2005-11-25|logging doesn't fall back with FallbackErrorHandle| |37734|New|Nor|2005-12-01|Customize Event ID and Event Category with NTEVent| |38363|Ass|Maj|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| |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 | |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 | |40611|New|Trv|2006-09-27|Bad subclass example; NullPointerException in Logg| |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? | |41547|Inf|Nor|2007-02-05|PropertyConfigurator and layout.contentType | |41799|New|Enh|2007-03-09|SyslogAppender should enable to customize Log4j.Le| |41980|Inf|Maj|2007-03-29|Log4j stop updating log file- version log4j-1.2.8 | |42189|Ass|Nor|2007-04-22|Add simple bridge for java.util.logging, with basi| |42213|Opn|Blk|2007-04-24|log4j causing threads to stuck in weblogic | |42516|Inf|Nor|2007-05-24|Log4j failed to log file when packaged in Eclipse | |42664|New|Enh|2007-06-14|JUL Appender | |42883|Opn|Nor|2007-07-12|'Welcome' and 'Drag &amp; Drop' panels can't be hidden| |42933|Inf|Maj|2007-07-18|IllegalStateException thrown from FileAppender.clo| |43282|Opn|Nor|2007-08-31|Add OSGi packaging info to log4j and companions | |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 | |44219|Inf|Nor|2008-01-13|'WARNING' for a log level is silently ignored/chan| |44308|New|Enh|2008-01-28|[Patch] JMX component for managing Logger configur| |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| |44649|Inf|Nor|2008-03-20|JMS Hangs when a Root Appender | |44700|New|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|Cri|2008-05-05|improve DailyRollingFileAppender handling of rotat| |44934|Inf|Enh|2008-05-05|add helper method to DailyRollingFileAppender to g| |45042|New|Nor|2008-05-19|Need a reliable way to detect misconfiguration | |45109|Inf|Nor|2008-05-31|SMTPAppender uses wrong property for mail server | |45165|Ass|Enh|2008-06-09|Multifile Appender | |45231|Ass|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|Inf|Nor|2008-06-29|using log4j with OAS for some reasone all the logg| |45482|Inf|Min|2008-07-25|Source contains unused variables | |45629|New|Nor|2008-08-13|TopicConnection is not closed | |45753|New|Nor|2008-09-06|Code contribution: BurstFilter for extras | |45781|New|Nor|2008-09-11|RollingFileAppender under Windows does not rotate | |45855|New|Enh|2008-09-21|Add site/apt documentation for JULBridgeLogManager| |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| |46100|New|Enh|2008-10-27|NagiosAppender available for contribution | |46260|Inf|Nor|2008-11-21|RollingFileAppender and Tomcat has a strange behav| |46426|Ass|Nor|2008-12-20|Implement commons-logging interfaces natively in l| |46514|New|Nor|2009-01-12|provide API to re-init log4j | |46533|New|Enh|2009-01-14|Deamon Thread | |46570|New|Nor|2009-01-20|DailyRollingFileAppender rolls logs into files dat| |46573|Inf|Maj|2009-01-21|MDC attributes cant't be displayed on Chainsaw | |46592|Opn|Trv|2009-01-23|trim() on property file entries | |46691|New|Nor|2009-02-10|log4j file rolling over on restart of the server | |46804|New|Enh|2009-03-05|create the method PropertyConfigurator.configureAn| |46868|New|Nor|2009-03-17|SocketHUBAppender: Allow restriction of binding to| |46878|New|Cri|2009-03-19|Deadlock in 1.2.15 caused by AsyncAppender and Thr| |46941|New|Enh|2009-03-31|Sub Level Logging Technique | |46983|New|Enh|2009-04-07|More Debug output for log4j auto-configure request| |47123|New|Blk|2009-04-29|TimeBasedRollingPolicy appends logs into a old log| |47141|Inf|Enh|2009-05-02|add getCyclicBuffer() method to log4j SMTPAppender| |47164|New|Enh|2009-05-07|HTMLLayout replace newline with &lt;BR&gt; | |47208|New|Enh|2009-05-17|Better Default colours for Log Panel Color Filter | |47357|New|Min|2009-06-11|Declaring logger and category with same name cause| |47575|Inf|Nor|2009-07-24|GZipping large files stops logging | |47595|Opn|Nor|2009-07-28|[companion] POMs of companions have problems | |47703|New|Nor|2009-08-18|Object rendering ought to be done outside synchron| |47713|Inf|Nor|2009-08-20|SMTPAppender system properties propagation issue | |47740|Inf|Nor|2009-08-26|log4j 1.2.15 deadlock RootAppender NDC | |47883|New|Nor|2009-09-21|Lines dropped with UseNewHashFunction | |47898|Inf|Maj|2009-09-24|DailyRollingFileAppender unable to create backup l| |47960|New|Min|2009-10-08|CompositeAppender contribution | |48027|Inf|Cri|2009-10-20|Logger statements in a particular class file is no| |48141|Inf|Cri|2009-11-05|Log file rotation issue in Linux VM | |48209|New|Nor|2009-11-17|Websphere 6.0: logging statements appear in the SY| |48220|New|Min|2009-11-18|LoggingEvent.mdcCopy serialization with non-serial| |48244|New|Min|2009-11-19|Socket Server configuration does not handle not re| |48365|New|Maj|2009-12-10|Log4J DailyRollingFileAppender sometimes does not | |48430|New|Nor|2009-12-22|log4j:ERROR Write failure. java.io.IOException: St| |48502|New|Cri|2010-01-07|Issue: Rotation file is not getting created - Roll| |48583|New|Enh|2010-01-20|allow format of timestamp (first column of log fil| |48607|New|Cri|2010-01-25|Log levels are not displayed corectly | |48679|New|Nor|2010-02-04|performance of getEffectiveLevel can be significan| |48704|New|Nor|2010-02-08|Multiple Java Process in Cluster Logging to the sa| |48802|New|Nor|2010-02-23|Log4j not writting. | |48820|New|Nor|2010-02-26|JDBCAppender inserts the current MDC values for th| |48986|New|Nor|2010-03-25|RollingFileAppender.rollOver() calls this.setFile | |49003|New|Nor|2010-03-27|SocketServerTestCase.test8 fails on Apache Harmony| |49177|New|Enh|2010-04-23|SyslogAppender: Make the maximum package size conf| |49247|New|Enh|2010-05-04|Add option for persistent/non-persistent delivery | |49248|New|Min|2010-05-04|javadoc for org.apache.log4j.rolling.FixedWindowRo| |49265|New|Nor|2010-05-07|log4j - java.io.OptionalDataException | |49307|New|Nor|2010-05-18|unusable error message when log4j.xml has a duplic| |49349|New|Nor|2010-05-27|LoggingEvent stoped coming with AsyncAppender | |49353|New|Nor|2010-05-28|[patch] change logfactor userdir name to hidden di| |49354|New|Nor|2010-05-28|XMLLayout writes illegal characters to XML file | |49390|New|Nor|2010-06-05|1.0 releases of log4j companions component and rec| |49421|New|Maj|2010-06-10|Chainsaw don't show Logger for SocketReceiver and | |49481|New|Maj|2010-06-21|Log4j stops writting to file, and then causes serv| |49489|New|Enh|2010-06-22|Ability to filter on several loggers | |49563|New|Min|2010-07-06|New SMTPProtocol and SMTPPort not recognized | |49571|New|Enh|2010-07-08|refreshing log4j - reconfigurable from log4j.prope| |49592|New|Cri|2010-07-14|477 All Attributes Not Set | |49597|New|Min|2010-07-15|The log4j.dtd is to restrictive | |49693|New|Cri|2010-08-03|Intermittently Log4j fails to bind with log file | |49797|New|Enh|2010-08-22|AsyncAppenders Enchancement | |49852|New|Enh|2010-08-31|Allow log files to rollover at any specified time | |49853|New|Enh|2010-08-31|Adding loggers to the configuration | |49854|New|Nor|2010-08-31|Documentation | |49899|New|Nor|2010-09-08|PatternLayout and EnhancedPatternLayout issues wit| |49920|New|Maj|2010-09-13|DailyRollingFileAppender.rollOver() might leave su| |50085|New|Maj|2010-10-13|SyslogAppender does not split stack traces correct| |50164|New|Nor|2010-10-27|getAppender method in Logger class doesn't return | |50166|New|Nor|2010-10-27|DailyRollingFileAppender and FileAppender fail to | |50188|New|Nor|2010-10-31|Update site content to Apache Branding Requirement| |50213|New|Nor|2010-11-04|Category callAppenders synchronization causes java| |50225|New|Nor|2010-11-06|Filesystem placeholder not working with PropertyCo| |50226|New|Nor|2010-11-06|Problem with placeholders and PropertyConfigurator| |50238|New|Cri|2010-11-09|wrong log levels logged with the serialized Loggin| |50323|New|Nor|2010-11-23|Vulnerability in NTEventLogAppender | |50366|New|Enh|2010-11-29|JDBCAppender Enhancement | |50433|New|Maj|2010-12-08|Drag and Drop does not work anymore | |50445|New|Nor|2010-12-09|Color bar is higher than scrollabr | |50463|New|Nor|2010-12-13|AsyncAppender causing deadlock when dispatcher thr| |50479|New|Nor|2010-12-15|[PATCH] JMSQueueAppender - Change message object t| |50614|New|Maj|2011-01-19|Lock in CallAppenders causing all Thread to wait f| |50641|New|Cri|2011-01-24|"Too Many Open Files" while using RollingFileAppen| |50776|New|Enh|2011-02-14|Support TCP in SyslogAppender | |50800|New|Cri|2011-02-16|log4j 1.2.16 has duplicate import-package entries | |50817|New|Nor|2011-02-22|The JDBCAppender can't insert log info like this:h| |50830|New|Min|2011-02-25|NPE in ISO8601DateFormat.hashCode and toString | |50844|New|Nor|2011-02-28|DateFormat.getDateTimeInstance() is very expensive| |50845|New|Enh|2011-03-01|Content Assist (Ctrl + Space) needed in log4j.prop| |50856|New|Enh|2011-03-02|Allow ignoreTCL option to be set in log4jconfig.xm| |50858|New|Nor|2011-03-02|Classloader leak when using Log4j in a webapp cont| |50930|New|Nor|2011-03-14|org.apache.log4jPriority methods toString(), toInt| |50931|New|Nor|2011-03-14|unclosed http | |51025|New|Nor|2011-04-05|PropertyConfigurator does not properly set up Erro| |51047|New|Maj|2011-04-11|Move org.apache.log4j.Category to reentrant read/w| |51048|New|Nor|2011-04-11|AsyncAppender.doAppend() does not need to be synch| |51055|New|Nor|2011-04-13|Appender not working properly with Windows Server | |51122|Inf|Enh|2011-04-26|Include option in throwable pattern converter to c| |51152|New|Nor|2011-05-04|RollingFileAppender of companion/extras 1.1 contai| |51164|New|Nor|2011-05-06|log4j should not dump errors to stdout on interrup| |51227|New|Maj|2011-05-19|after deleting logs using trash button no more log| |51279|New|Maj|2011-05-28|log4j.properties doesn't support environment varia| |51347|New|Cri|2011-06-09|Filename and line number not display , Java versio| |51438|New|Nor|2011-06-27|Pipe characters issue in log() method | |51538|New|Nor|2011-07-21|Chainsaw 2 - add password to JMSReceiverBeanInfo i| |51578|New|Cri|2011-07-28|Javaw.exe - Application Error -- The memory could | |51651|New|Nor|2011-08-11|Hook in before log4j starts, e.g. UnrecognizedElem| |51672|New|Enh|2011-08-17|Queue Appender for logging | |51721|New|Nor|2011-08-25|Log4j snapshots should be in the Apache Snapshot R| |51766|Opn|Nor|2011-09-06|Relocate RewriteAppender and UtilLoggingLevel from| |51783|New|Maj|2011-09-07|WriterAppender NullPointerException when calling c| |51784|New|Enh|2011-09-08|logger adapter, delagate call to logging method | |51849|New|Maj|2011-09-20|LogManager and ipv6 address | |51979|New|Reg|2011-10-06|Fix for bug 42087 introduces line truncating in sy| |52014|New|Nor|2011-10-12|option to set encoding for console appender confli| |52077|New|Nor|2011-10-24|Log entries are lost after rollover | |52094|New|Nor|2011-10-26|Add InputStream API to OptionConverter.selectAndCo| |52095|New|Nor|2011-10-26|Inconsistent Javadoc comment in addAppender(Append| |52133|New|Min|2011-11-04|Logging of configuration URLs/Paths on log4j confi| |52141|New|Blk|2011-11-05|[STUCK] ExecuteThread...Blocked trying to get lock| |52168|New|Nor|2011-11-10|change log4j property file at runtime cause an emp| |52392|New|Cri|2011-12-28|Issue with DailyRollingFileAppender | |52401|New|Blk|2011-12-30|Appender threshold set causes no logs to be writte| |52463|New|Enh|2012-01-13|log4j-extras: Configure thread priority of asynchr| |52490|New|Nor|2012-01-19|facelets.viewhandler logger using incorrect config| |52555|New|Nor|2012-01-30|[main][WARN][SocketServer]Could not find config fi| |52676|New|Nor|2012-02-15|Location information unavailable when FQCN ends in| |52699|New|Nor|2012-02-17|Misleading DailyRollingFileAppender javadoc | |52733|New|Maj|2012-02-21|log4j:ERROR Could not find value for key log4j.app| |52765|New|Blk|2012-02-25|ZeroConf does not work | |52797|New|Maj|2012-02-29|SyslogAppender ignores the whole message | |53299|New|Cri|2012-05-26|Simplify log4j Build | |53300|New|Maj|2012-05-26|Improve site build | |53345|New|Maj|2012-06-01|OutOfMemory Error from Appender | |53392|New|Maj|2012-06-11|Rolling file cannot be written, suspecting infinit| |53415|New|Cri|2012-06-14|JDBCAppender cannot reconnect after connection clo| |53417|New|Nor|2012-06-14|Extras TimeBasedRollingPolicy does not compress lo| |53471|New|Reg|2012-06-26|mvn fails with s.addTestSuite(org.apache.log4j.net| |53536|New|Maj|2012-07-11|RollingFileAppender with TimeBasedRolling policy d| |53557|New|Nor|2012-07-17|Configure java.util.logging messages to custom log| |53635|New|Nor|2012-08-01|LOG4J logging does not work correctly on Solaris w| |53645|New|Nor|2012-08-02|DBAppender has a compile error | |53745|New|Nor|2012-08-20|Extra's RollingFileAppender Delete Files | |53791|New|Enh|2012-08-28|Enabling compression of backups using the log4j.pr| |53948|New|Enh|2012-09-29|ThrowableInformationPatternConverter does not need| |54009|New|Cri|2012-10-16|Thread is getting Blocked | |54035|New|Nor|2012-10-22|logger.setLevel is not thread safe. | |54078|New|Enh|2012-10-30|FlashbackAppender: new appender for lost events | |54325|New|Nor|2012-12-19|Concurrency issues in AppenderAttachableImpl | |54335|New|Nor|2012-12-20|Removing columns in the log panel preferences resu| |54398|New|Nor|2013-01-10|Improve AyncAppender's append performance | |54455|New|Nor|2013-01-21|DynamicImport-Package in MANIFEST.MF not working i| |54635|New|Nor|2013-03-05|Can't truncate priority to first character | |54809|New|Maj|2013-04-07|Loader.getResource(String) and Loader.loadClass(St| |54818|New|Nor|2013-04-09|SyslogAppender tag does not support non-alphanumer| |54862|New|Maj|2013-04-18|log4j:ERROR Failed to rename | +-----+---+---+----------+--------------------------------------------------+ | Total 253 bugs | +---------------------------------------------------------------------------+ </pre> bugzilla< at >apache.org 2013-05-12T07:15:37 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20318 <pre>The Apache Log4j 2 team is pleased to announce the Log4j 2.0-beta6 release! Apache log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many of the improvements available in Logback while fixing some inherent problems in Logback's architecture. This is the eighth release of Log4j 2 and is being made available to encourage use and feedback from the community. Bug fixes and enhancements Changes in this version include: Fixed Bugs: o LOG4J2-231: Logger.getParent() was not returning the correct Logger. o LOG4J2-201: Renamed Plugin annotation attribute from "type" to "category". o LOG4J2-219: Fix: install default root logger if not configured (this is unchanged), but make sure to include configured named loggers. Clarified documentation. Thanks to Peter DePasquale. o LOG4J2-159: Use OSGi version format in Fragment-Host o LOG4J2-234: RegexFilter threw a NullPointerException when used as a context-wide filter. o LOG4J2-192: Add support for interpolating Environment variables when processing the configuration. o LOG4J2-235: Removed dependency on tools jar from core module, made jconsole dependency optional. Thanks to Sebastian Oerding. o LOG4J2-233: Fixed link to log4j-user mailing list. o LOG4J2-222: Disruptor will now shutdown during Tomcat shutdown. Thanks to Steven Yang. o LOG4J2-224: The FlumeAppender failed to start if the Flume RPCClient could not connect to any Flume agents. o LOG4J2-223: Fix LoggerContext start and stop to eliminate IllegalStateException and NoClassDefFound errors. o LOG4J2-221: Remove hundreds of compiler warnings. Thanks to Nick Williams. o LOG4J2-215: Various small documentation fixes. o LOG4J2-217: Ensure PluginManager streams are always closed. Thanks to Fabien Sanglard. Changes: o LOG4J2-237: Moved JMX Client GUI classes into separate jmx-gui submodule. o LOG4J2-230: Improved error reporting when misconfigured. Thanks to Wojciech Zaręba. o Renamed AsynchAppender to AsyncAppender. Plugin name became Async (was Asynch). o Removed CheckStyle false positives for NewlineAtEndOfFile and whitespace following '*' at end of line in javadoc. o Moved Clock interface to package org.apache.logging.log4j.core.helpers. o LOG4J2-225: Documentation updates to clarify use and impact of location in pattern layouts. Apache Log4j 2.0-beta6 requires a minimum of Java 6 to build and run. Basic compatibility with Log4j 1.x is provided through the log4j-1.2-api component, however it does not implement some of the very implementation specific classes and methods. The package names and Maven groupId have been changed to org.apache.logging.log4j to avoid any conflicts with log4j 1.x. For complete information on Apache Log4j 2, including instructions on how to submit bug reports, patches, or suggestions for improvement, see the Apache Apache Log4j 2 website: http://logging.apache.org/log4j/2.x/</pre> Ralph Goers 2013-05-12T06:09:52 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20315 <pre>[PROPOSAL for the text of an email and front page of the site] Log4j 2 logo contest Log4j 2 will be a major new version of Log4j. To mark this occasion, Log4j 2 will use a new logo. We would like to open participation to the community to create this new logo. Attach your entries to the Jira http://... Each person can submit more than one logo. Submissions will be accepted until [I pulled this one out of a hat] June 30, 2013. The PMC will then call for a vote on the user and dev mailing lists. You must submit your entries under the Apache License version 2.0. The Log4j team. --- Thoughts? Gary </pre> Gary Gregory 2013-05-12T01:38:33 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20312 <pre>Guys, There are a couple of things about the site that have been bugging me. I wanted to run some ideas by you and see what you think. Since I can commit now, I can take care of them once we come to a consensus. :-) </pre> Nick Williams 2013-05-11T23:13:20 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20276 <pre>Dear Infra, The Log4J 2 project would like to be able to use markup codes in Jira text fields. To enable this, an admin with 'global permissions' needs to log in according to https://confluence.atlassian.com/display/JIRA052/Specifying+Field+Behaviour Is this kind of permission in our admin rights, or does infra need to do it on our behalf? I cannot seem to do it even though I have other kinds of edit powers on the project. Thank you in advance for your help. Gary </pre> Gary Gregory 2013-05-10T12:46:48 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20272 <pre>This vote has passed with +1s from Ralph Goers (binding) Gary Gregory (binding) Ivan Habunek (binding) Christian Grobmeier (binding) Oliver Lamy Remko Popma The vote received 1 -1 vote from Nick Williams. I will continue with the release process. Thank you for taking the time to review the release. Ralph </pre> Ralph Goers 2013-05-10T06:37:24 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20241 <pre>For most of the JIRA project I work on, I am able to use {code:java} and the like to markup comments. Can someone enable this for our project? I've not found a way to do this or I do not have the karma. Thank you, Gary </pre> Gary Gregory 2013-05-09T20:06:36 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/20194 <pre>Hi All, I'm using log4j2 since beta4, now beta5. In general it's a cute library, but there's some bug that I've found out recently : When a client code genreates a huge message ( 64k ), the underlying DatagramOutputStream fails ( UDP socket throws exception). After that all following flushes fail because data buffer is not cleared upon exception. So in lines DatagramOutputStream:91 ---------------------------------------------------------------------- public synchronized void flush() throws IOException { if (this.data != null &amp;&amp; this.ds != null &amp;&amp; this.address != null) { final DatagramPacket packet = new DatagramPacket(data, data.length, address, port); ds.send(packet); } data = null; } -------------------------------------------------------------------------- data = null should be put in finally block or some simillar solution could be applied. What do you think ? Regards, Tomek Moreover DatagramOutputStream should check if message size is less then 64k . </pre> Tomek Kaczynski 2013-05-09T09:34:30 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.jakarta.log4j.devel