Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7CE9510F78 for ; Fri, 5 Jun 2015 13:40:24 +0000 (UTC) Received: (qmail 22114 invoked by uid 500); 5 Jun 2015 13:40:24 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 22074 invoked by uid 500); 5 Jun 2015 13:40:24 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 22062 invoked by uid 99); 5 Jun 2015 13:40:23 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jun 2015 13:40:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 5F766C08D9 for ; Fri, 5 Jun 2015 13:40:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.099 X-Spam-Level: X-Spam-Status: No, score=-0.099 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id gXe7-JvkymdX for ; Fri, 5 Jun 2015 13:40:14 +0000 (UTC) Received: from mail-la0-f45.google.com (mail-la0-f45.google.com [209.85.215.45]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id AC3CF20C4B for ; Fri, 5 Jun 2015 13:40:13 +0000 (UTC) Received: by laew7 with SMTP id w7so54494528lae.1 for ; Fri, 05 Jun 2015 06:40:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=i8sFoTYhVMYL49zYE11hR9kk24gCnoE1vVAyNP2mBBg=; b=Jtsp8nkAihP4l5L1rrSR+rpfiLGm92FQxToWFzcjXf0GyiRauef7MhlTKoAojWSMId jsZtJHiWOTV5boJ+hcORtWOvKewNCHf5cZd2IPvLktweMLRjTiwSsifG+0IF5TKWhka7 ulLS6jC9ugHds8nA5eaKLtQrzVziOhxkVzKCWQWheqLQSgAal+hx6iH68z6WXlS4xVJ4 gMaMaizQblQIyHNl+sVL945RKVrrcnr0MjpcYowf3PPRwIfwxtsJ8COxSWGuNaRjkV6g eGV2qZIdQk1zAxoB27KNgouFW6I6+ItAmcj2o5l8+nQRWWAymjxxj+AbNA6I1qQbG7i6 JiCA== MIME-Version: 1.0 X-Received: by 10.112.199.10 with SMTP id jg10mr3436272lbc.24.1433511613029; Fri, 05 Jun 2015 06:40:13 -0700 (PDT) Received: by 10.152.115.165 with HTTP; Fri, 5 Jun 2015 06:40:12 -0700 (PDT) In-Reply-To: References: Date: Fri, 5 Jun 2015 14:40:12 +0100 Message-ID: Subject: Re: Tracing ActiveMQ requests... From: Gary Tully To: "users@activemq.apache.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable have you run with trace=3Dtrue on the transport urls. this will log4j trace each openwire command on a per connection logger so that you can at least identify the actual command that is taking time. connection creation. producer creation, message send etc. On 30 May 2015 at 00:06, Kevin Burton wrote: > I=E2=80=99m trying to track down performance issues for our broker. > > I wrote a quick stopwatch around sending messages and it=E2=80=99s taking= 2-6 > seconds to send requests to ActiveMQ. > > I have NO idea why this could be because I have reasonable CPU on this bo= x > and what could be happening. Our broker runs out of memory, no disk is > involved, plenty of CPU and network, etc. > > It would be nice if we had more tracing support in ActiveMQ. > > If you=E2=80=99ve ever used Cassandra=E2=80=99s tracing support you=E2=80= =99ll know what I=E2=80=99m > talking about > > ALA dapper-style tracing. > > http://research.google.com/pubs/pub36356.html > > Essentially it would track each step that could potentially take time and > print them out as they happen. > > Maybe one way this could be accomplished is to send messages to a dedicat= ed > queue for each trace attempt? > > Either that or log the trace in the log file. > > This would NOT be log4j tracing.. which are just log lines. This would b= e > a list of events and timings. > > Maybe this would be better to add to ActiveMQ 6.0 though.. but I guess we > can figure it out as time goes by. > > Thoughts? > > -- > > Founder/CEO Spinn3r.com > Location: *San Francisco, CA* > blog: http://burtonator.wordpress.com > =E2=80=A6 or check out my Google+ profile >