[esb-issues] [JBoss JIRA] Commented: (JBESB-2752) Message lost in case of exception in Message Composer

[Kevin Conner (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12476679#action_12476679 ] 

Kevin Conner commented on JBESB-2752:
-------------------------------------

- you have set this up to auto-acknowledge deliver of the message and this is what you are seeing.

- exceptions do not cause any non-jca delivery of incoming messages to go to any DLQ but we can certainly add something for this.

- JCA delivery is working correctly.

What fault do you believe exists?


> Message lost in case of exception in Message Composer
> -----------------------------------------------------
>
>                 Key: JBESB-2752
>                 URL: https://jira.jboss.org/jira/browse/JBESB-2752
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.4 CP2
>         Environment: Fedora 11, 4.3.0.GA_CP01_SOA
>            Reporter: Boris Belovic
>         Attachments: custom_composer.tar.gz
>
>
> I have written (very simple) custom composer class. It just receives a JMSObjectMessage and according to message contents it creates an ESB-aware message or throws an exception. The creation of ESB aware message works fine and the message is properly delivered to receiver.  In the second case an exception is thrown and the original message should be redelivered, but this is not happening. Instead of redelivery, message is lost.
> In case that an exception is thrown, the original message should be routed to deadletter queue. But when I try to obtain this message from the deadletter queue (either queue/DLQ or using a MessageStore instance), the queue is empty. It contains no messages and the message is lost.
> I also tried to use jca-provider instead of jms-provider. This provider was also unable to deliver message to proper receiver. JCA provider tried several times to redeliver message, but after all the message ended up in DLQ queue (queue/DLQ).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira