[camel-groovy] Several Camel contexts stuck with inflight exchanges

Solution Verified - Updated -

Issue

  • We have several Camel contexts running on our Fuse node. It has occurred twice now that several of these interfaces got stuck at somewhat similar spots in the Camel routes. From the list of in-flight exchanges I can see the node id of the in-flight exchanges and in all cases there is a tag being used in the routes at that position.
  • I checked all in-flight exchanges and how long they have been stuck (in-flight duration). If they are blocking each other, the one with the highest duration should be the source of the problem. It seems that one with a groovy tag like this is responsible
<transform>
<groovy>camelContext.getRegistry().lookup("SomeFilesConfig").retrieveElements(request.headers.get("SomeFileName"))</groovy>
</transform>

Environment

  • Red Hat JBoss Fuse
    • 6.3.0
  • camel-groovy

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content