Uploaded image for project: 'ActiveMQ .Net'
  1. ActiveMQ .Net
  2. AMQNET-447

Individual Acknowledgement seems not working in NMS

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.6.0
    • 1.6.1
    • ActiveMQ, NMS
    • 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

    Description

      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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            tabish Timothy A. Bish
            HellKnight HellKnight
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment