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/14269 https://issues.apache.org/bugzilla/show_bug.cgi?id=45660 Summary: NDC could remove Hashtable entry if Stack gets empty Product: Log4j Version: 1.2 Platform: PC OS/Version: Windows XP Status: NEW Severity: enhancement Priority: P3 Component: Other AssignedTo: log4j-dev< at >logging.apache.org ReportedBy: kiralyattila.hu< at >gmail.com NDC documentation says that users should call remove() to get rid of the not needed entries and that the best place for that would be at the end of the thread's life. However in a servlet/filter environment (for example Spring's Log4jNestedDiagnosticContextFilter, http://static.springframework.org/spring/docs/2.5.x/api/org/springframework/web/filter/Log4jNestedDiagnosticContextFilter.html) there is no ideal place to call NDC.remove() (because spring does not know if anything else is using NDC or not and the web app developer does not know if the servlet container is using NDC or bugzilla< at >apache.org 2008-08-20T20:03:04 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14265 Author: carnold Date: Wed Aug 20 09:43:32 2008 New Revision: 687385 URL: http://svn.apache.org/viewvc?rev=687385&view=rev Log: Bug 45659: Incorrect user mailing list URL Modified: logging/log4j/trunk/pom.xml logging/log4j/trunk/src/changes/changes.xml Modified: logging/log4j/trunk/pom.xml URL: http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=687385&r1=687384&r2=687385&view=diff ============================================================================== --- logging/log4j/trunk/pom.xml (original) +++ logging/log4j/trunk/pom.xml Wed Aug 20 09:43:32 2008 < at >< at > -39,7 +39,7 < at >< at > <subscribe>log4j-user-subscribe< at >logging.apache.org</subscribe> <unsubscribe>log4j-user-unsubscribe< at >logging.apache.org</unsubscribe> <post>log4j-user< at >logging.apache.org</post> - <archive>http://mail-archives.apache.org/mod_mbox/logging-log4j-dev/</archive> + <archive>http://mail-archives.apache.org/mod_mbox/logging-log4j-user/</archive> <otherArchives> <otherArchive>http:// carnold< at >apache.org 2008-08-20T16:43:37 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14262 https://issues.apache.org/bugzilla/show_bug.cgi?id=45659 Summary: Incorrect user mailing list URL Product: Log4j Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: trivial Priority: P3 Component: Other AssignedTo: log4j-dev< at >logging.apache.org ReportedBy: sip.sniffa< at >gmail.com The URL for the log4j-user mail archive (under the table heading Archive) links to the developer mailing list (http://mail-archives.apache.org/mod_mbox/logging-log4j-dev/) rather than the user mailing list (http://mail-archives.apache.org/mod_mbox/logging-log4j-user/). bugzilla< at >apache.org 2008-08-20T13:04:31 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14261 https://issues.apache.org/bugzilla/show_bug.cgi?id=45658 Summary: error when working with ConsoleAppender Product: Log4j Version: 1.2 Platform: PC OS/Version: Windows XP Status: NEW Severity: major Priority: P2 Component: Appender AssignedTo: log4j-dev< at >logging.apache.org ReportedBy: spamolovko< at >gmail.com package ru.sanalis; import org.apache.log4j.Logger; public class LoggerTest { static private Logger LOG = Logger.getLogger(LoggerTest.class); static public void main(String[] args) { LOG.debug("Debug > " + args); LOG.fatal("Fatal > " + args); } } Config: # ***** Set root logger level to WARN and its two appenders to stdout and R. log4j.rootLogger=debug, stdoutRoot log4j.logger.ru=fatal, stdout # ***** stdout is set to be a ConsoleAppender. log4j.appender.stdoutRoot=org.apache.log4j.ConsoleAppender # ***** stdout uses PatternLayout. log4j.appender.stdoutRoot.layout=or bugzilla< at >apache.org 2008-08-20T11:17:34 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14259 Author: carnold Date: Mon Aug 18 15:31:24 2008 New Revision: 686885 URL: http://svn.apache.org/viewvc?rev=686885&view=rev Log: Bug 44517: Comment out JMX dependency only needed for builds on JDK 1.4 Modified: logging/log4j/trunk/pom.xml Modified: logging/log4j/trunk/pom.xml URL: http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=686885&r1=686884&r2=686885&view=diff ============================================================================== --- logging/log4j/trunk/pom.xml (original) +++ logging/log4j/trunk/pom.xml Mon Aug 18 15:31:24 2008 < at >< at > -424,12 +424,14 < at >< at > <version>1.4</version> <optional>true</optional> </dependency> + <!-- the following dependency is not needed on JDK 1.5 and higher <dependency> <groupId>com.sun.jmx</groupId> <artifactId>jmxri</artifactId> <version>1.2.1</version> <optional>true</optional> </dependency> + --> <dependency> <groupId>oro</groupId> <artifactId>oro</artifactId> carnold< at >apache.org 2008-08-18T22:31:25 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14258 Author: carnold Date: Mon Aug 18 15:24:46 2008 New Revision: 686884 URL: http://svn.apache.org/viewvc?rev=686884&view=rev Log: Bug 43282: Mark javax and com.sun imports as optional Modified: logging/log4j/trunk/pom.xml Modified: logging/log4j/trunk/pom.xml URL: http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=686884&r1=686883&r2=686884&view=diff ============================================================================== --- logging/log4j/trunk/pom.xml (original) +++ logging/log4j/trunk/pom.xml Mon Aug 18 15:24:46 2008 < at >< at > -373,8 +373,13 < at >< at > <instructions> <!-- omit chainsaw and LF5 --> <Export-Package>!org.apache.log4j.lf5.*,!org.apache.log4j.chainsaw.*,org.apache.log4j.*</Export-Package> - <!-- IBM Visual Age and HTMLAdapterServer are sniffed by reflection --> - <Import-Package>!com.ibm.uvm.tools,!com.sun.jdmk.comm,*</Import-Package> + <Import-Package>com.sun.jdmk.comm;resolution:=optional, + carnold< at >apache.org 2008-08-18T22:24:46 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14257 +---------------------------------------------------------------------------+ | 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|Op bugzilla< at >apache.org 2008-08-18T06:08:17 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14256 To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at general< at >gump.apache.org. Project logging-log4j-12-tests has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - logging-log4j-12-tests : Fast and flexible logging package for Java Full details are available at: http://vmgump.apache.org/gump/public/logging-log4j-12/logging-log4j-12-tests/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: activemq-core : unknown to *this* workspace To subscribe to this information via syndicated feeds: - RSS: http://vmgum carnold< at >apache.org 2008-08-16T10:04:12 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14254 I went and finally revisited a patch I proposed about a million years ago to enable testing of the JMSAppender class using ActiveMQ (Bug 38153). See my patch below [1]. However when I run the tests locally I'm getting a compile error: ... prepare: [available] DEPRECATED - <available> used to override an existing property. [available] Build file should not reuse the same property name for different values. build: [javac] Compiling 2 source files to /workspace/log4j/tests/classes /workspace/log4j/tests/src/java/org/apache/log4j/jms/ JMSAppenderTest.java:19: package javax.jms does not exist import javax.jms.Connection; We appear to run the tests via an antrun call within Maven, is that right? Just curious of the rationale there, why we couldn't just make it a standard maven test phase. Maybe there's a complication I'm not aware of, it's just not something I've had to deal with before, so I'm a bit confused on how to proceed. Normally for testing under Maven I've just added de Paul Smith 2008-08-16T00:15:27 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14252 Author: carnold Date: Fri Aug 15 16:09:53 2008 New Revision: 686415 URL: http://svn.apache.org/viewvc?rev=686415&view=rev Log: Bug 45636: 2 tests for DateLayout are failing because of ill initialized DateFormat Modified: logging/log4j/trunk/src/changes/changes.xml logging/log4j/trunk/src/main/java/org/apache/log4j/helpers/AbsoluteTimeDateFormat.java logging/log4j/trunk/src/main/java/org/apache/log4j/helpers/ISO8601DateFormat.java Modified: logging/log4j/trunk/src/changes/changes.xml URL: http://svn.apache.org/viewvc/logging/log4j/trunk/src/changes/changes.xml?rev=686415&r1=686414&r2=686415&view=diff ============================================================================== --- logging/log4j/trunk/src/changes/changes.xml (original) +++ logging/log4j/trunk/src/changes/changes.xml Fri Aug 15 16:09:53 2008 < at >< at > -58,6 +58,7 < at >< at > <action action="fix" issue="44157">InterruptedIOException ignored by log4j.</action> <action action="fix" issue="40246">HierarchyDynamicMBean missing unregi carnold< at >apache.org 2008-08-15T23:09:53 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14250 Author: carnold Date: Fri Aug 15 15:48:39 2008 New Revision: 686411 URL: http://svn.apache.org/viewvc?rev=686411&view=rev Log: Bug 45635: Maven local repository location hard coded in pom test phase Modified: logging/log4j/trunk/pom.xml logging/log4j/trunk/src/changes/changes.xml Modified: logging/log4j/trunk/pom.xml URL: http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=686411&r1=686410&r2=686411&view=diff ============================================================================== --- logging/log4j/trunk/pom.xml (original) +++ logging/log4j/trunk/pom.xml Fri Aug 15 15:48:39 2008 < at >< at > -207,11 +207,8 < at >< at > <id>runAll</id> <configuration> <tasks> - <ant dir="tests" target="runAll"> - <property name="junit.jar" location="${user.home}/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar"/> - <property name="jakarta.oro.jar" location="${user.home}/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar"/> - carnold< at >apache.org 2008-08-15T22:48:39 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14248 https://issues.apache.org/bugzilla/show_bug.cgi?id=45636 Summary: 2 tests for DateLayout are failing because of ill initialized DateFormat Product: Log4j Version: 1.2 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Other AssignedTo: log4j-dev< at >logging.apache.org ReportedBy: philippe.haution< at >mines-paris.org Inside org.apache.log4j.helpers.DateLayoutTest, testISO8601Format() and testDateTimeFormat() necessarily result in failures when run through an mvn test in the root directory. Indeed the ISO8601DateFormat and DateTimeFormat object responsible for this issue have a memory of the previous date they formatted (kept as a long representing the specified number of milliseconds since the standard base time known as "the epoch", namely January 1, 1970, 00:00:00 GMT) and the resulting String. If they are asked again to format the same time, then the bugzilla< at >apache.org 2008-08-15T15:37:36 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14247 https://issues.apache.org/bugzilla/show_bug.cgi?id=45635 Summary: Maven local repository location hard coded in pom test phase Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Other AssignedTo: log4j-dev< at >logging.apache.org ReportedBy: philippe.haution< at >mines-paris.org The maven test phase calls the unit tests through a maven-antrun-plugin, with all necessary jars picked up in the default local repository ${user.home}/.m2/repository : ... <execution> <phase>test</phase> <id>runAll</id> <configuration> <tasks> <ant dir="tests" target="runAll"> <property name="junit.jar" location="${user.home}/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar" /> <property name="jakarta.oro.jar" location="${user.home}/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar" /> ... If the maven repository is not in this bugzilla< at >apache.org 2008-08-15T13:00:52 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14243 Author: carnold Date: Thu Aug 14 22:53:55 2008 New Revision: 686149 URL: http://svn.apache.org/viewvc?rev=686149&view=rev Log: Bug 44157: InterruptedIOException ignored by log4j Modified: logging/log4j/trunk/src/main/java/org/apache/log4j/config/PropertyGetter.java logging/log4j/trunk/src/main/java/org/apache/log4j/config/PropertySetter.java logging/log4j/trunk/src/main/java/org/apache/log4j/helpers/Loader.java logging/log4j/trunk/src/main/java/org/apache/log4j/helpers/OptionConverter.java logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/Agent.java logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/AppenderDynamicMBean.java logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/LayoutDynamicMBean.java logging/log4j/trunk/src/main/java/org/apache/log4j/net/SocketHubAppender.java logging/log4j/trunk/src/main/java/org/apache/log4j/net/SocketNode.java logging/log4j/trunk/src/main/java/org/apache/log4j/net/TelnetAppender.java logging/log4j/trunk/src/main/jav carnold< at >apache.org 2008-08-15T05:53:56 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14241 Author: psmith Date: Thu Aug 14 20:31:30 2008 New Revision: 686131 URL: http://svn.apache.org/viewvc?rev=686131&view=rev Log: Bug 40246 Added cleaned up patch provided by wing tung Leung to allow the JMX Beans created to properly deregister, allowing Servlet Containers that shutdown/restart to be able to (re)register new JMX beans of the same name. Modified: logging/log4j/trunk/src/changes/changes.xml logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/AbstractDynamicMBean.java logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/AppenderDynamicMBean.java logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/HierarchyDynamicMBean.java logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/LoggerDynamicMBean.java Modified: logging/log4j/trunk/src/changes/changes.xml URL: http://svn.apache.org/viewvc/logging/log4j/trunk/src/changes/changes.xml?rev=686131&r1=686130&r2=686131&view=diff ============================================================================== --- logging/log4j/t psmith< at >apache.org 2008-08-15T03:31:31 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14237 Author: carnold Date: Thu Aug 14 00:56:20 2008 New Revision: 685796 URL: http://svn.apache.org/viewvc?rev=685796&view=rev Log: Bug 44157: InterruptedIOException ignored by log4j, round 2 Modified: logging/log4j/trunk/src/main/java/org/apache/log4j/PropertyConfigurator.java logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/AbstractDynamicMBean.java logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/Agent.java logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/AppenderDynamicMBean.java logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/HierarchyDynamicMBean.java logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/LayoutDynamicMBean.java logging/log4j/trunk/src/main/java/org/apache/log4j/jmx/LoggerDynamicMBean.java logging/log4j/trunk/src/main/java/org/apache/log4j/net/JMSAppender.java logging/log4j/trunk/src/main/java/org/apache/log4j/net/JMSSink.java logging/log4j/trunk/src/main/java/org/apache/log4j/net/SMTPAppender.java logging/log4j/trunk/sr carnold< at >apache.org 2008-08-14T07:56:21 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14235 https://issues.apache.org/bugzilla/show_bug.cgi?id=45629 Summary: TopicConnection is not closed Product: Log4j Version: unspecified Platform: PC OS/Version: Windows 2000 Status: NEW Severity: normal Priority: P2 Component: Other AssignedTo: log4j-dev< at >logging.apache.org ReportedBy: ackel< at >sohu.com In the code snippet [1], public JMSSink( String tcfBindingName, String topicBindingName, String username, String password) creates a TopicConnection but does not close it in any situation. JMSSink needs to implement a close method to deal with the resource, doesn't it? [1]http://svn.apache.org/viewvc/logging/log4j/trunk/src/main/java/org/apache/log4j/net/JMSSink.java?revision=565523&view=markup bugzilla< at >apache.org 2008-08-14T00:56:21 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14231 Author: carnold Date: Wed Aug 13 14:35:05 2008 New Revision: 685684 URL: http://svn.apache.org/viewvc?rev=685684&view=rev Log: Bug 44157: InterruptedIOException ignored by log4j Modified: logging/log4j/trunk/src/changes/changes.xml logging/log4j/trunk/src/main/java/org/apache/log4j/DailyRollingFileAppender.java logging/log4j/trunk/src/main/java/org/apache/log4j/FileAppender.java logging/log4j/trunk/src/main/java/org/apache/log4j/RollingFileAppender.java logging/log4j/trunk/src/main/java/org/apache/log4j/WriterAppender.java logging/log4j/trunk/src/main/java/org/apache/log4j/helpers/OnlyOnceErrorHandler.java logging/log4j/trunk/src/main/java/org/apache/log4j/net/SocketAppender.java logging/log4j/trunk/src/main/java/org/apache/log4j/net/SocketHubAppender.java logging/log4j/trunk/src/main/java/org/apache/log4j/net/SocketNode.java logging/log4j/trunk/src/main/java/org/apache/log4j/net/SyslogAppender.java logging/log4j/trunk/src/main/java/org/apache/log4j/net/TelnetApp carnold< at >apache.org 2008-08-13T21:35:05 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14229 Author: carnold Date: Wed Aug 13 12:27:27 2008 New Revision: 685646 URL: http://svn.apache.org/viewvc?rev=685646&view=rev Log: Bug 43282: Add OSGi packaging info Modified: logging/log4j/trunk/pom.xml logging/log4j/trunk/src/changes/changes.xml Modified: logging/log4j/trunk/pom.xml URL: http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=685646&r1=685645&r2=685646&view=diff ============================================================================== --- logging/log4j/trunk/pom.xml (original) +++ logging/log4j/trunk/pom.xml Wed Aug 13 12:27:27 2008 < at >< at > -19,7 +19,7 < at >< at > <modelVersion>4.0.0</modelVersion> <groupId>log4j</groupId> <artifactId>log4j</artifactId> - <packaging>jar</packaging> + <packaging>bundle</packaging> <name>Apache Log4j</name> <version>1.2.16-SNAPSHOT</version> <description>Apache Log4j 1.2</description> < at >< at > -367,6 +367,20 < at >< at > <artifactId>rat-maven-plugin</artifactId> <version>1.0-alpha-3</version> </plugin> + <plugin> + carnold< at >apache.org 2008-08-13T19:27:29 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14228 Author: carnold Date: Wed Aug 13 10:40:34 2008 New Revision: 685618 URL: http://svn.apache.org/viewvc?rev=685618&view=rev Log: Bug 45039: Rework to work from bottom down and explicitly format fullinfo Modified: logging/log4j/trunk/src/main/java/org/apache/log4j/spi/LocationInfo.java Modified: logging/log4j/trunk/src/main/java/org/apache/log4j/spi/LocationInfo.java URL: http://svn.apache.org/viewvc/logging/log4j/trunk/src/main/java/org/apache/log4j/spi/LocationInfo.java?rev=685618&r1=685617&r2=685618&view=diff ============================================================================== --- logging/log4j/trunk/src/main/java/org/apache/log4j/spi/LocationInfo.java (original) +++ logging/log4j/trunk/src/main/java/org/apache/log4j/spi/LocationInfo.java Wed Aug 13 10:40:34 2008 < at >< at > -131,34 +131,42 < at >< at > return; if (getLineNumberMethod != null) { try { - boolean hitCaller = false; Object[] noArgs = null; Object[] elements = (Object[]) getStackTrace carnold< at >apache.org 2008-08-13T17:40:35 http://comments.gmane.org/gmane.comp.jakarta.log4j.devel/14220 TopicConnection is not closed ----------------------------- Key: LOG4J2-25 URL: https://issues.apache.org/jira/browse/LOG4J2-25 Project: Log4j 2 Issue Type: Bug Reporter: Hao Zhong In the code snippet [1], public JMSSink( String tcfBindingName, String topicBindingName, String username, String password) creates a TopicConnection but does not close it in any situation. JMSSink needs to implement a close method to deal with the resource, doesn't it? [1]http://svn.apache.org/viewvc/logging/log4j/trunk/src/main/java/org/apache/log4j/net/JMSSink.java?revision=565523&view=markup Hao Zhong (JIRA 2008-08-13T08:22:46 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.jakarta.log4j.devel