[AMQ-3576] ProducerBrokerExchange last producer sequenceId initialization needs runtime updates to deal with possible duplicate resends

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.5.1
• Fix Version/s: 5.6.0
• Component/s: Broker

Environment

failover:(tcp://host:port?soWriteTimeout=500)?jms.useAsyncSend=true&trackMessages=true

• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 02/Nov/11 17:03
• Updated: 27/Mar/12 12:29
• Resolved: 24/Nov/11 17:05

Description

Under load, a buffered pending send can be replayed along with a failover replay (writeTimeFilter initiated) which can miss the audit b/c it won't have knowledge of the original send.
The dispatch decision is based on the current stored state at the time of reconnect with the expectation that the next message will not be duplicated. It seems under some load and tcp buffering conditions this is possible to get duplicate sends of new messages.

Issue Links

• is required by: AMQ-3473 Messages (possibly) stuck and pending messages count showing high number of pending message which do not get sent to a consumer.
• is required by: AMQ-3525 Messages seem to be getting stuck on queues