You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Oleg Kozakevych (JIRA)" <ji...@apache.org> on 2016/12/29 13:49:58 UTC

[jira] [Commented] (AMQNET-447) Individual Acknowledgement seems not working in NMS

    [ https://issues.apache.org/jira/browse/AMQNET-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15785350#comment-15785350 ] 

Oleg Kozakevych commented on AMQNET-447:
----------------------------------------

Is this problem still actual? I see that Java client already allows Individual ack mode for durable subscribers. Please see https://issues.apache.org/jira/browse/AMQ-5163

> Individual Acknowledgement seems not working in NMS
> ---------------------------------------------------
>
>                 Key: AMQNET-447
>                 URL: https://issues.apache.org/jira/browse/AMQNET-447
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: ActiveMQ, NMS
>    Affects Versions: 1.6.0
>         Environment: windows xp sp2 
> visual studio 2010 sp1
> .NET 4.0 
> JavaSE Runtime Envrionment build 1.7.0_17-b02
> ActiveMQ 5.8.0 running under RedHat 6.3
> NMS 1.6.0
>            Reporter: HellKnight
>            Assignee: Timothy Bish
>              Labels: test
>             Fix For: 1.6.1
>
>         Attachments: AMQDurableSub.rar
>
>
> I create a simple unit test to show my problem in VS2010 , coded in c#.
> The idea of my test is as follow :
> 1. Send some message to the broker by web console.
> 2. Start a durable subscriber , and receive the test messages.Then call message.acknowledge() on the last message received.
> 3. Close the connection of the durable subscriber and start listening again.
>     the session is using individual ack mode. Since the individual ack mode acknowledges each message individually, I would expect that only the last message is acked , so after restart the subscriber, the test messages except the last one should be received again. However, the fact is every message is acked and 
> none test message is received the second time. 
>     Generally speaking, My unit test compare the number of message received before ack the last message and after ack the last message. What I am expecting is the second time I will receive one less message but the fact is I receive 0 message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)