[
https://issues.apache.org/jira/browse/CAMEL-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-8640.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.15.3
Thanks for the PR. I had to adjust it a bit to apply to master first.
eg we always merge to master first, and then cherry pick to patch branches.
> BacklogTracer allocates 100k elements for an array even it is not enabled
> -------------------------------------------------------------------------
>
> Key: CAMEL-8640
> URL: https://issues.apache.org/jira/browse/CAMEL-8640
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.15.1
> Reporter: Mateusz Nowakowski
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.16.0, 2.15.3
>
>
> By default each camel context has one BacklogTracer which is by default
> disabled.
> However BacklogTracer contains a queue with
> {code}
> public static final int MAX_BACKLOG_SIZE = 100 * 1000;
> private final Queue<DefaultBacklogTracerEventMessage> queue = new
> ArrayBlockingQueue<DefaultBacklogTracerEventMessage>(MAX_BACKLOG_SIZE);
> {code}
> The easiest way:
> is it possible to replace it with LinkedBlockingQueue(int capacity)?
> Ideally the object could be initialized only when it is enabled but it seems
> BacklogTracer is not fully encapsulated (the queue reference is maintained
> also outside BacklogTracer in BacklogTracerAdvice)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
