OK, so seems like there's at least a partial resolution to this, which is to
use the latest trunk build, due to the bug QPID-1893. This bug relates to the
java client not generating heartbeats, fixed 12-Jan-2010.
I'm not entirely sure how not properly responding to heartbeats causes the
resend o
ws:
FailoverSingleServer:114 - No delay between connect retries, use
tcp://host:port?connectdelay='value' to enable.
It seems that the connectdelay value has not been picked up. Can anyone
conjecture why?
Thanks for any help!
-Simon
--- On Sun, 2/28/10, me really wrote:
Fr
Hello,
We are running a two-broker federation. We have a Java producer (0.5)
sending messages to Broker 1, which is configured to push to Broker 2, from
which a consumer is reading the data. The push link is configured
with: 'qpid-route -d -s queue add broker2 broker1 myexchange myqueue'
We are
