PrintStackTrace not appearing in application.log?

Question

We are having a difficult time locating the Stack Traces that we expected to see in the application.log of our J2EE Web Applications. Within our servlets the typical try/catch sequence is something like:
try {
// do some stuff that can throw an exception
} catch(Exception ex) {
ex.printStackTrace();
ErrorBean errorBean = new ErrorBean(
(ex.getMessage()!=null) ? ex.getMessage() : ex.getClass().getName(),
request.getRequestURI(),ex);
// Push ErrorBean into request scope for forward to Error Handler
request.setAttribute(Constants.ERROR_KEY,errorBean);
return (mapping.findForward("unexpectedError"));
However, we can't find the output from the ex.printStackTrace() anywhere. It doesn't appear to be laying in the application.log. Any ideas? Is there something we should configure somewhere to send the stacktraces to application.log?
Arghh....any help would be greatly appreciated.
Bob
Bob

Answer 1

Ah...yes...they were right where you said they would be. However, is there some configuration that I could do to put the console messages (System.out.println() and, more importantly for us, ex.printStackTrace()) in the global-application.log so we would at least get some concept of the time of the exceptions? As it stands now we can see the actual exceptions in a file named after our OC4J instances (./ora9ias/opmn/logs/camsu.default_island.1) and some logging stuff with Timestamps from the Struts framework in the file the application.xml sends it to(<file path="../log/global-application.log"/>) but it is difficult to match the exceptions up with the servlet requests that caused them due, mainly, to lack of timestamps. Is there a way to get the stuff that presently goes to the opmn/logs file into the global-application.log?
Regardless, I will definitely follow up the the Log4J stuff. Maybe that's where the magic bullet is. Thanks so much for your reply. This was giving me fits.
Bob