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/16 13:17:31 UTC

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

    [ https://issues.apache.org/jira/browse/QPID-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613910#action_12613910 ] 

Martin Ritchie commented on QPID-1178:
--------------------------------------


pool-6-thread-1 2008-07-15 22:52:34,102 DEBUG [qpid.server.protocol.AMQProtocolSession] Frame Received: Frame channelId: 1, bodyFrame: [BasicConsumeBodyImpl: ticket=0, queue=example.queue, consumerTag=4, noLocal=false, noAck=true, exclusive=false, nowait=false, arguments={x-filter-auto-close=[BOOLEAN: true], x-filter-no-consume=[BOOLEAN: true]}]
pool-6-thread-1 2008-07-15 22:52:34,102 DEBUG [qpid.server.handler.BasicConsumeMethodHandler] BasicConsume: from 'example.queue' for:4 nowait:false args:{x-filter-auto-close=[BOOLEAN: true], x-filter-no-consume=[BOOLEAN: true]}
...
pool-6-thread-3 2008-07-15 22:52:34,110 DEBUG [qpid.client.protocol.AMQProtocolHandler] (32978439)Method frame received: [BasicDeliverBodyImpl: consumerTag=4, deliveryTag=1, redelivered=false, exchange=amq.direct, routingKey=example.queue]
pool-6-thread-3 2008-07-15 22:52:34,110 DEBUG [qpid.client.handler.BasicDeliverMethodHandler] New JmsDeliver method received:org.apache.qpid.client.protocol.AMQProtocolSession@164c243
...
main 2008-07-15 22:52:34,115 INFO [apache.qpid.client.BasicMessageConsumer] Closing consumer:4[18154379]
main 2008-07-15 22:52:34,115 DEBUG [apache.qpid.framing.AMQDataBlockEncoder] Encoded frame byte-buffer is '0x01000100000007003c001e013400ce'
main 2008-07-15 22:52:34,115 DEBUG [qpid.client.protocol.AMQProtocolHandler] Sent frame Frame channelId: 1, bodyFrame: [BasicCancelBodyImpl: consumerTag=4, nowait=false]
...
Dispatcher-Channel-1 2008-07-15 22:52:34,115 INFO [apache.qpid.client.AMQSession$Dispatcher] Received a message(10201233)[1] from queue  consumer(4) is closed rejecting(requeue)...
...
Dispatcher-Channel-1 2008-07-15 22:52:34,115 DEBUG [apache.qpid.client.AMQSession] Rejecting Unacked message:1
Dispatcher-Channel-1 2008-07-15 22:52:34,115 DEBUG [apache.qpid.client.AMQSession] Rejecting delivery tag:1:SessionHC:22530022
Dispatcher-Channel-1 2008-07-15 22:52:34,115 DEBUG [apache.qpid.framing.AMQDataBlockEncoder] Encoded frame byte-buffer is '0x0100010000000d003c005a000000000000000101ce'
Dispatcher-Channel-1 2008-07-15 22:52:34,115 DEBUG [qpid.client.protocol.AMQProtocolHandler] Sent frame Frame channelId: 1, bodyFrame: [BasicRejectBodyImpl: deliveryTag=1, requeue=true]
...
pool-6-thread-4 2008-07-15 22:52:34,835 DEBUG [qpid.server.protocol.AMQProtocolSession] Frame Received: Frame channelId: 1, bodyFrame: [BasicRejectBodyImpl: deliveryTag=1, requeue=true]
pool-6-thread-4 2008-07-15 22:52:34,835 DEBUG [qpid.server.handler.BasicRejectMethodHandler] Rejecting:1: Requeue:true on channel:1(26085693)
pool-6-thread-4 2008-07-15 22:52:34,835 WARN [qpid.server.handler.BasicRejectMethodHandler] Dropping reject request as message is null for tag:1


> 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
>
> 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.