[
https://issues.jboss.org/browse/JBAS-7950?page=com.atlassian.jira.plugin....
]
Piotr Komisarski commented on JBAS-7950:
----------------------------------------
hi.
I'm facing the same problem, but i think there is some kind of workaround:
Instead of throwing RuntimeException you can inject MessageDrivenContext and call
setRollbackOnly().
In this case messaging engine is properly redelivering message and when it comes to max
redelivering count
it's send to DLQ. But now I'm curious why JMSXDeliveryCount is not set to max in
DLQ. (it's set to zero)
I've found, that this property it's not updated by default, and i must set
"persist-delivery-count-before-delivery"
in configuration. But anyway - it's still not working.
HornetQ keeps re-delivering the message infinitely on a failure to
deliver to MDB
----------------------------------------------------------------------------------
Key: JBAS-7950
URL:
https://issues.jboss.org/browse/JBAS-7950
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Environment: AS trunk (hornetq 2.1.0 Beta2)
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 6.1.0
Attachments: hornetq.diff, 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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira