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 on failover, but with heartbeating, a failover doesn't occur, so in one sense, it's moot. But if anyone can offer any insight into why, if no heartbeat occurs, that a message sent before the connection timeout and failover, gets re-sent, would still be appreciated.
