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:16:12 UTC
[jira] [Created] (CAMEL-5793) Clients referring to seda: endpoint
without options in URI, create implicit endpoints
Jan-Helge Bergesen created CAMEL-5793:
-----------------------------------------
Summary: 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
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
[jira] [Assigned] (CAMEL-5793) Clients referring to seda: endpoint
without options in URI, create implicit endpoints
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-5793:
----------------------------------
Assignee: Claus Ibsen
> 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
[jira] [Updated] (CAMEL-5793) Clients referring to seda: endpoint
without options in URI, create implicit endpoints
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-5793:
-------------------------------
Fix Version/s: 2.11.0
Issue Type: Improvement (was: Bug)
> 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: Improvement
> Components: camel-core
> Affects Versions: 2.10.2
> Environment: Observed on Windows XP
> Reporter: Jan-Helge Bergesen
> Assignee: Claus Ibsen
> Fix For: 2.11.0
>
> 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
[jira] [Commented] (CAMEL-5793) Clients referring to seda: endpoint
without options in URI, create implicit endpoints
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503485#comment-13503485 ]
Claus Ibsen commented on CAMEL-5793:
------------------------------------
There will be 2 endpoints, but the queue itself will be shared. Though its the 1st endpoint that creates the queue, that determines the queue size. So if "seda:something" creates the queue first, its unbounded.
> 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
[jira] [Commented] (CAMEL-5793) Clients referring to seda: endpoint
without options in URI, create implicit endpoints
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CAMEL-5793) Clients referring to seda: endpoint
without options in URI, create implicit endpoints
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503523#comment-13503523 ]
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: 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
[jira] [Updated] (CAMEL-5793) Clients referring to seda: endpoint
without options in URI, create implicit endpoints
Posted by "Jan-Helge Bergesen (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (CAMEL-5793) Clients referring to seda: endpoint
without options in URI, create implicit endpoints
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-5793.
--------------------------------
Resolution: Fixed
> 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: Improvement
> Components: camel-core
> Affects Versions: 2.10.2
> Environment: Observed on Windows XP
> Reporter: Jan-Helge Bergesen
> Assignee: Claus Ibsen
> Fix For: 2.11.0
>
> 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