Hi Since we are re-doing Camel 2.9.0, I wonder if we should wait for the CXF 2.5.1 release and try upgrade and use that release? The CXF 2.5.1 is about to be released?
On Fri, Dec 16, 2011 at 7:28 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Fri, Dec 16, 2011 at 6:02 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: >> On Fri, Dec 16, 2011 at 4:55 PM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: >>> I will redo this release. I also looking into an issue in camel-quartz which >>> looks like a bug. Once CAMEL-4786 is fixed I will restart the release >>> builds. >>> >> >> I am running a full test locally before committing anything about 4786. >> > > I have committed a fix for CAMEL-4786 on trunk. > > >> However it looks good so far. The throttler EIP will no longer eat up >> all memory, if you add messages >> faster to it, than it can take out and process. >> >> >> >>> Hadrian >>> >>> >>> On 12/16/2011 09:40 AM, Claus Ibsen wrote: >>>> >>>> Hi >>>> >>>> I discovered a critical bug, which at runtime could cause Camel to >>>> re-wrap the same processor in the routes, causing an every growing >>>> processor path. >>>> See the stacktrace in the JIRA: >>>> https://issues.apache.org/jira/browse/CAMEL-4787 >>>> >>>> I think that warrants a -1 vote, as it can cause OOME issues for >>>> people running Camel in production. >>>> >>>> I am also working on https://issues.apache.org/jira/browse/CAMEL-4786 >>>> to fik an issue reported that the throttler EIP can cause OOME because >>>> the scheduled thread pool will just keep intake new tasks (this is how >>>> the JDK thread pool is). To fix that problem we need to detect when >>>> we have reached an upper task limit, and reject tasks. This would then >>>> resolve the problem for the end users as the throttler EIP will not >>>> keep growing and cause OOME as well. >>>> >>>> I would like to have CAMEL-4786 fixed as well for the Camel 2.9.0 release. >>>> >>>> Therefore I vote -1 >>>> >>>> >>>> >>>> >>>> On Thu, Dec 15, 2011 at 3:20 PM, Hadrian Zbarcea<hzbar...@gmail.com> >>>> wrote: >>>>> >>>>> A new release candidate apache-camel-2.9.0 final is out with >>>>> approximately >>>>> 464 issues resolved so far: improvements and bug fixes [1]. >>>>> >>>>> Please find the staging repo here: >>>>> https://repository.apache.org/content/repositories/orgapachecamel-343/ >>>>> >>>>> The tarballs are here >>>>> >>>>> https://repository.apache.org/content/repositories/orgapachecamel-343/org/apache/camel/apache-camel/2.9.0/ >>>>> >>>>> Tag: >>>>> http://svn.apache.org/repos/asf/camel/tags/camel-2.9.0/ >>>>> >>>>> Please review, help out with testing and vote to approve this release >>>>> binary. Your vote counts! >>>>> >>>>> [ ] +1 Release the binary as Apache Camel 2.9.0 >>>>> [ ] -1 Veto the release (provide specific comments) >>>>> Vote is open for at least 72 hours. >>>>> >>>>> Here's my +1 >>>>> Hadrian >>>>> >>>>> [1] >>>>> >>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12316374 >>>>> >>>>> -- >>>>> Hadrian Zbarcea >>>>> Principal Software Architect >>>>> Talend, Inc >>>>> http://coders.talend.com/ >>>>> http://camelbot.blogspot.com/ >>>> >>>> >>>> >>>> >>> >>> -- >>> Hadrian Zbarcea >>> Principal Software Architect >>> Talend, Inc >>> http://coders.talend.com/ >>> http://camelbot.blogspot.com/ >> >> >> >> -- >> Claus Ibsen >> ----------------- >> FuseSource >> Email: cib...@fusesource.com >> Web: http://fusesource.com >> Twitter: davsclaus, fusenews >> Blog: http://davsclaus.blogspot.com/ >> Author of Camel in Action: http://www.manning.com/ibsen/ > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: cib...@fusesource.com > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/ -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
