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??
