No, the bug only affects ViewStatusMessagesServlet, not the console.
On 16.11.2011 13:18, Yuvaraj Vanarase wrote:
Hello Ceki, It would be great if you provide confirmation for your answer below: /There is a serious bug in AccessViewStatus servlet. That is probably/ /why you are seeing the 'Could not find status manager' message which/ /will be fixed with the logback next release./ Does this also cause the logback-access initialization logs to be absent on console? I mean I wouldn’t able to see something like: /21:56:09,921 |-INFO in c.q.lb.access.j.a.ConfigurationAction - Ignoring debug attribute. 21:56:09,921 |-INFO in c.q.lb.core.j.a.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 21:56:09,921 |-INFO in c.q.lb.core.j.a.AppenderAction - Naming appender as [STDOUT] 21:56:10,000 |-INFO in c.q.lb.core.j.a.NestedComponentIA - Pushing component [layout] on top of the object stack. 21:56:10,015 |-INFO in c.q.lb.core.j.a.AppenderAction - Popping appender named [STDOUT] from the object stack 21:56:10,015 |-INFO in c.q.lb.core.j.a.AppenderRefAction - Attaching appender named [STDOUT] to ch.qos.logback.access.tomcat.LogbackValve[Catalina] 21:56:10,015 |-INFO in c.q.lb.access.j.a.ConfigurationAction - End of configuration./ Because apart from status manager issue, I do not see above initialization log either. Regards, Yuvaraj *Date: Wed, 16 Nov 2011 08:02:14 +0100* *From: Ceki Gulcu <[email protected]>* *To: logback users list <[email protected]>* *Subject: Re: [logback-user] Using logback access* *Message-ID: <[email protected]>* *Content-Type: text/plain; charset=windows-1252; format=flowed* Hello Yuvaraj, Responses inline. On 16.11.2011 07:05, Yuvaraj Vanarase wrote: > Hi, > > I have 2 questions. > > 1. What is logback access exactly. Is it about providing webserver > request information in terms of log. Doesn?t such facility come with web > server itself? (catalina.log for tomcat etc) Yes, web-containers already support access logging. Logback-access provides the same functionality but in addition logback-access is more flexible with much better filtering and rolling capabilities. > 2. I am trying to use logback access with Tomcat, however just not > getting there. It would be great if someone points out any miss-outs. > > Below are details: > > -Tomcat 6.0.33 > > -Logback core 0.9.30 > > -Logback access 0.9.30 > > I have put above logback jars into tomcat jar directory. I have added > ?Valve? configuration in server.xml and as required put the > logback-access.xml in conf directory of tomcat. I referred > http://logback.qos.ch/access.html > > My webapp has single simple servlet that just prints login name on page > which has been input from html login form. This works well however I do > not see any logback initialization logs. When I query > ?AccessViewStatusMessages?, again I do not see any messages except one > *?Could not find status manager?* There is a serious bug in AccessViewStatus servlet. That is probably why you are seeing the 'Could not find status manager' message which will be fixed with the logback next release. > Yuvaraj ------------------------------ _______________________________________________ Logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user End of Logback-user Digest, Vol 2, Issue 32 ******************************************* _______________________________________________ Logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user
_______________________________________________ Logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user
