[
https://issues.apache.org/jira/browse/FINERACT-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212017#comment-17212017
]
Michael Vorburger commented on FINERACT-1199:
---------------------------------------------
Actually this should ideally also cover Tomcat's own logs, such as this:
{noformat}
Oct 11, 2020 8:14:07 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-nio-8080"]
Oct 11, 2020 8:14:07 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["https-jsse-nio-8443"] {noformat}
I wonder if just adding jcl-over-slf4j.jar (see
[http://www.slf4j.org/legacy.html]) is all we are missing here? Worth a try...
> Jersey (JAX RS implementation) & Tomcat logging needs to be configured to use
> slf4j instead of JUL
> --------------------------------------------------------------------------------------------------
>
> Key: FINERACT-1199
> URL: https://issues.apache.org/jira/browse/FINERACT-1199
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Michael Vorburger
> Priority: Major
>
> Fineract uses slf4j with logback, but Jersey (JAX RS implementation) doesn't
> dig that. It ideally should, as that would lead to nicer and more unified
> logging. Specifically, fixing this would make all of these kinds of logs:
> {code:java}
> Oct 11, 2020 8:14:08 PM
> com.sun.jersey.spi.spring.container.SpringComponentProviderFactory
> registerSpringBeans
> INFO: Registering Spring bean, accrualAccountingApiResource, of type
> org.apache.fineract.accounting.accrual.api.AccrualAccountingApiRe
> source as a root resource class {code}
> looks more like most of the other log messages, e.g. this one et al:
> {code:java}
> 2020-10-11 20:14:07.934 INFO 198000 --- [ main]
> o.s.b.a.e.web.EndpointLinksResolver : Exposing 2 endpoint(s) beneath b
> ase path '/actuator {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
