yes, but please look at the solution I found in previous post which
works WITHOUT stripping down everything. I think tomcat should fix this
by reporting something like this
log.log(Level.WARNING, "Application Errors will not be logged because
webapp has log4j but no config file", new RuntimeException("See
msg).fillInStackTrace());
The RuntimeException is to make it more noticeable in the logs. I mean
953 hits on googling is quite alot of people having trouble. Would be
nice to cut that number down with an easy log statement that tomcat
could add!!!
thanks,
dean
Markus Schönhaber wrote:
Dean Hiller wrote:
Okay, a zip file with one *.java file and one *.class file can be found
here...
https://pro40.abac.com/deanhiller/cgi-bin/moin.cgi/Downloads
You can unzip it and copy the folder to tomcat/webapps and watch no
Exception get logged. Just the " Error listenerStart" message gets
logged an no more information is there. Google has 953 references to
"Error listenerStart" and many of them are "what went wrong with my app"
as there is no stack trace. I haven't found any posts answering those
questions though.
If I strip down this webapp to only contain the LifecycleListener - i. e.
remove logging.properties, remove the lib dir, remove filters and listeners
short of LifecycleListener from web.xml - the stacktrace gets logged in
localhost.<date>.log.
Regards
mks
---------------------------------------------------------------------
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]
