Sorry I didn't understand your message Matt. If your message is meant for Bryan, could you add a comment to the JIRA ticket? I doubt he is on this list. Or is JIRA bridge something that automatically creates a JIRA comment when you reply to an email?
Which class produces the "Unable to locate ServletContext" status logger message? I did a search but I cannot find it. Is this not some remnant of pre-refactoring code that still expects web stuff to exist in core? Finally, Bryan is right, java/org/apache/logging/log4j/core/net/SocketServer is gone (it used to be in log4j-core). Does anyone know what happened to it? On Tue, May 6, 2014 at 7:54 AM, Matt Sicker <boa...@gmail.com> wrote: > JIRA bridge still isn't set up right? Anyway, I fixed that error message > the other day. I changed it to info IIRC as it's not super relevant other > than to mention you can't use the WebLookup plugin. > > > On Monday, 5 May 2014, Bryan Hsueh (JIRA) <j...@apache.org> wrote: > >> >> [ >> https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989899#comment-13989899] >> >> Bryan Hsueh commented on LOG4J2-628: >> ------------------------------------ >> >> Tested, and works, thanks. I see this message log 7 times at the start >> though, "ERROR StatusLogger Unable to locate ServletContext". Does this >> have to do with my build process? Likewise, I can no longer find >> SocketServer. I pulled your revision from github and followed the build >> instructions. >> >> > Cannot set log4j.Clock with Async appender >> > ------------------------------------------ >> > >> > Key: LOG4J2-628 >> > URL: https://issues.apache.org/jira/browse/LOG4J2-628 >> > Project: Log4j 2 >> > Issue Type: Question >> > Components: Appenders >> > Affects Versions: 2.0-rc1 >> > Environment: Ubuntu 12.04 / Java 7 >> > Reporter: Bryan Hsueh >> > Assignee: Remko Popma >> > Fix For: 2.0-rc2 >> > >> > >> > I override log4j.Clock to support a "live" time vs a "simulated" time. >> > System.setProperty("log4j.Clock", "teambh.trade.utils.MyClock"); >> > If I use asynchronous loggers, it works fine and calls my >> Clock:currentTimeMillis(). >> > If I switch to async appenders, currentTimeMillis() is not called. >> > Is this expected behavior or a bug? >> > Thanks >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v6.2#6252) >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >> For additional commands, e-mail: log4j-dev-h...@logging.apache.org >> >> > > -- > Matt Sicker <boa...@gmail.com> >
