Write yourself a Servlet Filter [1] that catches any exception, logs it, and passes it on. Your logger should be configured to write to a file. If the filter is the first in the chain, the exception caught is definitely unhanded.
PS: If you don't pass on the exception, you have handled it (by definition). The container will think everything is fine if you don't. [1] https://docs.oracle.com/javaee/6/api/javax/servlet/Filter.html Cheers, Paul On Tue, May 3, 2016 at 2:04 PM, v yang <vpy...@hotmail.com> wrote: > Is there no alternative to this? I really do not want to add a catch to > anything at all. > > vpyang > > ________________________________________ > From: Ralph Goers <ralph.go...@dslextreme.com> > Sent: Tuesday, May 3, 2016 11:54 AM > To: Log4J Users List > Subject: Re: uncaught exception with log4j2 > > All you need is to catch the exceptions by doing: > > try { > } catch (Exception ex) { > logger.error(“Uncaught exception:”, ex); > } > > You would put this in your servlet, Controller or whatever the first thing > in your application is that gets control from Tomcat. > > If you want to treat them specially then add a Marker to the error method. > > Ralph > > > > On May 3, 2016, at 9:29 AM, v yang <vpy...@hotmail.com> wrote: > > > > Hello list, > > > > > > I'm looking for a way to log any uncaught exceptions to a file. I'm > currently running Wildfly 9.0.2 server and all uncaught exceptions are > printing to console. I'd like to use log4j2 log those exceptions. Can > anyone point me in the right direction. > > > > > > vpyang > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > >
