http://permalink.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://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20663 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13665608#comment-13665608 ] Jim Tang commented on LOG4J2-265: --------------------------------- Hi Ralph, I have changed the attachment to zip formant:) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Jim Tang (JIRA 2013-05-23T20:17:20 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20662 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Tang updated LOG4J2-265: ---------------------------- Attachment: (was: zzzzzzzzzzzzzzzzzTest.7z) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Jim Tang (JIRA 2013-05-23T20:17:20 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20661 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Tang updated LOG4J2-265: ---------------------------- Attachment: zzzzzzzzzzzzzzzzzTest.zip -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Jim Tang (JIRA 2013-05-23T20:17:20 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20660 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13665311#comment-13665311 ] Ralph Goers commented on LOG4J2-265: ------------------------------------ I don't have 7-zip for OSX and can't seem to find a current one. Can you please use zip or gzip? I will test this once I can unarchive the attachment, however since the FlumeAvroManager now just uses the Flume RPC Client this is most likely something that will have to be fixed in Flume. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Ralph Goers (JIRA 2013-05-23T16:24:21 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20659 <pre>Jim Tang created LOG4J2-265: ------------------------------- Summary: FlumeAppender Stops App from Shutting Down when Newer Version of Netty is Used Key: LOG4J2-265 URL: https://issues.apache.org/jira/browse/LOG4J2-265 Project: Log4j 2 Issue Type: Bug Components: Appenders Affects Versions: 2.0-beta6 Reporter: Jim Tang Attachments: zzzzzzzzzzzzzzzzzTest.7z FlumeAppender(log4j-flume-ng) depends on flume-ng-sdk, which uses netty-3.4.0.Final. When a higher version of netty is used instead, such as 3.5.8.Final or 3.6.5.Final, FlumeAppender will not shutdown properly. To reproduce the problem (use attached Maven project): 1. Start your remote flume agent 2. Change the log4j2.xml to your agent host and port 3. press x and hit Enter Notice how the application continues to run. Press x should break out of the main loop and return from main(), indicating that the application should close. The thread holding</pre> Jim Tang (JIRA 2013-05-23T15:03:19 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20658 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Tang updated LOG4J2-265: ---------------------------- Attachment: zzzzzzzzzzzzzzzzzTest.7z -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Jim Tang (JIRA 2013-05-23T15:03:20 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20657 <pre>https://issues.apache.org/bugzilla/show_bug.cgi?id=55011 Dmitry &lt;moon3854&lt; at &gt;yandex.ru&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |moon3854&lt; at &gt;yandex.ru </pre> bugzilla< at >apache.org 2013-05-23T12:04:51 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20656 <pre>https://issues.apache.org/bugzilla/show_bug.cgi?id=55011 Bug ID: 55011 Summary: No new log entries after Rolling Product: Log4j Version: 1.2 Hardware: Sun OS: Solaris Status: NEW Severity: major Priority: P2 Component: Appender Assignee: log4j-dev&lt; at &gt;logging.apache.org Reporter: moon3854&lt; at &gt;yandex.ru Classification: Unclassified Logs are not written to new .log file after an old one was rolled by RollingFileAppender. Several messages appear in the new file, with a last entry timestamp nearly identical to log.gz file creation time and that is all. Logging resumes after tomcat restart. This only happens to server.log file, specified in config below. Others work fine. Log4j version - 1.2.16 Tomcat version - 7.0.23 Log4j config: &lt;log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false"&gt; &lt;!-- File Appender --&gt; &lt;appender name="FILE" class="org.apa</pre> bugzilla< at >apache.org 2013-05-23T12:03:59 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20655 <pre>never did that, but the url looks like it should be: https://issues.apache.org/jira/browse/LOG4J2 On Wed, May 22, 2013 at 8:58 PM, manyofh &lt;manyofh&lt; at &gt;googlemail.com&gt; wrote: </pre> Christian Grobmeier 2013-05-23T04:55:46 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20654 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13664617#comment-13664617 ] Edward Sargisson edited comment on LOG4J2-254 at 5/22/13 10:28 PM: ------------------------------------------------------------------- This code doesn't work the second time the file rolls. I get the following stack trace: 2013-05-22 22:24:09,522 ERROR Unable to write to stream /var/log/flume-ng/flume.log for appender RollingFile 2013-05-22 22:24:09,522 ERROR An exception occurred processing Appender RollingFile org.apache.logging.log4j.core.appender.AppenderRuntimeException: Error flushing stream /var/log/flume-ng/flume.log at org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:150) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:115) at org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFi</pre> Edward Sargisson (JIRA 2013-05-22T22:30:20 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20653 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Sargisson reopened LOG4J2-254: ------------------------------------- This code doesn't work the second time the file rolls. I get the following stack trace: 2013-05-22 22:24:09,522 ERROR Unable to write to stream /var/log/flume-ng/flume.log for appender RollingFile 2013-05-22 22:24:09,522 ERROR An exception occurred processing Appender RollingFile org.apache.logging.log4j.core.appender.AppenderRuntimeException: Error flushing stream /var/log/flume-ng/flume.log at org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:150) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:115) at org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:84) at org.apache.logging.log4j.core.config.AppenderControl.callAppender(Appender</pre> Edward Sargisson (JIRA 2013-05-22T22:28:21 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20652 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Sargisson updated LOG4J2-254: ------------------------------------ Priority: Blocker (was: Major) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Edward Sargisson (JIRA 2013-05-22T22:28:22 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20651 <pre>Hi, I am trying to set up the issue track from log4j2 as a task repository in my eclipse. But I am not able to do this. I am using the JIRA connector (atlassian 3.13) with the url http://issues.apache.org/jira/browse/LOG4J2-10. I am getting only the information "Server Error: (303) Found". It looks like that there is no service for this feature. Has somebody already tried to do this? Or has some information about this topic? Regards, Andreas </pre> manyofh 2013-05-22T18:58:41 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20650 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13663867#comment-13663867 ] Remko Popma commented on LOG4J2-228: ------------------------------------ Hi Imesh, I am in a similar situation as Ralph, work has been very busy for me the last few weeks. (But no holiday planned :-) The quickest way to get this fixed may be to submit a patch... -Remko -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Remko Popma (JIRA 2013-05-22T06:55:23 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20649 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13663867#comment-13663867 ] Remko Popma edited comment on LOG4J2-228 at 5/22/13 6:55 AM: ------------------------------------------------------------- Hi Imesh, I am in a similar situation as Ralph, work has been very busy for me the last few weeks. (But no holiday planned :-( ) The quickest way to get this fixed may be to submit a patch... -Remko was (Author: remkop&lt; at &gt;yahoo.com): Hi Imesh, I am in a similar situation as Ralph, work has been very busy for me the last few weeks. (But no holiday planned :-) The quickest way to get this fixed may be to submit a patch... -Remko -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Remko Popma (JIRA 2013-05-22T06:55:23 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20648 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13663835#comment-13663835 ] Imesh Damith commented on LOG4J2-228: ------------------------------------- Hi Ralph, I understand you. Is there anyone else who can help me? Ramko can't help me? -Imesh -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Imesh Damith (JIRA 2013-05-22T06:21:21 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20647 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13663786#comment-13663786 ] Ralph Goers commented on LOG4J2-223: ------------------------------------ 1. JNDIContextSelector implements the NamedContextSelector interface. In theory, JNDIContextFilter can work on any NamedContextSelector so I guess it really should be named NamedContextFilter. 2. If the context isn't found in the ThreadLocal then JNDIContextSelector performs a JNDILookup to locate the context. Using the ThreadLocal avoids the need to do the JNDI lookup, which is much more expensive. 3. Both should work fine if they are used together. Log4jContextListener will get control during web app deployment and set the context as a ServletContext attribute. On each request JNDIContextFilter will get the context from the attribute and store it in a ThreadLocal. Note that all the apps where I work run in JBoss 5, which doesn't support web-fragment.xml as far a</pre> Ralph Goers (JIRA 2013-05-22T05:16:20 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20646 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-264. ---------------------------------- Resolution: Fixed Fix Version/s: 2.0-beta7 Resolved with r1485032. Please verify and close. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Nick Williams (JIRA 2013-05-22T02:31:20 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20645 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13663694#comment-13663694 ] Nick Williams commented on LOG4J2-264: -------------------------------------- Note: The maven-taglib-plugin is _supposed_ to flag issues like this. However, the generated report is all green checkboxes. It does not flag the fact that the attribute does not have a setter. I have filed http://jira.openmindlab.com/browse/MAVENTAGLIB-16 about this. Also, I have filed a featured request for the maven-taglib-plugin to be able to run it at compile time and fail the build if validation fails. http://jira.openmindlab.com/browse/MAVENTAGLIB-17 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Nick Williams (JIRA 2013-05-22T02:23:20 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20644 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13663650#comment-13663650 ] Nick Williams commented on LOG4J2-223: -------------------------------------- Ralph, My bad, I typoed. Meant to say the sample WAR was compiled with Java 7, not Java 6. If someone could respond to my analysis in the comment immediately above and let me know if my assumptions are correct and what the answers to my questions are, I'd be in a good position to make some recommendations about how I think this could all be improved, vis-à-vis {{web-fragment.xml}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Nick Williams (JIRA 2013-05-22T01:16:20 http://permalink.gmane.org/gmane.comp.jakarta.log4j.devel/20643 <pre> [ https://issues.apache.org/jira/browse/LOG4J2-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Sargisson closed LOG4J2-261. ----------------------------------- Verified by source inspection. Closing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Edward Sargisson (JIRA 2013-05-21T16:35:16 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.jakarta.log4j.devel