dead-letter

问题 It is very hard to find some good documentation on getting all the messages in a deadletter queue and getting to take a peek at them. I have an Azure Servicebus Queue and everything I can find is for Azure Servicebus Topics. Can someone help me with a quick guide? 回答1: Dead letter queue is a secondary sub-queue where the poison messages are moved to. In case of Azure Servicebus Queue the standard path for DLQ is queuePath/$DeadLetterQueue . So you need to have another queueClient to read the

问题 I want to do the following: when a message fails and falls to my dead letter queue, I want to wait 5 minutes and republishes the same message on my queue. Today, using Spring Cloud Streams and RabbitMQ, I did the following code Based on this documentation: @Component public class HandlerDlq { private static final Logger LOGGER = LoggerFactory.getLogger(HandlerDlq.class); private static final String X_RETRIES_HEADER = "x-retries"; private static final String X_DELAY_HEADER = "x-delay"; private

问题 I´m currently struggeling with implementing my Akka router logic using scaldi for dependency injection. Why cant I bind to a single actor instance with scaldi, since my actor is a router and I only want to have one single instance of it? The way I came to ask this question was another stackoverflow entry. My scaldi Module: class DAOModule extends Module { bind toProvider new UserDaoWorker binding to new UserDaoRouter } This way only one instance is created and as soon as I inject my router

问题 I´m currently struggeling with implementing my Akka router logic using scaldi for dependency injection. Why cant I bind to a single actor instance with scaldi, since my actor is a router and I only want to have one single instance of it? The way I came to ask this question was another stackoverflow entry. My scaldi Module: class DAOModule extends Module { bind toProvider new UserDaoWorker binding to new UserDaoRouter } This way only one instance is created and as soon as I inject my router

问题 I'm writing a piece of code which will allow us to: View a list of all dead letter messages that exist within an Azure Service Bus Topic (Peek) Fix and send them back to the Topic Delete them from the dead letter queue upon resending. I have no issues with the first 2 points; using the Peek receive mode I can show a list of messages and we can edit and resend with no issues. The problem comes when I want to actually delete the message from the dead letter queue. How do we do this on a message

问题 I've created an Actor that performs some basic operations and appears to be working correctly - however I'm seeing the following show up in my logs regularly [INFO] [05/28/2014 14:24:00.673] [application-akka.actor.default-dispatcher-5] [akka://application/deadLetters] Message [akka.actor.Status$Failure] from Actor[akka://application/user/trigger_worker_supervisor#-2119432352] to Actor[akka://application/deadLetters] was not delivered. [1] dead letters encountered. This logging can be turned

问题 Here's what we have here: Topic Exchange DLE , which is intended to be a Dead-Letter Exchange Topic Exchange E , which is the "main" Exchange Several Queues ( EQ1 , ..., EQn ) bound to E (and initialized with x-dead-letter-exchange = DLE ), each with own Routing Key. These queues are the ones being consumed from. For each EQn , there's a DLEQn (initialized with x-dead-letter-exchange = E and x-message-ttl = 5000 ), bound to DLE with the same routing key as EQn . These queues are not being

问题 I have a java application running on JBoss 7.1. It is using more than 20 JMS-queues. My configuration to setup the JMS queues: <jms-queue name="MX.EQ.DT.MT.OUT"> <entry name="queue/MX.EQ.DT.MT.OUT"/> <entry name="java:jboss/exported/jms/queue/MX.EQ.DT.MT.OUT"/> </jms-queue> <jms-queue name="MX.EQ.DS.XML.OUT"> <entry name="queue/MX.EQ.DS.XML.OUT"/> <entry name="java:jboss/exported/jms/queue/MX.EQ.DS.XML.OUT"/> </jms-queue> Now, I want to configure the dead letter queue for above two queues.

问题 I have a very simple structure based on Akka actors in Scala, but I keep on receiving warnings about undelivered messages. This is the code for the main class, Collector is a separate class extending Actor: object Executor extends App { class ExecutorMaster extends Actor { def receive() = { case _ => Executor.actorSystem.actorOf(Props[Collector], name = "Collector") ! true } } val actorSystem = ActorSystem("ReadScheduler") private val app = actorSystem.actorOf(Props[ExecutorMaster], name =

问题 I'm trying to implement a dlx queue in RabbitMQ. The scenario is quite easy I have 2 queues: 1) alive 2) dead (x-dead-letter-exchange: "immediate", x-message-ttl: 5000) and an exchange "immediate" that is bound to 1) alive I tried to run this example: http://blog.james-carr.org/2012/03/30/rabbitmq-sending-a-message-to-be-consumed-later/ but it seems that the messages are dropped after the ttl expires and they dont get published on the exchange, so my alive queue is always empty. I also tried