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 Nabbl
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 wrote:
> Works fine. I added an unit test
> http://svn.apache.org/viewvc?rev=1087773&view=rev
>
>
> On Fri, Mar 25, 2011 at 2
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.
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
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-affecti
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.
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 t
