Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 43F0C200CE1 for ; Thu, 31 Aug 2017 14:52:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 427B916B081; Thu, 31 Aug 2017 12:52:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8AB8616B086 for ; Thu, 31 Aug 2017 14:52:06 +0200 (CEST) Received: (qmail 51108 invoked by uid 500); 31 Aug 2017 12:52:05 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 50842 invoked by uid 99); 31 Aug 2017 12:52:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Aug 2017 12:52:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C69D4C7CD3 for ; Thu, 31 Aug 2017 12:52:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id h3-zOp-QFG3o for ; Thu, 31 Aug 2017 12:52:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 635115F21F for ; Thu, 31 Aug 2017 12:52:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 0BD1BE0DCA for ; Thu, 31 Aug 2017 12:52:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 54EC424158 for ; Thu, 31 Aug 2017 12:52:00 +0000 (UTC) Date: Thu, 31 Aug 2017 12:52:00 +0000 (UTC) From: "Sergey Beryozkin (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CXF-7389) JAXRSUtils warning logs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 31 Aug 2017 12:52:07 -0000 [ https://issues.apache.org/jira/browse/CXF-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16148938#comment-16148938 ] Sergey Beryozkin commented on CXF-7389: --------------------------------------- I've updated the code to log the client errors at the fine level, which can be further customized by reg a ClientErrorException.class.getName() + ".log.level" property > 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.4.14#64029)