Hi Elliot,
I posted a reply at:
http://www.nabble.com/Expired-messages-are-not-being-removed-from-queues-tt21967682.html#a22773666
Cheers,
Michael
--
View this message in context:
http://www.nabble.com/How-to-purge-old-messages-when-no-consumer-exists--tp22745203p22774153.html
Sent from the Ac
Hi Elliot,
Yes I was quite disappointed to figure out that ActiveMQ was just leaving
those messages around. Particularly since it caused queues to seize up and
become useless, even after following all the advice out there about turning
off producer flow control.
In the end I implemented a workar
tting up a log4j.properties
file as recommended by the activeMQ website. Has anyone else had trouble
getting activeMQ to output debugging information?
mcarter wrote:
>
> That would certainly produce the described behaviour. I've checked very
> carefully though and I'm 100% cert
>
> Re #2 - you could write yourself a broker plugin thingy that extends
> BrokerService and implements the addConnection(ConnectionContext context,
> ConnectionInfo info) method; within which you can check the IP address of
> the remote client making the connection request.
>
>
I've imple
Hi everyone,
I've recently been trying to sort out a problem whereby my message queues
are seizing up. Essentially after a certain number of messages get put into
a queue, the whole queue seems to freeze up. That issue aside, the reason it
was filling up in the first place was that expired messag
I get exactly the same issue. The only way I've found to get rid of it is to
not use the fileQueueCursor pendingQueuePolicy
--
View this message in context:
http://www.nabble.com/Queue-Fill-Up-tp15917723p21907015.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
That would certainly produce the described behaviour. I've checked very
carefully though and I'm 100% certain that I don't have another consumer.
I've discovered a few more things though.
I only have two machines involved in this transaction but it seems to only
be triggered when I"m using a part
