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

Rob Godfrey reassigned QPID-6313:
---------------------------------

    Assignee: Rob Godfrey

> [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]

Reply via email to