[QPID-8225] [Broker-J][AMQP 0-10] stops delivering queue/consumer messages after 4 GB data transfer

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: qpid-java-6.1.6, qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, 0.18, 0.20, 0.22, 0.24, 0.26, 0.28, 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, qpid-java-6.0.6, qpid-java-6.1.1, qpid-java-6.1.2, qpid-java-6.0.7, qpid-java-6.1.3, qpid-java-6.0.8, qpid-java-6.1.4, qpid-java-broker-7.0.0, qpid-java-6.1.5, qpid-java-broker-7.0.1, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, qpid-java-broker-7.0.6
• Fix Version/s: qpid-java-broker-7.1.0, qpid-java-broker-7.0.7
• Component/s: Broker-J
• Assignee: Unassigned
• Reporter: Michael Dyslin
• Created: 06/Aug/18 15:58
• Updated: 09/Jul/19 17:05
• Resolved: 07/Aug/18 10:24

Description

Created this Jira so I could send a logfile attachment to be analyzed.  Attachments are removed from the user discussion email lists.

 

Log file is for the java broker with a NameAndLevel filter of org.apache.qpid.server.protocol.v0_10.ServerConnection at the DEBUG level.

Activity was:

1. Start the java broker
2. Start the consumer
3. Start the producer
4. 2 messages sent every 10 seconds
5. Stopped producer after 10 messages sent
6. stopped the consumer much later

This log does not contain the problem where message flow stopped, probably due to CREDIT flow mode exceeding 4 GB credit.

 

 

 

Issue Links

• is duplicated by: QPID-3616 Java Broker misinterprets message.flow infinite credit value (0xFFFFFFFF)