dead-letter

Dead-letter in Akka Scala actors

心已入冬 提交于 2019-12-05 12:15:47
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 = "Executor") app ! true } The message is not being delivered to the Collector, the result for the code is:

Dead letter exchange RabbitMQ dropping messages

白昼怎懂夜的黑 提交于 2019-12-05 04:54:59
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 to create the queues by hand in the management console and I get the same behaviour. I tested it with

How to view akka dead letters

匆匆过客 提交于 2019-12-03 02:07:37
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 off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during

ActiveMQ redelivery does not work

我怕爱的太早我们不能终老 提交于 2019-12-01 12:50:28
I am trying the implement a dead letter queue using ActiveMQ. Unfortunately the documentation on this end is rather vague on some aspects and I can't seem to get everything properly set up. I have the following Beans configured: @Bean public JmsTemplate createJMSTemplate() { logger.info("createJMSTemplate"); JmsTemplate jmsTemplate = new JmsTemplate(getActiveMQConnectionFactory()); jmsTemplate.setDefaultDestinationName(queue); jmsTemplate.setDeliveryPersistent(true); jmsTemplate.setDeliveryMode(DeliveryMode.PERSISTENT); return jmsTemplate; } @Bean public DefaultJmsListenerContainerFactory

ActiveMQ redelivery does not work

被刻印的时光 ゝ 提交于 2019-12-01 11:32:12
问题 I am trying the implement a dead letter queue using ActiveMQ. Unfortunately the documentation on this end is rather vague on some aspects and I can't seem to get everything properly set up. I have the following Beans configured: @Bean public JmsTemplate createJMSTemplate() { logger.info("createJMSTemplate"); JmsTemplate jmsTemplate = new JmsTemplate(getActiveMQConnectionFactory()); jmsTemplate.setDefaultDestinationName(queue); jmsTemplate.setDeliveryPersistent(true); jmsTemplate

RabbitMQ dead letter exchange never getting messages

ε祈祈猫儿з 提交于 2019-11-28 15:43:37
I'm trying to setup my first RabbitMQ dead letter exchange, here are the steps I'm using through the web admin interface: Create new DIRECT exchange with the name "dead.letter.test" Create new queue "dead.letter.queue" Bind "dead.letter.queue" to "dead.letter.test" Create new queue "test1" with the dead letter exchange set to "dead.letter.test" Send a message into "test1" Nack (with requeue = false) the message in "test1" I am expecting that these steps should put a record into the "dead.letter.queue" through the "dead.letter.test" exchange. This is not happening. I can manually put a message

Dead-lettering dead-lettered messages in RabbitMQ

时间秒杀一切 提交于 2019-11-28 09:32:53
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 consumed from What I want is the following: if a consumer cannot process a message from EQn , it Nacks the

Dead Lettered Message Not Being Consumed in RabbitMQ and Node Using AMQP.Node

╄→尐↘猪︶ㄣ 提交于 2019-11-28 05:23:54
问题 I want to receive a message after a certain amount of time in one of my workers. I decided to go with Node and RabbitMQ after discovering so-called dead letter exchanges. The message seems to get send to the queue in DeadExchange, but the consumer is never receiving the message after the elapsed time in the WorkQueue in the WorkExchange. Either the bindQueue is off, or the dead-letter'ing doesn't work? I've tried a lot of different values now. Can someone please point out what I'm missing?