Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
Consumers that starts the routing by calling the first processor, have AsyncCallback as lambda which creates a new instance per message.
If pooled we can for some consumers avoid this and reuse the lambda. But we need to find a way to make this transparent so the lambda can work in prototype vs pooled mode.
Attachments
Issue Links
- relates to
-
CAMEL-16279 camel-core - Optimize routing engine to reuse internal state objects for GC reduction
- Resolved