Guess an enhancement is needed to optionally see TempQueues in Jmx. Even
better would be to get this fixed.
On the test case, these existing junit tests from acrtivemq-core would make
a good start point, the first is one that tests temp queues in a network of
brokers:
org.apache.activemq.usecases.
just to give a short update ... seems like there is NOW way to remove
temp-queue like in this example. Normal queue can be simply removed but no
temp ones. Bug or a "feature"?
M.
--
View this message in context:
http://old.nabble.com/temp-queue-purge-from-code%28%29-tp28082374p28098574.html
Sen
Well I can spend this time and help you but I'm not that fluent with java and
junit so if you can suggest how to start would be great.
Thanks for this link!
M.
Have a look at the ruby jmx4r example at the bottom of this blog entry as a
starting point on a simple way to code jmx calls :
http:/
Have a look at the ruby jmx4r example at the bottom of this blog entry as a
starting point on a simple way to code jmx calls :
http://pavelgolubeff.ya.ru/replies.xml?item_no=1583&ncrnd=3263
It may also be worth investing some time in a junit test case for your
scenario, as that would speed up find
... or maybe there is a way to remove such "zombie queue" without stopping
the MQ server?
M.
lucious wrote:
>
> Hi I filed this bug AMQ-2657 which is really annoying to me and sometimes
> it takes me the whole day to look at "zombie" temp-queue (no consumers but
> messagecount increasing) and
