The Service Bus for the Connected Business
We are new customers, using Neuron 3.1, and we have a question regarding republishing of messages from a poison queue. It seems that when a message ends up in our poison queue, and we try to republish it manually, a copy of that message is sent to the main queue, but the original msg stays in the poison queue. If the message is delivered with success, we still have the original msg in the poison queue. On the other hand, if the message still fails, we end up with two identical messages in the poison queue. Can you please explain why this is happening and how to configure Neuron in order to be able to move the message to the main queue on Republishing instead of copying it.
We have a MSMQ topic with the following Networking configuration:
Transaction Timeout: 30 (if we use default 60 sec, Neuron will discard the msg after 25 sec without retry).
Use Policy for Retries: False (we do have a custom policy, but if we set this value to True, Neuron will not use the retry values registered on the topic)
Retry Cycle Delay: 00:02:00
Max Retry Cycles: 2
Receive Retry Count: 2
Receive Error Handling: Move
Enable Poison Message processing: True
Enable Dead Letter Processing: True
We also have a custom policy on our service connector (we need to define this custom policy, without any custom policy the msg will be discarded after 25 sec.), with the following configuration:
Retry interval: 45 sec.
Retry Expiration: 5 min
Failure action: Discard message.
Regards,
Nanna Fog
Views: 489
Hi Nanna,
We'll look into this today. this could be an oversight on our side though. I'm assuming you're republishing from the Neuron Explorer's MSMQ management screen?
Another option it to enable Poison queue message processing on the Topic's networking properties. With that enabled, anytime a message his a poison queue, Neuron will automatically move it to the failed message reports. From there you can republish the message. This tends to be a nice of way of never having to worry about poison queues
Yes, we resume the messages from the Neuron Explorer's MSMQ management screen. And we do have Poison queue Message Processing enabled. But the messages stay in the poison queue. The same happens if we republish the message from the Message History or Failed Messages, it is still a copy of the msg, the original stays in the poison queue.
Regards,
Nanna
For your information, we actually run this on Neuron 3.5.
Nanna
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin.
Powered by
