camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5793) Clients referring to seda: endpoint without options in URI, create implicit endpoints
Date Sun, 25 Nov 2012 17:32:58 GMT


Claus Ibsen commented on CAMEL-5793:

Camel was working as designed. Though for Camel 2.11 we have improved this to validate the
endpoints and fail if they have been mis-configured. As well there is INFO logging of the
endpoints with the queues and their sizes in use. This allows end users to spot their mis
configurations better.

Its generally best to configure the size on the consumer, and leave out this option when using
the producer.
> Clients referring to seda: endpoint without options in URI, create implicit endpoints
> -------------------------------------------------------------------------------------
>                 Key: CAMEL-5793
>                 URL:
>             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:

View raw message