Re: [jetty-users] Changing the log level for fatal Exceptions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [jetty-users] Changing the log level for fatal Exceptions

From: Travis Spencer <travislspencer@xxxxxxxxx>
Date: Thu, 26 Jan 2017 20:36:23 +0000
Delivered-to: jetty-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jetty-users>
List-help: <mailto:jetty-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=unsubscribe>

On Thu, Jan 26, 2017 at 10:28 AM Channing Walton <channingwalton@xxxxxxx> wrote:

Is there anyway I can arrange errors like OOM errors to be logged at ERROR level?

You can use log4j2's rewrite appender https://logging.apache.org/log4j/2.x/manual/appenders.html#RewriteAppender. We do that for a few components, not Jetty itself, but libs we use in the app Jetty hosts. Would work the same way though, and doesn't require any code changes, only config. If you go this route, be aware of these "bugs" in the docs at that link https://issues.apache.org/jira/browse/LOG4J2-1381

--

Regards,

Travis Spencer

References:
- [jetty-users] Changing the log level for fatal Exceptions
  - From: Channing Walton

Prev by Date: Re: [jetty-users] Changing the log level for fatal Exceptions
Next by Date: Re: [jetty-users] "early EOF" warning when https call from old application in 9.2.9.v2015022er
Previous by thread: Re: [jetty-users] Changing the log level for fatal Exceptions
Next by thread: [jetty-users] http2 client - push promise question
Index(es):
- Date
- Thread

Back to the top