Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I suspect a thread created by a third-party jar used by my web application may be throwing an exception, and not catching it. However, I don’t see any evidence of this in the log files. How can I force all uncaught exceptions to be dumped to a log file? This is for a web app running inside Glassfish.
It turns out that this is not necessary with Glassfish, because Glassfish already does it – but I was looking at the wrong place in the logs.
The exception was printed to the main
server.logfile – not to my application’s own log4j log file.