-
1. Re: quickstart deadletter service bug?
kadlecp Sep 12, 2007 9:58 AM (in response to kadlecp)And the ServiceInvoker.deliverSync in case of failure really stores message with classification "DLQ" to the message store.
-
2. Re: quickstart deadletter service bug?
kconner Sep 12, 2007 11:05 AM (in response to kadlecp)There is a bug but it may not be the one you are thinking about.
The ServiceInvoker.deliverSync method does send the message to the DeadLetterService but this does not mean that the message is stored with a classification of DLQ. The message can specify a classification as a property in which case this will be used instead.
The bug occurs because the previous action failed (AsyncAction) and this resulted in that message being tagged with a RDLVR classification. Because this tagging was not tidied up all subsequent failures of that message would also be tagged with a RDLVR classification.
If you were to swap the actions in the quickstart then the SyncAction would result in a message going to DLQ but the QS would obviously not work as it currently stands. -
3. Re: quickstart deadletter service bug?
kconner Sep 12, 2007 12:40 PM (in response to kadlecp)This has been addressed in the following issues
http://jira.jboss.com/jira/browse/JBESB-1029 and http://jira.jboss.com/jira/browse/JBESB-1030
My bad, thanks for pointing this out.