I am using the MessageQueueServlet and after a while, the broker is becoming non-responsive (no errors in the logs, but cpu spins up to 100%)When looking at the mbeans, I noticed that a new topic subscription shows up for *every* request under:
Subscription->Non-Durable->Topic->topic_//ActiveMQ.Advisory.TempQueue_topic_//ActiveMQ.Advisory.TempTopic In addition, I am warnings in the logs for every message posted like this: WARN BrokerRegistry - Broker localhost not started so using skaro instead In context: DEBUG log - servlet holder=MessageQueueServlet DEBUG log - call filter session DEBUG log - call servlet MessageQueueServlet DEBUG MessageServletSupport - destination uri=edw.report.edw.report.loadtest DEBUG MessageServletSupport - edw.report.edw.report.loadtest?consumer.prefetchSize=1 (queue) WARN BrokerRegistry - Broker localhost not started so using skaro instead DEBUG TransportConnection - Setting up new connection: vm://localhost#1998 DEBUG AbstractRegion - Adding consumer: ID:skaro-33505-1267748807277-2:999:-1:1 I have changed all references in all configs to reference "skaro" and not localhost, so I'm not sure where this is coming from. Could these be related? Is the topic subscription build-up something to be concerned about? It looks to me like the MessageQueueServlet may be setting up a new vm://localhost connection every time and maybe that triggers the advisory subscription. Any other ideas? Thanks for any help, David Snyder -- View this message in context: http://old.nabble.com/MessageQueueServlet-and-Topic-Subscription-Buildup--tp27788666p27788666.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
