You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jan-Helge Bergesen (JIRA)" <ji...@apache.org> on 2012/11/16 08:18:11 UTC
[jira] [Updated] (CAMEL-5793) Clients referring to seda: endpoint
without options in URI, create implicit endpoints
[ https://issues.apache.org/jira/browse/CAMEL-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan-Helge Bergesen updated CAMEL-5793:
--------------------------------------
Attachment: clients-without-seda-options.PNG
clients-with-seda-options.png
clients-without-seda-options.png show the MBeans created when the clients only refer to the seda endpoint without options.
clients-without-seda-options.png show the MBeans created when the clients refer to the seda endpoint with all options, as the "from" DSL states.
> Clients referring to seda: endpoint without options in URI, create implicit endpoints
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-5793
> URL: https://issues.apache.org/jira/browse/CAMEL-5793
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.10.2
> Environment: Observed on Windows XP
> Reporter: Jan-Helge Bergesen
> Attachments: clients-without-seda-options.PNG, clients-with-seda-options.png
>
>
> Create a "from()" endpoint with configuration:
> {code}
> from("seda:something?size=10000&blockWhenFull=true")...
> {code}
> Let clients push to the endpoint without options:
> {code}
> to("seda:something")...
> {code}
> Camel then creates two seda endpoints: one bounded (with options) and one unbounded.
> Both endpoints receive messages from the client, but the unbounded one doesn't seem to do much other than buffer things?
> Possible this leads to duplicates on the process following "from" (not tested).
> For our case, this lead to an OOM under an extreme (200-300% of expected peak) load test.
> Will attach screenshots from jVisualVM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira