Uploaded image for project: 'FUSE Mediation Router'
  1. FUSE Mediation Router
  2. MR-933

Exchange Leak Caused By pollEnrich

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.14.0.redhat-62-xx
    • 2.12.0.redhat-61379
    • None
    • None
    • Hide

      All it takes is a simple route such as this:

      <route id="testRoute">
       <from uri="timer:testTimer?period=2s" />
       <pollEnrich uri="activemq:test.queue" />
      </route>
      

      And have the pollEnrich URI point to a non-existent ActiveMQ broker. You will note exceptions and for each set of exceptions there will be a dangling Exchange. The dangling Exchanges become evident when stopping the context. Also, adding an exception handler doesn't help, as the exception is never handled.

      Customer states the following, "Debugging the PollEnricher it appears that an exception on the receive call is not caught".

      Show
      All it takes is a simple route such as this: <route id= "testRoute" > <from uri= "timer:testTimer?period=2s" /> <pollEnrich uri= "activemq:test.queue" /> </route> And have the pollEnrich URI point to a non-existent ActiveMQ broker. You will note exceptions and for each set of exceptions there will be a dangling Exchange. The dangling Exchanges become evident when stopping the context. Also, adding an exception handler doesn't help, as the exception is never handled. Customer states the following, "Debugging the PollEnricher it appears that an exception on the receive call is not caught".

      If you use a pollEnrich in a route and it encounters an error (e.g., miss-configured AMQ URI) then each time the pollEnrich is invoked, the result is a dangling inflight Exchange that is never cleaned up. A side effect is that a graceful shutdown of the context will block until the default 300 seconds.

            cibsen@redhat.com Claus Ibsen
            Argo_Integration Travis North (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: