Hi Steve,

I've found myself on the same situation couple of years ago and to solve my problem I've configured the LoggerProvider to point to Slf4JLoggerProvider. Basically, this can be reproduced by declaring a META-INF/services/org.jboss.logging.LoggerProvider file with org.jboss.logging.Slf4jLoggerProvider as a value.

I hope it helps.

Cheers!

On Mon, Feb 6, 2017 at 9:09 PM Steve Hu <stevehu@gmail.com> wrote:

Hi,

Undertow is using jboss logger to log errors and my application is using slf4j/logback with logback.xml config file in the classpath with Undertow core http server embedded. I handles most exceptions in my own handlers but sometimes uncaught exceptions reaches Connectors class - executeRootHandler method which logs the error and return 500 response code.

My first question: Is there a way to redirect the logs from Undertow to logback logs and controlled by logback.xml? I've found some discussions about replacing logger in WildFly but I am using embedded Undertow core only.

Second question: When Connectors.executeRootHandler will be called? Is it called when you have the following line in your handler?

if (exchange.isInIoThread()) {
     exchange.dispatch(this);
     return;

}

 

Is there any way we can by pass this so that I can handle uncaught exceptions in my ExceptionHandler in the handler chain?

Thanks,

Steve

 

_______________________________________________
undertow-dev mailing list
undertow-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/undertow-dev

--

Miere Teixeira

_______________________________________________
undertow-dev mailing list
undertow-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/undertow-dev