Larry, Thanks very much for your help! This is invaluable information. Do you know if it would be possible to make Tomcat 3.3a use JspServlet instead of JspInterceptor?
I am using the Tomcat 3.2.1 engine now for our applications and the preformance is acceptable, so I am assuming that if I could make Tomcat 3.3a use the JspServlet the perfomance would be relatively the same. Is that a valid assumption? If there is anyway to do this I would really appreciate the help. Thanks, Tom C. --- Larry Isaacs <[EMAIL PROTECTED]> wrote: > For performance reasons, Tomcat 3.3 uses the > JspInterceptor > module instead of Jasper's JspServlet to translate > and > compile JSP files. Since it was the JspServlet that > was > providing most of the log output for the INFORMATION > level, > you don't see any "jasper" log output when using > JspInterceptor. > If you set the level to DEBUG, you will see some > "jasper" log > output. > > The JspInterceptor sends "Compiling: <file> to ..." > messages > to the context log. Contexts without an assigned > log, as > well as other JspInterceptor messages, go to > Tomcat's log, > which is written to the stderr by default. The > "/examples" > context is assigned to a file so you will see > "Compiling: ..." > messages in logs/examples.log. However, you are not > likely > to see any additional log messages unless there is > an error > or the debug level for JspInterceptor is set > 0. > > Cheers, > Larry > > > > -----Original Message----- > > From: Tomcat Programmer > [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, March 06, 2002 12:36 PM > > To: [EMAIL PROTECTED] > > Subject: strange problem with tomcat version 3.3a > > > > > > I apologize if I sent this twice.. I don't think > it > > went through the first time! > > > > I have been using tomcat for several releases, and > > have just upgraded my server to version 3.3a and I > > have noticed a change in the behavior of the > logging > > mechanism. > > > > With Tomcat 3.3a, nothing gets written to the > > JASPER_LOG stream. I have the verbosityLevel set > to > > INFORMATION, which used to cause all request > > information to get written to this log at release > > 3.2.1. However, now the file is always zero-byte. > It > > does not seem to matter if I define it globally or > > within a specific context. I even changed the > > verbosity level to DEBUG and still *nothing* gets > > written into this file. > > > > I have searched High and Wide over the internet > > looking for the answer to this problem, and I have > not > > been able to find it. > > > > Can anyone help me configure this, please ! > > > > Many Thanks!! > > > > -Tom C. > > > > > > __________________________________________________ > > Do You Yahoo!? > > Try FREE Yahoo! Mail - the world's greatest free > email! > > http://mail.yahoo.com/ > > > > -- > > To unsubscribe: > <mailto:[EMAIL PROTECTED]> > > For additional commands: > <mailto:[EMAIL PROTECTED]> > > Troubles with the list: > <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe: > <mailto:[EMAIL PROTECTED]> > For additional commands: > <mailto:[EMAIL PROTECTED]> > Troubles with the list: > <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
