David,
Does your own application have a log4j.properties file which might
override logging so it isn't directed to stdout?
Just to be sure it isn't a problem in Tomcat, you could try to download
a nightly build of e.g. the tomahawk-examples and try to deploy it. If
you deploy e.g. myfaces-examples-simple and afterwards create a JSF EL
error in one of the pages, it creates both a custom error page
(error.jsp in the same war file, if you want to try it on your own
application) and logging entries in Tomcat's localhost_xxxxxxx.log file
on my machine.
Regards,
Gert Vanthienen
[EMAIL PROTECTED]
David Delbecq wrote:
Logging output goes to stdout, all output during webapp startup and
normal operations seems to get out to stdout without problem, when in
debug mode, all debug message of all libraries go to stdout without
problem, the only thing that is not showing is the reason of those 500
error (in the previous case i hunted it down to a typo in a JSF EL in
the jsp).
There is no conf/logging.properties, there is no logger entry in the
context.xml. The logging is done using log4j.
Gert Vanthienen a écrit :
David,
We have several JSF applications (using MyFaces) in production, but I
don't remember having seen this type of problem. Are you sure there
are not stacktraces in any of the Tomcat log files? On our
installation, these messages usually appear in stdout_xxxxxxxx.log.
If none of the log files holds the message details, is there any
special logging configuration in Tomcat's conf/logging.properties file
or in the context.xml (e.g. <Logger/> elements in Tomcat 5.0)?
Regards,
Gert Vanthienen
[EMAIL PROTECTED]
David Delbecq wrote:
Hello,
When developping with myface, i get on a regular basis an "error 500"
message coming from tomcat, however, neither in console, not in web page
is there any reason for the error (not stack trace, no message), only an
"internal server error". I have set the log level of myfaces to debug,
but all i get in console is
616505 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG
org.apache.catalina.session.ManagerBase - Start expire sessions
StandardManager at 1157100966186 sessioncount 0
616505 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG
org.apache.catalina.session.ManagerBase - End expire sessions
StandardManager processingTime 0 expired sessions: 0
currently, i know it's an error in my jsp, as commenting the new section
remove the error, however , i don't get any clue from myface of what the
error is. Is it a myface bug not to set the reason of error before
sending a 500, or could it be the tomcat fault (as far as i'm concerned,
when i do non JSF related errors in my jsp, i get a stacktrace from
tomcat). It's really a pain to develop blindly like that. Is there a way
to get more informations from myfaces errors??
