[
https://issues.apache.org/jira/browse/CAMEL-24619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18111485#comment-18111485
]
Torsten Mielke commented on CAMEL-24619:
----------------------------------------
Glad you got to the bottom of it [~ivanra].
{quote}In any case, even if delete permission exist, the constant creation and
deletion of queues places an additional load on the broker.
{quote}
That is true but can be avoided by using default cacheLevelName of
{{{}CACHE_CONSUMER{}}}.
Only in distributed transaction use cases, you need cannot go with
{{{}CACHE_CONSUMER{}}}, as the XA session is tied to the consumer session in
Spring JMS.
> camel-jms + Artemis: the default topic consumer causes an OOM on the broker.
> ----------------------------------------------------------------------------
>
> Key: CAMEL-24619
> URL: https://issues.apache.org/jira/browse/CAMEL-24619
> Project: Camel
> Issue Type: Bug
> Components: came-jms
> Reporter: Ivan Ravin
> Assignee: Guillaume Nodet
> Priority: Major
>
> Maybe it's known problem. The Artemis broker creates a temporary queue for
> each topic consumer. camel-jms component can create Default and Simple
> consumer. A simple consumer is essentially a listener, and all works fine.
> The default consumer attempts to retrieve a message every second, and every
> second creates temporary queue on topic address, which live until the
> connection is terminated. This leads OOM on the broker.
> To work around this situation, you can specify in the URI
> consumerType=Simple, but default behavior is dangerous.
> It might not be a bad idea by default to switch consumer type to Simple for
> topic consumers?
> This is complex problem that affects camel-jms + Artemis topics + (maybe)
> pooled connection factory
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
