[
https://issues.apache.org/jira/browse/CXF-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032935#comment-16032935
]
Sergey Beryozkin commented on CXF-7389:
---------------------------------------
At what level say Tomcat reports 404 in its logs without CXF even being
involved ?
> JAXRSUtils warning logs
> -----------------------
>
> Key: CXF-7389
> URL: https://issues.apache.org/jira/browse/CXF-7389
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Reporter: Anton Johansson
> Priority: Minor
>
> We're running a REST API service using CXF. We've got a dashboard with all
> warning and error logs that we frequently use, and this dashboard includes
> 404's that clients get when communicating with our API. We do not log WARN or
> ERROR any other errors from the 400-series, because it's in theory the
> clients fault and we can't do anything about it. We have now decided that we
> want to stop logging WARN for these 404's.
> Our issue: We don't see any possible way to disable this log (or preferably
> change it to INFO). It's logged from a static class, JAXRSUtils, see this
> line:
> http://grepcode.com/file/repo1.maven.org/maven2/org.apache.cxf/cxf-bundle-jaxrs/2.7.6/org/apache/cxf/jaxrs/utils/JAXRSUtils.java#501
> We could of course change the threshold to ERROR for this class, but I don't
> want to lose the other INFO and WARN logs.
> I understand that this warning is great for clients, but I don't see it being
> very useful for servers?
> Any tips or ideas about how we can disable this warning?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)