-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Guillaume,
On 2/27/2009 3:23 PM, Guillaume Cauchon wrote: > However we realized the logging configuration doesn't seams to be > working the same way! The same webapp running on 5.5 and 6 doesn't > produce the same amount of logging: everything that was produced by the > JspServlet (Servlet API) is missing now; and I guess a lot more is also > missing, but we didn't saw it yet... > > The logging is based on log4j, using a xml configuration file. We are > using DOMConfigurator to intitialise and monitor the log4j configuration > which can be modified at runtime. So, are you talking about application logging or Tomcat internal logging? You mentioned the JspServlet, but any logging performed by that servlet (that is, the actual log messages) is not part of the servlet API. If you use ServletContext.log(...) you aren't guaranteed (in fact, you are very unlikely) to use your application's logging mechanism. > I know the Common Logging if the basis of the whole logging architecture > in tomcat, is there something I need to know about the tomcat 6 release > that might be related to this issue? I'm not sure if there is an appreciable difference between logging configuration in Tomcat 5.5 and 6.0. Can you tell us what you expected and what actually happens? No log files created? No log messages generated? Log level is different than expected? You didn't give any real details except for "we upgraded and now it doesn't work". :( - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmsEdoACgkQ9CaO5/Lv0PCenACfdCDcRqYAjyriSFLCNYDA0gIG tawAn1JeKcALyKvKBHZg7D++m4kofbvi =WSiR -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
