[jboss-jira] [JBoss JIRA] Commented: (JBAS-7950) HornetQ keeps re-delivering the message infinitely on a failure to deliver to MDB

[Tim Fox (JIRA)]

    [ https://jira.jboss.org/browse/JBAS-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12547209#action_12547209 ] 

Tim Fox commented on JBAS-7950:
-------------------------------

Ok, I'm assuming CMT is the default? (Since nothing in the annotations says to use CMT)

Section 13.3.6.2 of EJB spec says:

"A transaction must be started before the dequeuing of the JMS message and, hence, before the
invocation of the message-driven bean’s onMessage method. The resource manager associ-
ated with the arriving message is enlisted with the transaction as well as all the resource man-
agers accessed by the onMessage method within the transaction. If the onMessage method
invokes other enterprise beans, the container passes the transaction context with the invoca-
tion. The transaction is committed when the onMessage method has completed. If the
onMessage method does not successfully complete or the transaction is rolled back, **** message
redelivery semantics apply ****."

Unfortunately I can't find any definition of these message delivery semantics in this spec. Any ideas?




> HornetQ keeps re-delivering the message infinitely on a failure to deliver to MDB 
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-7950
>                 URL: https://jira.jboss.org/browse/JBAS-7950
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS (HornetQ)
>         Environment: AS trunk (hornetq 2.1.0 Beta2)
>            Reporter: jaikiran pai
>            Assignee: Tim Fox
>             Fix For: TBD
>
>         Attachments: JBAS-7950-source.tar.gz, jbas7950.ear
>
>
> As discussed in the referenced forum thread, when HornetQ first fails to deliver a message to a MDB, it continues to redeliver the message infinitely. Also note that the JMS Message.getJMSRedelivered() is also broken - it keeps returning false even on a redelivered message.

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