[jira] [Resolved] (CAMEL-19394) Camel SEDA issue with heap

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-19394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-19394.
---------------------------------
    Resolution: Invalid

Yes ask on mailing list / chat first.

Also if you create a log of dynamic queues then you have a lot more memory use, seda is not for unlimited queues. Its for a set of static queues to have async messaging between routes.

Its not an message broker or something like that - use JMS or Kafka etc for that.

> Camel SEDA issue with heap
> --------------------------
>
>                 Key: CAMEL-19394
>                 URL: https://issues.apache.org/jira/browse/CAMEL-19394
>             Project: Camel
>          Issue Type: Task
>          Components: camel-core
>            Reporter: Artem Shumilov
>            Priority: Major
>         Attachments: screenshot-1.png, screenshot-3.png
>
>
> Hi, 
> I am using the 2.23.1 Camel version and faced some problems with SEDA when I use it with dynamically named queues.
> SedaComponent creates a lot of queues in its inner "queues" map and creates a lot of SedaEndpoints. That increases memory usage and fills app's heap with SEDA, which provides performance degradation because of unstoppable usage of GC.
> Does anyone know how to clean SEDA after work properly?
> 1) SEDA "queues" fields example  !screenshot-1.png!
> 2) SedaEndpoints:
> !screenshot-3.png!
> If i should write my question somewhere else, advice me where please :)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)