You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Andreas Becker <a....@web.de> on 2020/08/11 13:25:55 UTC

Potential bug in ThreadPoolProfile.clone ?

Hello,
 
can you please check the following code in the current version of Camel which we supect to be a bug:
 
Class: org.apache.camel.spi.ThreadPoolProfile

Method: clone

Problem: In the clone member poolSize is set to the value of maxPoolSize:
 
cloned.setMaxPoolSize(maxPoolSize);
cloned.setPoolSize(maxPoolSize);

If I see this correctly this bug came in with CAMEL-4244 on Aug 18, 2011.

Thank you very much,
best regards,

Andreas Becker




 
 

Re: Potential bug in ThreadPoolProfile.clone ?

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Yes you are right. That is a little bug. I took the liberty of fixing
this on the 3.x branches.

On Tue, Aug 11, 2020 at 3:54 PM Andreas Becker <a....@web.de> wrote:
>
> Hello,
>
> can you please check the following code in the current version of Camel which we supect to be a bug:
>
> Class: org.apache.camel.spi.ThreadPoolProfile
>
> Method: clone
>
> Problem: In the clone member poolSize is set to the value of maxPoolSize:
>
> cloned.setMaxPoolSize(maxPoolSize);
> cloned.setPoolSize(maxPoolSize);
>
> If I see this correctly this bug came in with CAMEL-4244 on Aug 18, 2011.
>
> Thank you very much,
> best regards,
>
> Andreas Becker
>
>
>
>
>
>



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2