activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: AMQ NMS endless AdvisoryConsumer messages
Date Tue, 08 May 2012 23:11:26 GMT
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/


Mime
View raw message