[
http://jira.jboss.com/jira/browse/JBESB-678?page=comments#action_12368791 ]
Mark Little commented on JBESB-678:
-----------------------------------
But that's precisely what I mean. We're going to the message store after 2
attempts. That's probably fine for most people, but what if someone really wants to
avoid the message store and try 3, 4 or 5 times? Or alterantively they don't want to
bother checking at all if the first cache fails? We should try to offer flexibility, even
if 80% of the time it isn't needed.
Remove retry hard-coded magic number
------------------------------------
Key: JBESB-678
URL:
http://jira.jboss.com/jira/browse/JBESB-678
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Kurt Stam
Fix For: 4.2
ServiceInvoker appears to retry deliver twice:
private Message deliver(Message message, boolean synchronous) throws
MessageDeliverException
{
int numberOfAttemps=0;
while (numberOfAttemps++ < 2) {
2 is an arbitrary number. Rather than hard-code it, it should be configurable, at least
via a run-time property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira