[
https://issues.apache.org/jira/browse/AMQNET-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kozakevych updated AMQNET-563:
-----------------------------------
Description:
Under AMQNET-447 individual acknowledgement for durable subscribers was
disabled as there were some problems in ActiveMQ (see comments in AMQNET-447).
For now it looks like the problem for ActiveMQ is not actual (see
https://issues.apache.org/jira/browse/AMQ-5163).
But NMS is still throws an exception in such case.
Looks like AMQNET-447 should be reverted.
was:
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.
> Individual Acknowledgement is disabled in NMS
> ---------------------------------------------
>
> Key: AMQNET-563
> URL: https://issues.apache.org/jira/browse/AMQNET-563
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ, NMS
> 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: Oleg Kozakevych
> Assignee: Timothy Bish
> Labels: test
>
> Under AMQNET-447 individual acknowledgement for durable subscribers was
> disabled as there were some problems in ActiveMQ (see comments in AMQNET-447).
> For now it looks like the problem for ActiveMQ is not actual (see
> https://issues.apache.org/jira/browse/AMQ-5163).
> But NMS is still throws an exception in such case.
> Looks like AMQNET-447 should be reverted.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
