activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Gellings (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-221) Should be able to max out retries on a message and then sent to dead letter queue
Date Fri, 11 Dec 2009 19:53:54 GMT

    [ https://issues.apache.org/activemq/browse/AMQNET-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56399#action_56399
] 

Mark Gellings commented on AMQNET-221:
--------------------------------------

I've done some more troubleshooting and the issue is the ActiveMQTextMessage.Text property
can't be set on a message being consumed in v1.2.  With v1.1 this was possible.  Now NMS ActiveMQ
throws back:

?e.Message
"Message is in Read-Only mode."
?e.StackTrace
"   at Apache.NMS.ActiveMQ.Commands.ActiveMQMessage.FailIfReadOnlyBody()\r\n   at Apache.NMS.ActiveMQ.Commands.ActiveMQTextMessage.set_Text(String
value)\r\n   at Quad.NMS.ActiveMQTextMessageExtensions.ToJson(ActiveMQTextMessage msg, Object
list) in C:\\WIP\\QuadNMS\\src\\NMS\\ActiveMQTextMessageExtensions.cs:line 36\r\n   at Quad.NMS.ClientAcknowledgementHandler.GetSender(ActiveMQTextMessage
concreteMessage, ISession session, Int32 redeliveredCount) in C:\\WIP\\QuadNMS\\src\\NMS\\ClientAcknowledgementHandler.cs:line
125\r\n   at Quad.NMS.ClientAcknowledgementHandler.Execute(Exception exception, ISession session,
IMessage message) in C:\\WIP\\QuadNMS\\src\\NMS\\ClientAcknowledgementHandler.cs:line 56\r\n
  at Quad.NMS.AcknowledgementHandler.Execute(ISession session, IMessage message, Exception
exception) in C:\\WIP\\QuadNMS\\src\\NMS\\AcknowledgementHandler.cs:line 73\r\n   at Quad.NMS.Listener`1.OnMessage(IMessage
message) in C:\\WIP\\QuadNMS\\src\\NMS\\Listener.cs:line 257"

We have some logic built into our NMS framework (which sits on top of NMS ActiveMQ) to enhance
redelivery logic with ClientAcknowledgement mode.  We modify a message's text before sending
it to the DLQ.  We reuse the same message in order to preserve its properties as they were
originally set by the producer.

I'd have to think about how we can get around this.  I'm sure there's a good reason behind
this change but it is breaking...what's the reasoning?

> Should be able to max out retries on a message and then sent to dead letter queue
> ---------------------------------------------------------------------------------
>
>                 Key: AMQNET-221
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-221
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: NMS
>    Affects Versions: 1.2.0
>         Environment: ActiveMQ 1.2
>            Reporter: Mark Gellings
>            Assignee: Jim Gomes
>
> Using AcknowledgementMode.ClientAcknowledge, after exhausting all of the retries of a
message the message remains in the original queue.
> With v1.1 message is sent to the DLQ. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message