You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2008/07/23 17:40:31 UTC

[jira] Resolved: (QPID-1178) Java Client Rejects messages for QueueBrowsers

     [ https://issues.apache.org/jira/browse/QPID-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie resolved QPID-1178.
----------------------------------

       Resolution: Fixed
    Fix Version/s: M3

Resolved on trunk

> Java Client Rejects messages for QueueBrowsers
> ----------------------------------------------
>
>                 Key: QPID-1178
>                 URL: https://issues.apache.org/jira/browse/QPID-1178
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>            Reporter: Martin Ritchie
>            Priority: Minor
>             Fix For: M3
>
>
> 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:

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.