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 31644CD3D for ; Tue, 8 May 2012 23:11:59 +0000 (UTC) Received: (qmail 13786 invoked by uid 500); 8 May 2012 23:11:58 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 13751 invoked by uid 500); 8 May 2012 23:11:58 -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 13742 invoked by uid 99); 8 May 2012 23:11:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 May 2012 23:11:58 +0000 X-ASF-Spam-Status: No, hits=-0.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tabish121@gmail.com designates 209.85.216.171 as permitted sender) Received: from [209.85.216.171] (HELO mail-qc0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 May 2012 23:11:50 +0000 Received: by qcsp15 with SMTP id p15so1956739qcs.2 for ; Tue, 08 May 2012 16:11:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:date:in-reply-to:references:content-type :x-mailer:content-transfer-encoding:mime-version; bh=0nJfJFhEHlbvh3g4VjsasV4RsbLv6OGbytU7EYC7lWI=; b=HY1xaiLwAppz5Wxiu+rCC66+YTQaOEYDDATGe5DwuzMdQcNVSV0uRMy1nDsY+RTwoK 03XfdlHsNNCTMGe0NXQ+MXOGV7nnI2JG2ez4J25TfNjrbMnzWK9b9nnD7nA7ffOW7Xwp gLD+UEEn3L3fiHHhJ+QCEedNwbwOoR1v4GHQnIfup7m4NGu23/mhV774eFWqiHOeG5lS pkN2neGkKADF/x2F1YnmpoziJROta9uqBJeGRgkWwPRmz6is/UMNGo1/jAk9y749bl3f cVOuefIVLbt3oVuAAVDEWuoH/BDt3iSuvBkBGncpYVUZj9hbsx2h8rCd+p+1KGB2EH/z Y2qw== Received: by 10.229.112.75 with SMTP id v11mr10506283qcp.144.1336518689834; Tue, 08 May 2012 16:11:29 -0700 (PDT) Received: from [192.168.2.150] (c-98-231-181-148.hsd1.va.comcast.net. [98.231.181.148]) by mx.google.com with ESMTPS id bs9sm6637862qab.2.2012.05.08.16.11.28 (version=SSLv3 cipher=OTHER); Tue, 08 May 2012 16:11:29 -0700 (PDT) Message-ID: <1336518686.2728.11.camel@OfficePC> Subject: Re: AMQ NMS endless AdvisoryConsumer messages From: Timothy Bish To: users@activemq.apache.org Date: Tue, 08 May 2012 19:11:26 -0400 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.2- Content-Transfer-Encoding: 7bit Mime-Version: 1.0 On Tue, 2012-05-08 at 16:07 -0600, Chris Robison wrote: > I implemented a tracer and and turned on debug and the client is endlessly > spitting out the following: > > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer removing: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer adding: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer removing: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer adding: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer removing: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer adding: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer removing: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer adding: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer removing: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer adding: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer removing: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer adding: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5109|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer removing: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5265|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer adding: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5265|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer removing: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5265|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer adding: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5265|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer removing: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > 2012-05-08 18:01:40.5265|DEBUG|VOAuto.Services.Citrix.RequestInvoker|DEBUG: > AdvisoryConsumer adding: > temp-queue://ID:POTMIP102-64244-634720212832430486-1:149:1 > > Any suggestions? > > Chris Best thing to do is to create a test case that can demonstrate the issue, without know more its hard to say what is going on here. -- Tim Bish Sr Software Engineer | FuseSource Corp tim.bish@fusesource.com | www.fusesource.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/