I'm wondering if these are coming about due to RESTful posts of new messages...
If an HTTP client comes along and sends POST /api/message?destination=queue://testqueue HTTP/1.1 is it going to try and use 'localhost' first and then fall back to the actual broker name? If so, should the client be specifying "?brokerName=<name>" where <name> is the actual broker name? Jim On Mon, Jan 16, 2017 at 11:23 AM James A. Robinson <[email protected]> wrote: > Several times now we've witnessed a cluster spinning off hundreds of > threads and spewing warnings like: > > 2017-01-16 11:10:35,376 [p209148636-3304] WARN BrokerRegistry - Broker > localhost not started so using amq-prod-1 instead > > A thread dump shows hundreds of threads along these lines: > > "ActiveMQ VMTransport: vm://localhost#205379-1" daemon prio=10 > tid=0x00007fa79c838000 nid=0x6fff waiting on condition [0x00007fa76ed6c000] > java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x0000000462734f80> (a > java.util.concurrent.SynchronousQueue$TransferStack) > at > java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) > at > java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460) > at > java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:359) > at > java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:942) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > > What's the best way to track down the source of this vm://localhost > reference? It's not coming from the activemq.xml, so I'm suspecting it's > coming from a client. > > Jim > >
