[
https://issues.apache.org/activemq/browse/CAMEL-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58670#action_58670
]
Claus Ibsen commented on CAMEL-2558:
------------------------------------
Its more work than at first sight.
This would require end users to {{start}} their {{ProducerTemplate}} before
use. In fact the javadoc already states this. But currently you could still use
it without have started it.
This will enforce better resource management as end users must start/stop those
templates.
It now has a getter/setter for {{maximumCacheSize}} so you can use another
value than the default of 1000.
You can do this from both Java and Spring XML as <template/> has it as an
attribute.
A global option will also be possible on CamelContext so you can configure this
for all cache pools.
Also the EIP patterns which uses a ProducerCache will be retrofitted:
- routing slip
- send (to / toAsync / wireTap etc.)
- recipient list
I wonder if they should
- share one global cache
- have their local cache (= as now)
- option in the DSL to set an individual cache size
> Configurable cache size for ConsumerTemplate and ProducerTemplate
> ------------------------------------------------------------------
>
> Key: CAMEL-2558
> URL: https://issues.apache.org/activemq/browse/CAMEL-2558
> Project: Apache Camel
> Issue Type: Improvement
> Affects Versions: 2.2.0
> Reporter: Norman Maurer
> Assignee: Claus Ibsen
> Fix For: 2.3.0
>
>
> The cache size of the ConsumerTemplate and ProducerTemplate should be
> configurable to help to prevent OOM when every call use an other endpoint uri.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
