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

Seems like there is a race condition that can lead to an InvalidDestinationException for tempoary queues after failover has resumed

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Incomplete
    • 1.5.3
    • 1.6.0
    • None
    • None

    Description

      If I repeat the test below I sometimes get a:
      Apache.NMS.InvalidDestinationException: Cannot publish to a deleted Destination: temp-queue://ID:Duracell-61594-634642411329432145-1:0:1

      Test:
      1. Start Message bus
      2. Start server code.
      3. Stop Message bus
      4. Start Message bus
      5. Start client code.

      The client/server uses the request/response pattern.

      I don't have a unit test since it doesn't happen all the time. But if happens often enough that I am sure there is a race condition bug here
      somewhere. And I think it's in NMS since I can see these log lines:

      AdvisoryConsumer adding: temp-queue://ID:Duracell-61594-634642411329432145-1:0:1

      ...Get InvalidDestinationException here...

      AdvisoryConsumer removing: temp-queue://ID:Duracell-61594-634642411329432145-1:0:1

      Attachments

        Activity

          People

            jgomes Jim Gomes
            fgynnild Frank Gynnild
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: