Discussion:
seda default queue size
Dennis Holunder
2018-09-11 09:30:29 UTC
Permalink
Hi,

according to the seda documetation
https://github.com/apache/camel/blob/master/camel-core/src/main/docs/seda-component.adoc
the default size value is 2147483647. However I observe that it will
actually default to 1000, which is the default value of queueSize
option. Source code of SedaEndpoint:

Integer size = getSize() == Integer.MAX_VALUE ? null : getSize();

Why there are two size options with different default values?

Dan
Claus Ibsen
2018-09-19 10:48:02 UTC
Permalink
Hi

In the beginning there was only one size you had to set per endpoint.
So later we added a default size on the component so you can set it
once.
Then alter that default was reduced from infinitie to 1000. So today
its 1000 and there is a glitch in the docs.
Post by Dennis Holunder
Hi,
according to the seda documetation
https://github.com/apache/camel/blob/master/camel-core/src/main/docs/seda-component.adoc
the default size value is 2147483647. However I observe that it will
actually default to 1000, which is the default value of queueSize
Integer size = getSize() == Integer.MAX_VALUE ? null : getSize();
Why there are two size options with different default values?
Dan
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Claus Ibsen
2018-09-19 10:50:39 UTC
Permalink
Hi

Its this ticket about the 1000 as new default size
https://issues.apache.org/jira/browse/CAMEL-12542
Post by Claus Ibsen
Hi
In the beginning there was only one size you had to set per endpoint.
So later we added a default size on the component so you can set it
once.
Then alter that default was reduced from infinitie to 1000. So today
its 1000 and there is a glitch in the docs.
Post by Dennis Holunder
Hi,
according to the seda documetation
https://github.com/apache/camel/blob/master/camel-core/src/main/docs/seda-component.adoc
the default size value is 2147483647. However I observe that it will
actually default to 1000, which is the default value of queueSize
Integer size = getSize() == Integer.MAX_VALUE ? null : getSize();
Why there are two size options with different default values?
Dan
--
Claus Ibsen
-----------------
Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Claus Ibsen
2018-09-19 11:32:15 UTC
Permalink
Hi

I have fixed the docs
Post by Claus Ibsen
Hi
Its this ticket about the 1000 as new default size
https://issues.apache.org/jira/browse/CAMEL-12542
Post by Claus Ibsen
Hi
In the beginning there was only one size you had to set per endpoint.
So later we added a default size on the component so you can set it
once.
Then alter that default was reduced from infinitie to 1000. So today
its 1000 and there is a glitch in the docs.
Post by Dennis Holunder
Hi,
according to the seda documetation
https://github.com/apache/camel/blob/master/camel-core/src/main/docs/seda-component.adoc
the default size value is 2147483647. However I observe that it will
actually default to 1000, which is the default value of queueSize
Integer size = getSize() == Integer.MAX_VALUE ? null : getSize();
Why there are two size options with different default values?
Dan
--
Claus Ibsen
-----------------
Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
DariusGmail
2018-09-24 03:20:09 UTC
Permalink
I use RecipientList with a custom Aggregator. If there is an error in a
sub-route (one of the "recipients") that is "handled" there.
I want the main route to continue
In the Aggregator, I was setting:
   if (oldExchange == null) {
       oldExchange = newExchange;
  }

Because of this, the Exchange had properties like "CamelExceptionCaught"
and "CamelErrorHandlerHandled"
And, because these were present in the Aggregated Exchange the flow was
not continuing through the outer route

After removing these two, the flow continued through the main route

I have two questions about this:
1. Does this sound like the right way to handle things in the Aggregator?
2. Any other Properties that I need to watch out for an remove, if present?

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Loading...