[QPID-1178] Java Client Rejects messages for QueueBrowsers

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: M3
• Component/s: JMS AMQP 0-x
• Assignee: Unassigned
• Reporter: Martin Ritchie
• Created: 16/Jul/08 11:16
• Updated: 14/Mar/17 20:02
• Resolved: 23/Jul/08 15:39

Description

Summary:
The Java client wastes it's time rejecting messages for closed QueueBrowsers.

In 0-8 these messages are sent with NO_ACK so the reject will currently have no effect.
Currently the Java Broker simply reports a warning of this:
_logger.warn("Dropping reject request as message is null for tag:" + deliveryTag);
// throw evt.getMethod().getChannelException(AMQConstant.NOT_FOUND, "Delivery Tag(" + deliveryTag + ")not known");
But it should close the Channel as rejecting an invalid message is a Channel error:

Protocol Trace attached in comments: