cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Johansson (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CXF-7389) JAXRSUtils warning logs
Date Thu, 01 Jun 2017 15:07:04 GMT

    [ https://issues.apache.org/jira/browse/CXF-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033122#comment-16033122
] 

Anton Johansson edited comment on CXF-7389 at 6/1/17 3:06 PM:
--------------------------------------------------------------

I had to enable DEBUG-logging to see anything related to Jetty, and this is the only log related
to the 404:

2017-06-01 17:03:58,839 | DEBUG | on-existing-path | Server                           | 47
- org.eclipse.jetty.aggregate.jetty-all-server - 8.1.16.v20140903 | RESPONSE /non-existing-path
 404 handled=true


was (Author: anton-johansson):
I had to enable DEBUG-logging to see anything related to Jetty, and this is the only log related
to the 404:

2017-06-01 17:03:58,839 | DEBUG | urrentversionasd | Server                           | 47
- org.eclipse.jetty.aggregate.jetty-all-server - 8.1.16.v20140903 | RESPONSE /non-existing-path
 404 handled=true

> 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)

Mime
View raw message