[jira] [Commented] (LOG4J2-703) Android: Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

[ https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057365#comment-14057365 ] Nelson MELINA commented on LOG4J2-703: -- [~garydgregory] How can i download the code f

[jira] [Comment Edited] (LOG4J2-703) Android: Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

[ https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057365#comment-14057365 ] Nelson MELINA edited comment on LOG4J2-703 at 7/10/14 10:59 AM:

[jira] [Commented] (LOG4J2-703) Android: Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

[ https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057368#comment-14057368 ] Andreas Opitz commented on LOG4J2-703: -- Nelson MELINA look at this page http://loggin

[jira] [Comment Edited] (LOG4J2-703) Android: Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

[ https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057368#comment-14057368 ] Andreas Opitz edited comment on LOG4J2-703 at 7/10/14 11:06 AM:

[jira] [Updated] (LOG4J2-706) InvocationTargetException with RollingFileAppender in Log4J2

[ https://issues.apache.org/jira/browse/LOG4J2-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-706: --- Description: I'm trying to use a RollingFileAppender in Log4J2 and apparently I'm missing something.

[jira] [Assigned] (LOG4J2-706) InvocationTargetException with RollingFileAppender in Log4J2

[ https://issues.apache.org/jira/browse/LOG4J2-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-706: -- Assignee: Remko Popma > InvocationTargetException with RollingFileAppender in Log4J2 >

[jira] [Commented] (LOG4J2-706) InvocationTargetException with RollingFileAppender in Log4J2

[ https://issues.apache.org/jira/browse/LOG4J2-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058053#comment-14058053 ] Remko Popma commented on LOG4J2-706: The class at the beginning of the stack trace {{

[jira] [Resolved] (LOG4J2-706) InvocationTargetException with RollingFileAppender in Log4J2

[ https://issues.apache.org/jira/browse/LOG4J2-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-706. Resolution: Not a Problem Marking this ticket as "Not a problem". Please feel free to re-open if th

[jira] [Commented] (LOG4J2-705) Async logger loses thread context stack for events

[ https://issues.apache.org/jira/browse/LOG4J2-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058062#comment-14058062 ] Remko Popma commented on LOG4J2-705: Can you please post the full contents of your log

[jira] [Assigned] (LOG4J2-700) MyBatis 3.2.7 gives "java.lang.ClassNotFoundException: org.apache.logging.log4j.spi.AbstractLoggerWrapper" with log4j-2.0-rc2

[ https://issues.apache.org/jira/browse/LOG4J2-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-700: -- Assignee: Remko Popma > MyBatis 3.2.7 gives "java.lang.ClassNotFoundException: > org.apache.lo

[jira] [Resolved] (LOG4J2-700) MyBatis 3.2.7 gives "java.lang.ClassNotFoundException: org.apache.logging.log4j.spi.AbstractLoggerWrapper" with log4j-2.0-rc2

[ https://issues.apache.org/jira/browse/LOG4J2-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-700. Resolution: Won't Fix Resolving this ticket as "Won't fix": the problem will be addressed in the ne

[jira] [Closed] (LOG4J2-700) MyBatis 3.2.7 gives "java.lang.ClassNotFoundException: org.apache.logging.log4j.spi.AbstractLoggerWrapper" with log4j-2.0-rc2

[ https://issues.apache.org/jira/browse/LOG4J2-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-700. -- > MyBatis 3.2.7 gives "java.lang.ClassNotFoundException: > org.apache.logging.log4j.spi.AbstractLoggerWrap

[jira] [Commented] (LOG4J2-702) LoggerConfig#waitForCompletion is not thread safe

[ https://issues.apache.org/jira/browse/LOG4J2-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058141#comment-14058141 ] Remko Popma commented on LOG4J2-702: I think I agree with Sean's analysis. There is a

[jira] [Created] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

Matt Sicker created LOG4J2-708: -- Summary: Servlet filter claims to support async but doesn't use AsyncContext Key: LOG4J2-708 URL: https://issues.apache.org/jira/browse/LOG4J2-708 Project: Log4j 2

[jira] [Assigned] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker reassigned LOG4J2-708: -- Assignee: Matt Sicker > Servlet filter claims to support async but doesn't use AsyncContext > -

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058211#comment-14058211 ] Matt Sicker commented on LOG4J2-708: Actually, now that I look deeper at this, I don't

[jira] [Updated] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-708: --- Issue Type: Question (was: Bug) > Servlet filter claims to support async but doesn't use AsyncContex

[jira] [Commented] (LOG4J2-412) RollingRandomAccessFile appender loses output when fileName/filePattern accesses ${sys:property}

[ https://issues.apache.org/jira/browse/LOG4J2-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058250#comment-14058250 ] Remko Popma commented on LOG4J2-412: Sorry for getting back to you so late. I believe

[jira] [Updated] (LOG4J2-524) Feature request: auto-delete older rolled over files

[ https://issues.apache.org/jira/browse/LOG4J2-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-524: --- Issue Type: Improvement (was: Bug) Summary: Feature request: auto-delete older rolled over fil

[jira] [Resolved] (LOG4J2-593) INFO: Illegal access: this web application instance has been stopped already.

[ https://issues.apache.org/jira/browse/LOG4J2-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-593. Resolution: Incomplete Resolving this issue as "Incomplete" because of lack of response from the is

Re: svn commit: r1609602 - /logging/log4j/log4j2/trunk/log4j-core/src/main/java/org/apache/logging/log4j/core/lookup/Interpolator.java

Or should we catch Exception and VerifyError, but not Throwable? Gary On Thu, Jul 10, 2014 at 9:26 PM, wrote: > Author: mattsicker > Date: Fri Jul 11 01:26:18 2014 > New Revision: 1609602 > > URL: http://svn.apache.org/r1609602 > Log: > Catch Throwable here to handle VerifyError. > > Modified:

Re: svn commit: r1609602 - /logging/log4j/log4j2/trunk/log4j-core/src/main/java/org/apache/logging/log4j/core/lookup/Interpolator.java

I think catching Throwable is fine. It is better for the user if all Errors here are trapped and handled IMO. Sent from my iPhone > On 2014/07/11, at 11:48, Gary Gregory wrote: > > Or should we catch Exception and VerifyError, but not Throwable? > > Gary > > >> On Thu, Jul 10, 2014 at 9:2

[jira] [Updated] (LOG4J2-569) Configuring RollingRandomAccessFile with HTMLLayout does not work as expected

[ https://issues.apache.org/jira/browse/LOG4J2-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-569: --- Description: I'm trying to configure a rolling file appender to work with HTMLLayout: {code}

[jira] [Resolved] (LOG4J2-569) Configuring RollingRandomAccessFile with HTMLLayout does not work as expected

[ https://issues.apache.org/jira/browse/LOG4J2-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-569. Resolution: Fixed Fix Version/s: 2.0-rc2 I believe this issue was fixed as part of LOG4J2-67

[jira] [Updated] (LOG4J2-612) Reduce log4j2 initialization time: consider reusing PatternParser in RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-612: --- Summary: Reduce log4j2 initialization time: consider reusing PatternParser in RollingFileAppender (w

[jira] [Resolved] (LOG4J2-626) ThreadContext for Asynchronous logger in multithreaded environmant is overwriting the values.

[ https://issues.apache.org/jira/browse/LOG4J2-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-626. Resolution: Not a Problem Resolving this issue as Not a Problem. Please feel free to reopen if requ

[jira] [Resolved] (LOG4J2-441) logger level configuration does not work correct

[ https://issues.apache.org/jira/browse/LOG4J2-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-441. Resolution: Fixed Fix committed in revision 1609639. Please verify and close. > logger level confi

Next release

I would like to do the release for Log4j 2.0 this weekend. Are there any objections? Ralph - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org