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 8AC39200C84 for ; Mon, 29 May 2017 16:06:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 89436160BCE; Mon, 29 May 2017 14:06: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 D0780160BC2 for ; Mon, 29 May 2017 16:06:06 +0200 (CEST) Received: (qmail 28904 invoked by uid 500); 29 May 2017 14:06:06 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 28887 invoked by uid 99); 29 May 2017 14:06:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 May 2017 14:06:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id AEB33180533 for ; Mon, 29 May 2017 14:06:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id bWbvz8VdFoP1 for ; Mon, 29 May 2017 14:06:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D75935FD8E for ; Mon, 29 May 2017 14:06:04 +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 5CC40E0A75 for ; Mon, 29 May 2017 14:06:04 +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 151DF2193C for ; Mon, 29 May 2017 14:06:04 +0000 (UTC) Date: Mon, 29 May 2017 14:06:04 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CAMEL-11360) Disable Tracer and use BacklogTracer instead MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 29 May 2017 14:06:07 -0000 Claus Ibsen created CAMEL-11360: ----------------------------------- Summary: Disable Tracer and use BacklogTracer instead Key: CAMEL-11360 URL: https://issues.apache.org/jira/browse/CAMEL-11360 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.20.0 See CAMEL-11359 We have the old tracer logic that is cruft. Its still capturing tracing details during runtime, but that is obsolete with the message history we use instead (eg the stuff that also dumps those route stacktrace errors). So if users say camelContext.setTracing(true) we can then use BacklogTracer instead to log similar trace events. This allows us to not capture 2x trace details during routing as message history will be used for both. -- This message was sent by Atlassian JIRA (v6.3.15#6346)