You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Marco Crivellaro <mc...@optasportsdata.com> on 2011/03/22 18:31:04 UTC
Exchange.MAXIMUM_CACHE_POOL_SIZE is not affecting producers created
by recipientList
Camel 2.7.0-SNAPSHOT
I've tried to set the maximum producer cache size to 5 and send messages to
100 of different ftp endpoints (using several recipientList exchanges),
checking the jmap heap dump I've found out there were 100 FTPClient,
FTPConfigurations, FTPOperations ... loaded in memory. Is there a way to
limit the producer cache size when using recipientList?
--
View this message in context: http://camel.465427.n5.nabble.com/Exchange-MAXIMUM-CACHE-POOL-SIZE-is-not-affecting-producers-created-by-recipientList-tp4257273p4257273.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Exchange.MAXIMUM_CACHE_POOL_SIZE is not affecting producers
created by recipientList
Posted by Marco Crivellaro <mc...@optasportsdata.com>.
Excellent!
That is something I was looking for since Camel 2.5!
--
View this message in context: http://camel.465427.n5.nabble.com/Exchange-MAXIMUM-CACHE-POOL-SIZE-is-not-affecting-producers-created-by-recipientList-tp4257273p4279856.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Exchange.MAXIMUM_CACHE_POOL_SIZE is not affecting producers
created by recipientList
Posted by Claus Ibsen <cl...@gmail.com>.
You may also want to take a look at
https://issues.apache.org/jira/browse/CAMEL-3827
As Camel has an endpoint cache as well.
On Fri, Apr 1, 2011 at 5:45 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Works fine. I added an unit test
> http://svn.apache.org/viewvc?rev=1087773&view=rev
>
>
> On Fri, Mar 25, 2011 at 2:05 PM, Marco Crivellaro
> <mc...@optasportsdata.com> wrote:
>> this affects 2.7.0 release too
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.com/Exchange-MAXIMUM-CACHE-POOL-SIZE-is-not-affecting-producers-created-by-recipientList-tp4257273p4264057.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> CamelOne 2011: http://fusesource.com/camelone2011/
> Twitter: davsclaus
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: Exchange.MAXIMUM_CACHE_POOL_SIZE is not affecting producers
created by recipientList
Posted by Marco Crivellaro <mc...@optasportsdata.com>.
Thank you, I will check it using the example provided.
--
View this message in context: http://camel.465427.n5.nabble.com/Exchange-MAXIMUM-CACHE-POOL-SIZE-is-not-affecting-producers-created-by-recipientList-tp4257273p4275924.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Exchange.MAXIMUM_CACHE_POOL_SIZE is not affecting producers
created by recipientList
Posted by Claus Ibsen <cl...@gmail.com>.
Works fine. I added an unit test
http://svn.apache.org/viewvc?rev=1087773&view=rev
On Fri, Mar 25, 2011 at 2:05 PM, Marco Crivellaro
<mc...@optasportsdata.com> wrote:
> this affects 2.7.0 release too
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Exchange-MAXIMUM-CACHE-POOL-SIZE-is-not-affecting-producers-created-by-recipientList-tp4257273p4264057.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: Exchange.MAXIMUM_CACHE_POOL_SIZE is not affecting producers
created by recipientList
Posted by Marco Crivellaro <mc...@optasportsdata.com>.
this affects 2.7.0 release too
--
View this message in context: http://camel.465427.n5.nabble.com/Exchange-MAXIMUM-CACHE-POOL-SIZE-is-not-affecting-producers-created-by-recipientList-tp4257273p4264057.html
Sent from the Camel - Users mailing list archive at Nabble.com.