You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Artem Shumilov (Jira)" <ji...@apache.org> on 2023/05/26 12:39:00 UTC

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

Artem Shumilov created CAMEL-19394:
--------------------------------------

             Summary: 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
         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)