[CAMEL-2650] @Produce and @Consume injected on prototype beans needs a mechanism for automatic stopping when no longer in use

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.2.0
• Fix Version/s: Future
• Component/s: camel-spring
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 15/Apr/10 11:26
• Updated: 25/Mar/15 08:24
• Resolved: 25/Mar/15 08:24

Description

This only applies for prototype scoped POJOs which uses @Produce or @Consume to inject a Camel Producer/Consumer.

As the prototype scoped POJO is short lived and there could potentially be created many of those POJOs.
Then @Produce / @Consume will inject new instances of Producer / Consumer as well.

And since there is no standard way of knowing when the POJO is no longer in need, which is where we can to stop the Producer/Consumer.

For singleton scoped this is not a problem as CamelContext will keep track on the created Producer/Consumer in its internal servicesToClose.
Which is then stopped when CamelContext stops.

For prototype we need a different strategy such as

• proxy it to use pooled producers/consumers which CamelContext manage the lifecycle
• use a shared ProducerTemplate / ConsumerTemplate instead which CamelContext manages the lifecycle
• other
• maybe some thread local tricks