On Thu, 30 Aug 2012 15:40:18 -0400, Timothy Bish
tabish...@gmail.com wrote:
On Thu, 2012-08-30 at 12:44 +0100, spam trap wrote:
On Wed, 29 Aug 2012 10:08:36 -0400, Timothy Bish
tabish...@gmail.com wrote:
On Wed, 2012-08-29 at 15:04 +0100, spam trap wrote:
On Wed, 29 Aug 2012 08:46:18
that is really the point of a priority queue, to starve out low
priority messages in favor of higher priority.
There is currently no way to tell amq; every now and again let some
lower priority messages through. It begs lots of questions and it
would be quite complex to achieve :-)
Priority
On Fri, 2012-08-31 at 10:08 +0100, spam trap wrote:
On Thu, 30 Aug 2012 15:40:18 -0400, Timothy Bish
tabish...@gmail.com wrote:
On Thu, 2012-08-30 at 12:44 +0100, spam trap wrote:
On Wed, 29 Aug 2012 10:08:36 -0400, Timothy Bish
tabish...@gmail.com wrote:
On Wed, 2012-08-29 at
Is there any way to log messages that got trapped in DLQ in logs? How I can
be notified when a message get stored in DLQ, do I need to write some thread
class?
Thanks Regards,
Gaurav Seth
--
View this message in context:
What all messages land in ActiveMQ.DLQ and what all in Individual dead letter
queues. What configuration we need to do in activemq.xml file to do that? I
have following entries in my activemq.xml file and my dead messages are
getting stored in DLQ.wfc.notifications.router:
destinationPolicy
You could register a topic listener on your DLQ and consume and process the
message when it gets send to the DLQ.
Alternatively you can have an advisory msg generated whenever a msg is moved to
DLQ. See http://activemq.apache.org/advisory-message.html, properties
Hello,
With the configuration below any queue msgs being moved to a DLQ will end up on
the corresponding individual dead letter queue. If you also have durable topic
subscriber, then the failure to deliver msgs to these subscribers after 6
redelivery attempts could cause these messages to be
seems to be jetty related but have not tracked it down to a version
http://www.codingtiger.com/questions/jetty/mysterious-console-output-to-stderr-from-jetty.html
On 30 August 2012 17:30, boday ben.o...@initekconsulting.com wrote:
I'm also seeing this message frequently after upgrading from
Hello
The Apache.NMS.Stomp 1.5.3 Release bundle is now available on the
Apache.NMS site:
http://activemq.apache.org/nms/apachenmsstomp-v153.html
This release is based on the Apache.NMS API v1.5.1 and runs on .NET
and .NETCF frameworks 2.0+ and Mono 2.0+.
This is a bugfix release that adds
thanks Gary...that makes sense...I just thought I'd check to see if there was
some built-in mechanism to handle this case...indefinite starvation is a
common concern for this pattern, but tricky to implement as you stated.
for now, I suppose I can periodically check the queue for old messages
10 matches
Mail list logo
