[esb-issues] [JBoss JIRA] Commented: (JBESB-3611) ServiceInvoker would always set DELIVER_TO property
[
https://issues.jboss.org/browse/JBESB-3611?page=com.atlassian.jira.plugin...
]
Kevin Conner commented on JBESB-3611:
-------------------------------------
A small example which could be deployed into the ESB would be sufficient.
The DELIVER_TO will be set on the message just prior to sending it to the dead letter
service, provided the message matches the right criteria. It is then removed immediately
so that it does not affect subsequent users of the message.
We really need to see an example of your issue in order to get a better understanding of
it.
ServiceInvoker would always set DELIVER_TO property
---------------------------------------------------
Key: JBESB-3611
URL: https://issues.jboss.org/browse/JBESB-3611
Project: JBoss ESB
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.9 CP1
Reporter: Michael Burman
Attachments: serviceinvoker_jbesb_3611.patch
If ServiceInvoker fails when sending a msg to destination queue, it sets DELIVER_TO
messageProperty before sending it to DeadLetterService. With this functionality the
jbossesb.esb package can send DLQ messages from the database back to the destination
JMS-Queue. However, this functionality does not work when used with JCA and the
JMS-servers' own DLQ-functionality, since there is no DELIVER_TO parameter set.
The attached patch would always set the DELIVER_TO property to the messages and would
make the ESB's DLQ-handler work with transacted JCA-queues also. It should not break
any existing functionality, as this value is only read by DBMessageStoreImpl,
redeliver(URI uuid) part.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira