[
https://issues.apache.org/jira/browse/CAMEL-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503501#comment-13503501
]
Claus Ibsen commented on CAMEL-5793:
------------------------------------
>From Camel 2.11 onwards we now validate the queue size when a shared queue is
>being used by another endpoint. And if the sub sequent endpoints have a
>different queue size, then Camel will now fail creating the endpoint. This
>would allow end users to fix their mistakes.
> 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
> Assignee: Claus Ibsen
> 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
