[
https://issues.apache.org/jira/browse/QPID-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278980#comment-14278980
]
Rob Godfrey commented on QPID-6313:
-----------------------------------
I'm not sure where this notion of blocking for 1 second comes from. I'm not
aware of anything like that in the JMS definition.
The javadoc for recover() says:
{quote}
Stops message delivery in this session, and restarts message delivery with the
oldest unacknowledged message.
All consumers deliver messages in a serial order. Acknowledging a received
message automatically acknowledges all messages that have been delivered to the
client.
Restarting a session causes it to take the following actions:
* Stop message delivery
* Mark all messages that might have been delivered but not acknowledged as
"redelivered"
* Restart the delivery sequence including all unacknowledged messages that had
been previously delivered. Redelivered messages do not have to be delivered in
exactly their original delivery order.
{quote}
which is what I believe the client is now doing (and as of last night is should
also be incrementing the delivery count).
> [AMQP 1.0] - Calling session.Recover() with CLIENT_ACKNOWLEDGE does not
> increase redelivery count
> -------------------------------------------------------------------------------------------------
>
> Key: QPID-6313
> URL: https://issues.apache.org/jira/browse/QPID-6313
> Project: Qpid
> Issue Type: Bug
> Components: JMS AMQP 1.0 Client
> Affects Versions: Future
> Reporter: Mathias Wiberg
> Assignee: Rob Godfrey
>
> Hi,
> I'm using Qpid 1.0 client to integrate with a Microsoft Azure bus. I've been
> using the latest version of Qpid (compiled today from trunk). The testcase is
> very simple:
> 1. One application sends a message to a queue, and another application starts
> a MessageListener.
> 2. In the onMessage method, the MessageId and DeliveryFailues variables are
> printed out. After this, the session is recover (session.recover()).
> When using version 0.28, and 0.30 each recovery would be printed each minute
> (pre-defined value in service bus for locking messages), and the
> deliveryCount property on the message would be increased by 1.
> When using version 0.32, each recovery is happening within ms of each other,
> and the deliveryCount property is the same for all (almost) messages. I can
> even disconnect the link between the client and the server and the
> MessageListener still prints out the messageId and DeliveryFailues. Therefor,
> it seems like there is some caching involved, or repeating the last sent
> message without notifying the broker.
> Here are some logstatements from my test application:
> [0.30]
> 2015-01-14T15:30:08.057 - Received message with JMSMessageID:
> ID:2581847573616249688, RedeliveryCount: 0
> 2015-01-14T15:31:08.094 - Received message with JMSMessageID:
> ID:2581847573616249688, RedeliveryCount: 1
> 2015-01-14T15:32:08.117 - Received message with JMSMessageID:
> ID:2581847573616249688, RedeliveryCount: 2
> [0.32]
> 2015-01-14T15:35:38.964 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 0
> 2015-01-14T15:35:38.979 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.979 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.979 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.979 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.979 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:38.995 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:39.011 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:39.011 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:39.011 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:39.011 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:39.011 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:39.011 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:39.011 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:39.011 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:39.011 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:39.011 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> 2015-01-14T15:35:39.011 - Received message with JMSMessageID:
> ID:907900209320220697, RedeliveryCount: 1
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
