Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-7897

Camel consumes & discards activemq messages after suspension

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • 2.14.0
    • None
    • camel-jms
    • None

    • All

    • Unknown

    Description

      When used with a PooledConnectionFactory, a Camel Route that consumes via JMS from an ActiveMQ endpoint will read one extra message and simply discard it after it has completed suspension, if that message is sent within a second of suspension being completed.

      See attached test case.

      As far as I can tell this is because nothing interrupts the taskExecutor on DefaultMessageListenerContainer when a route is suspended.

      Expected behaviour - once a route is suspended, any messages sent to the queue from which it consumes should remain on that queue.

      Attachments

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

          People

            davsclaus Claus Ibsen
            mahoney Robert Elliot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment