thanks for the link. I need that too. Regardless of logging thought,
quickly add this to any serlvetlistener
public void contextInitialized(ServletContextEvent evt) {
throw new RuntimeException("asdfsf");
}
Run it, and enjoy not being able to know what the heck went wrong with
your app like I have seen many have done on the posts already. ie.
Tomcat used to log the stack trace, but in 5.5 does not, and that should
be high enough warning level that config of logs don't matter.
Making the problem even harder.....
On a second note, I have fooled around with logging and it works fine in
my app, and I could configure it and such(with 5.5) and my
logging.properties file in WEB-INF. I could never get my
servletlistener to log any statements(making the problem doubly hard).
thanks,
dean
Vamsidhar wrote:
I am assuming you have been using logger to log stack traces in case of
errors in tomcat 5.0. This was deprecated in 5.0 and completely removed in
5.5. So, If you have logger defined for engine, host, or context to record
the stack traces in a file in your application this will not work on tomcat
5.5
http://tomcat.apache.org/tomcat-5.0-doc/config/logger.html
"Please note that Loggers are deprecated in Tomcat 5.0 and removed from
Tomcat 5.5. Tomcat 5.5 uses Commons-Logging instead."
hope this helps.
On 3/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On number 1 5.0 logs the entire stack trace, so you can jump to the line
number. On 5.5, no such stack trace in any file. Also, I searched a few
lists and many people had questions on what was wron when they saw that
error. I think the cause is the lack of information....it should at the
very least log the stack trace and does not.
I just used the latest facelets and it did not work, but worked on 5.0.
in fact, all the stuff works on 5.0 which leads me to believe 5.5 is
unstable, but I wanted to verify.
dean
On 3/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Anyone have much experience with running on these. On tomcat 5.5, I
have
ran into many problems
1. exception fron ServletContextListener.contextInitialized causes the
vague error of "Error listenerStart" with no details. Most people on
lists I have seen don't even know it was caused by Exception out of
that
method(Took me a while to figure out too)
Yes, it's an extremely myterious log message, as a
ServletContextListener is a listener for the context.
2. logging MyFaces logs was not working
Whatever.
3. Facelets example war files don't work in 5.5.16
It uses a bad method for descovering its config, if I remember well,
which is now fixed.
--
xxxxxxxxxxxxxxxxxxxxxxxxx
Rémy Maucherat
Developer & Consultant
JBoss Inc
xxxxxxxxxxxxxxxxxxxxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
