You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Christian Müller <ch...@gmail.com> on 2013/04/11 12:50:49 UTC
[VOTE] Release Apache Camel 2.11.0 (take 3)
After 9 month of development, we have a new minor release candidate
apache-camel-2.11.0 ready.
It comes with 659 issues resolved: new features, improvements and bug fixes
[1]. You can find the release notes here [2].
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-092/
The tarballs are here
https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
Tag:
http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
Please review, help out with testing and vote to approve this release
binary. Please mention what you tested to prevent duplicate work. Your vote
counts!
[ ] +1 Release the binary as Apache Camel 2.11.0
[ ] -1 Veto the release (provide specific comments)
Vote is open for at least 72 hours.
Thanks in advance,
Christian
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
[2]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by David Karlsen <da...@gmail.com>.
second that
2013/4/14 Babak Vahdat <ba...@swissonline.ch>
>
>
> Am 14.04.13 13:09 schrieb "Raul Kripalani" unter <ra...@evosent.com>:
>
> >Hi Claus
> >
> >+1 to redo the release.
> >
> >These stats are really useful for profiling.
> >
> >I'd rather turn the counters into plain longs and make it clear to users
> >(in the log statements and documentation) that the figures are merely
> >indicative and not fully accurate.
>
> Hi
>
> I think more than accuracy and precision using plain long the main problem
> would be to have really WIRED numbers, that's also NEGATIVE numbers even
> if you would ONLY increment, mostly reproduciable on multi-core boxes
> (verifying/testing this is trivial & straightforward).
>
> Just wonder if we could disable this per default but let the stats get
> enabled somehow through a flag, property or the likes. Then ppl can decide
> on their own what's more important to them: better performance versus
> statistics.
>
> Babak
>
> >
> >Regards,
> >Raúl.
> > On 14 Apr 2013 09:42, "Claus Ibsen" <cl...@gmail.com> wrote:
> >
> >> Hi
> >>
> >> All the examples with those WARN about thread pools on shutdown should
> >> been fixed on trunk.
> >>
> >> I wonder if we should redo the release as I want to fix by removing
> >> the overhead of these stats. Its IMHO better to have higher
> >> performance. And there is no good way to do the counters without the
> >> threads contention. We could use plain long for the counters, but then
> >> they are not accurate as a ++ on a long value is not atomic.
> >>
> >> https://issues.apache.org/jira/browse/CAMEL-6264
> >>
> >>
> >>
> >> On Sat, Apr 13, 2013 at 7:25 PM, Christian Müller
> >> <ch...@gmail.com> wrote:
> >> > I tested the following examples:
> >> >
> >> > camel-example-cxf-blueprint:
> >> > OK
> >> >
> >> > camel-example-cxf-osgi
> >> > FAILED (see CAMEL-6257)
> >> >
> >> > camel-example-aggregate
> >> > OK, but it logged some WARNings by stopping the service:
> >> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
> >> > Waited 10.002 seconds for ExecutorService:
> >> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
> >>
> >>[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%2
> >>8enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> >> > to terminate...
> >> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
> >> > Forcing shutdown of ExecutorService:
> >> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
> >>
> >>[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%2
> >>8enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> >> > due first await termination elapsed.
> >> >
> >> > camel-example-bam
> >> > some ERRORs in the log
> >> >
> >> > camel-example-cafe
> >> > OK
> >> >
> >> > camel-example-cdi
> >> > OK
> >> >
> >> > camel-example-console
> >> > OK, but it logged some WARNings by stopping the service:
> >> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
> >> > Waited 10.002 seconds for ExecutorService:
> >> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
> >> [stream://in?promptMessage=Enter+something%3A+]
> >> > to terminate...
> >> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
> >> > Cannot completely force shutdown of ExecutorService:
> >> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
> >> [stream://in?promptMessage=Enter+something%3A+]
> >> > due second await termination elapsed.
> >> >
> >> > camel-example-cxf
> >> > OK
> >> >
> >> > camel-example-cxf-proxy
> >> > OK, but the README needs an update because we use dynamic ports
> >> (available
> >> > port finder). DONE
> >> >
> >> > camel-example-docs
> >> > Doesn't generated the images for the index.html file
> >> >
> >> > Still testing the other examples...
> >> >
> >> > Best,
> >> > Christain
> >> >
> >> >
> >> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> >> > christian.mueller@gmail.com> wrote:
> >> >
> >> >> After 9 month of development, we have a new minor release candidate
> >> >> apache-camel-2.11.0 ready.
> >> >> It comes with 659 issues resolved: new features, improvements and bug
> >> >> fixes [1]. You can find the release notes here [2].
> >> >>
> >> >> Please find the staging repo here:
> >> >>
> >>https://repository.apache.org/content/repositories/orgapachecamel-092/
> >> >>
> >> >> The tarballs are here
> >> >>
> >> >>
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachecamel-092/org
> >>/apache/camel/apache-camel/2.11.0/
> >> >>
> >> >> Tag:
> >> >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
> >> >>
> >> >> Please review, help out with testing and vote to approve this release
> >> >> binary. Please mention what you tested to prevent duplicate work.
> >>Your
> >> vote
> >> >> counts!
> >> >>
> >> >> [ ] +1 Release the binary as Apache Camel 2.11.0
> >> >> [ ] -1 Veto the release (provide specific comments)
> >> >> Vote is open for at least 72 hours.
> >> >>
> >> >> Thanks in advance,
> >> >> Christian
> >> >>
> >> >> [1]
> >> >>
> >>
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20
> >>fixVersion%20%3D%20%222.11.0%22
> >> >> [2]
> >> >>
> >>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211
> >>&version=12321695
> >> >>
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> Red Hat, Inc.
> >> FuseSource is now part of Red Hat
> >> Email: cibsen@redhat.com
> >> Web: http://fusesource.com
> >> Twitter: davsclaus
> >> Blog: http://davsclaus.com
> >> Author of Camel in Action: http://www.manning.com/ibsen
> >>
>
>
>
--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Good idea about the option true|false. I logged a ticket
https://issues.apache.org/jira/browse/CAMEL-6282
On Sun, Apr 14, 2013 at 1:54 PM, Raul Kripalani <ra...@evosent.com> wrote:
> Yes, in that case I agree too this is the most sensible option.
>
> +1
>
> Raúl.
> On 14 Apr 2013 12:38, "Christian Müller" <ch...@gmail.com>
> wrote:
>
>> +1 for an option so the user can decide whether he want the stats or not.
>>
>> Sent from a mobile device
>> Am 14.04.2013 13:30 schrieb "Babak Vahdat" <ba...@swissonline.ch>:
>>
>> >
>> >
>> > Am 14.04.13 13:09 schrieb "Raul Kripalani" unter <ra...@evosent.com>:
>> >
>> > >Hi Claus
>> > >
>> > >+1 to redo the release.
>> > >
>> > >These stats are really useful for profiling.
>> > >
>> > >I'd rather turn the counters into plain longs and make it clear to users
>> > >(in the log statements and documentation) that the figures are merely
>> > >indicative and not fully accurate.
>> >
>> > Hi
>> >
>> > I think more than accuracy and precision using plain long the main
>> problem
>> > would be to have really WIRED numbers, that's also NEGATIVE numbers even
>> > if you would ONLY increment, mostly reproduciable on multi-core boxes
>> > (verifying/testing this is trivial & straightforward).
>> >
>> > Just wonder if we could disable this per default but let the stats get
>> > enabled somehow through a flag, property or the likes. Then ppl can
>> decide
>> > on their own what's more important to them: better performance versus
>> > statistics.
>> >
>> > Babak
>> >
>> > >
>> > >Regards,
>> > >Raúl.
>> > > On 14 Apr 2013 09:42, "Claus Ibsen" <cl...@gmail.com> wrote:
>> > >
>> > >> Hi
>> > >>
>> > >> All the examples with those WARN about thread pools on shutdown should
>> > >> been fixed on trunk.
>> > >>
>> > >> I wonder if we should redo the release as I want to fix by removing
>> > >> the overhead of these stats. Its IMHO better to have higher
>> > >> performance. And there is no good way to do the counters without the
>> > >> threads contention. We could use plain long for the counters, but then
>> > >> they are not accurate as a ++ on a long value is not atomic.
>> > >>
>> > >> https://issues.apache.org/jira/browse/CAMEL-6264
>> > >>
>> > >>
>> > >>
>> > >> On Sat, Apr 13, 2013 at 7:25 PM, Christian Müller
>> > >> <ch...@gmail.com> wrote:
>> > >> > I tested the following examples:
>> > >> >
>> > >> > camel-example-cxf-blueprint:
>> > >> > OK
>> > >> >
>> > >> > camel-example-cxf-osgi
>> > >> > FAILED (see CAMEL-6257)
>> > >> >
>> > >> > camel-example-aggregate
>> > >> > OK, but it logged some WARNings by stopping the service:
>> > >> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
>> > >> > Waited 10.002 seconds for ExecutorService:
>> > >> >
>> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
>> > >>
>> >
>> >>[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%2
>> > >>8enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
>> > >> > to terminate...
>> > >> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
>> > >> > Forcing shutdown of ExecutorService:
>> > >> >
>> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
>> > >>
>> >
>> >>[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%2
>> > >>8enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
>> > >> > due first await termination elapsed.
>> > >> >
>> > >> > camel-example-bam
>> > >> > some ERRORs in the log
>> > >> >
>> > >> > camel-example-cafe
>> > >> > OK
>> > >> >
>> > >> > camel-example-cdi
>> > >> > OK
>> > >> >
>> > >> > camel-example-console
>> > >> > OK, but it logged some WARNings by stopping the service:
>> > >> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
>> > >> > Waited 10.002 seconds for ExecutorService:
>> > >> >
>> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
>> > >> [stream://in?promptMessage=Enter+something%3A+]
>> > >> > to terminate...
>> > >> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
>> > >> > Cannot completely force shutdown of ExecutorService:
>> > >> >
>> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
>> > >> [stream://in?promptMessage=Enter+something%3A+]
>> > >> > due second await termination elapsed.
>> > >> >
>> > >> > camel-example-cxf
>> > >> > OK
>> > >> >
>> > >> > camel-example-cxf-proxy
>> > >> > OK, but the README needs an update because we use dynamic ports
>> > >> (available
>> > >> > port finder). DONE
>> > >> >
>> > >> > camel-example-docs
>> > >> > Doesn't generated the images for the index.html file
>> > >> >
>> > >> > Still testing the other examples...
>> > >> >
>> > >> > Best,
>> > >> > Christain
>> > >> >
>> > >> >
>> > >> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
>> > >> > christian.mueller@gmail.com> wrote:
>> > >> >
>> > >> >> After 9 month of development, we have a new minor release candidate
>> > >> >> apache-camel-2.11.0 ready.
>> > >> >> It comes with 659 issues resolved: new features, improvements and
>> bug
>> > >> >> fixes [1]. You can find the release notes here [2].
>> > >> >>
>> > >> >> Please find the staging repo here:
>> > >> >>
>> > >>https://repository.apache.org/content/repositories/orgapachecamel-092/
>> > >> >>
>> > >> >> The tarballs are here
>> > >> >>
>> > >> >>
>> > >>
>> > >>
>> >
>> https://repository.apache.org/content/repositories/orgapachecamel-092/org
>> > >>/apache/camel/apache-camel/2.11.0/
>> > >> >>
>> > >> >> Tag:
>> > >> >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>> > >> >>
>> > >> >> Please review, help out with testing and vote to approve this
>> release
>> > >> >> binary. Please mention what you tested to prevent duplicate work.
>> > >>Your
>> > >> vote
>> > >> >> counts!
>> > >> >>
>> > >> >> [ ] +1 Release the binary as Apache Camel 2.11.0
>> > >> >> [ ] -1 Veto the release (provide specific comments)
>> > >> >> Vote is open for at least 72 hours.
>> > >> >>
>> > >> >> Thanks in advance,
>> > >> >> Christian
>> > >> >>
>> > >> >> [1]
>> > >> >>
>> > >>
>> > >>
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20
>> > >>fixVersion%20%3D%20%222.11.0%22
>> > >> >> [2]
>> > >> >>
>> > >>
>> > >>
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211
>> > >>&version=12321695
>> > >> >>
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> Claus Ibsen
>> > >> -----------------
>> > >> Red Hat, Inc.
>> > >> FuseSource is now part of Red Hat
>> > >> Email: cibsen@redhat.com
>> > >> Web: http://fusesource.com
>> > >> Twitter: davsclaus
>> > >> Blog: http://davsclaus.com
>> > >> Author of Camel in Action: http://www.manning.com/ibsen
>> > >>
>> >
>> >
>> >
>>
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Raul Kripalani <ra...@evosent.com>.
Yes, in that case I agree too this is the most sensible option.
+1
Raúl.
On 14 Apr 2013 12:38, "Christian Müller" <ch...@gmail.com>
wrote:
> +1 for an option so the user can decide whether he want the stats or not.
>
> Sent from a mobile device
> Am 14.04.2013 13:30 schrieb "Babak Vahdat" <ba...@swissonline.ch>:
>
> >
> >
> > Am 14.04.13 13:09 schrieb "Raul Kripalani" unter <ra...@evosent.com>:
> >
> > >Hi Claus
> > >
> > >+1 to redo the release.
> > >
> > >These stats are really useful for profiling.
> > >
> > >I'd rather turn the counters into plain longs and make it clear to users
> > >(in the log statements and documentation) that the figures are merely
> > >indicative and not fully accurate.
> >
> > Hi
> >
> > I think more than accuracy and precision using plain long the main
> problem
> > would be to have really WIRED numbers, that's also NEGATIVE numbers even
> > if you would ONLY increment, mostly reproduciable on multi-core boxes
> > (verifying/testing this is trivial & straightforward).
> >
> > Just wonder if we could disable this per default but let the stats get
> > enabled somehow through a flag, property or the likes. Then ppl can
> decide
> > on their own what's more important to them: better performance versus
> > statistics.
> >
> > Babak
> >
> > >
> > >Regards,
> > >Raúl.
> > > On 14 Apr 2013 09:42, "Claus Ibsen" <cl...@gmail.com> wrote:
> > >
> > >> Hi
> > >>
> > >> All the examples with those WARN about thread pools on shutdown should
> > >> been fixed on trunk.
> > >>
> > >> I wonder if we should redo the release as I want to fix by removing
> > >> the overhead of these stats. Its IMHO better to have higher
> > >> performance. And there is no good way to do the counters without the
> > >> threads contention. We could use plain long for the counters, but then
> > >> they are not accurate as a ++ on a long value is not atomic.
> > >>
> > >> https://issues.apache.org/jira/browse/CAMEL-6264
> > >>
> > >>
> > >>
> > >> On Sat, Apr 13, 2013 at 7:25 PM, Christian Müller
> > >> <ch...@gmail.com> wrote:
> > >> > I tested the following examples:
> > >> >
> > >> > camel-example-cxf-blueprint:
> > >> > OK
> > >> >
> > >> > camel-example-cxf-osgi
> > >> > FAILED (see CAMEL-6257)
> > >> >
> > >> > camel-example-aggregate
> > >> > OK, but it logged some WARNings by stopping the service:
> > >> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
> > >> > Waited 10.002 seconds for ExecutorService:
> > >> >
> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
> > >>
> >
> >>[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%2
> > >>8enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> > >> > to terminate...
> > >> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
> > >> > Forcing shutdown of ExecutorService:
> > >> >
> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
> > >>
> >
> >>[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%2
> > >>8enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> > >> > due first await termination elapsed.
> > >> >
> > >> > camel-example-bam
> > >> > some ERRORs in the log
> > >> >
> > >> > camel-example-cafe
> > >> > OK
> > >> >
> > >> > camel-example-cdi
> > >> > OK
> > >> >
> > >> > camel-example-console
> > >> > OK, but it logged some WARNings by stopping the service:
> > >> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
> > >> > Waited 10.002 seconds for ExecutorService:
> > >> >
> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
> > >> [stream://in?promptMessage=Enter+something%3A+]
> > >> > to terminate...
> > >> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
> > >> > Cannot completely force shutdown of ExecutorService:
> > >> >
> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
> > >> [stream://in?promptMessage=Enter+something%3A+]
> > >> > due second await termination elapsed.
> > >> >
> > >> > camel-example-cxf
> > >> > OK
> > >> >
> > >> > camel-example-cxf-proxy
> > >> > OK, but the README needs an update because we use dynamic ports
> > >> (available
> > >> > port finder). DONE
> > >> >
> > >> > camel-example-docs
> > >> > Doesn't generated the images for the index.html file
> > >> >
> > >> > Still testing the other examples...
> > >> >
> > >> > Best,
> > >> > Christain
> > >> >
> > >> >
> > >> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> > >> > christian.mueller@gmail.com> wrote:
> > >> >
> > >> >> After 9 month of development, we have a new minor release candidate
> > >> >> apache-camel-2.11.0 ready.
> > >> >> It comes with 659 issues resolved: new features, improvements and
> bug
> > >> >> fixes [1]. You can find the release notes here [2].
> > >> >>
> > >> >> Please find the staging repo here:
> > >> >>
> > >>https://repository.apache.org/content/repositories/orgapachecamel-092/
> > >> >>
> > >> >> The tarballs are here
> > >> >>
> > >> >>
> > >>
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecamel-092/org
> > >>/apache/camel/apache-camel/2.11.0/
> > >> >>
> > >> >> Tag:
> > >> >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
> > >> >>
> > >> >> Please review, help out with testing and vote to approve this
> release
> > >> >> binary. Please mention what you tested to prevent duplicate work.
> > >>Your
> > >> vote
> > >> >> counts!
> > >> >>
> > >> >> [ ] +1 Release the binary as Apache Camel 2.11.0
> > >> >> [ ] -1 Veto the release (provide specific comments)
> > >> >> Vote is open for at least 72 hours.
> > >> >>
> > >> >> Thanks in advance,
> > >> >> Christian
> > >> >>
> > >> >> [1]
> > >> >>
> > >>
> > >>
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20
> > >>fixVersion%20%3D%20%222.11.0%22
> > >> >> [2]
> > >> >>
> > >>
> > >>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211
> > >>&version=12321695
> > >> >>
> > >>
> > >>
> > >>
> > >> --
> > >> Claus Ibsen
> > >> -----------------
> > >> Red Hat, Inc.
> > >> FuseSource is now part of Red Hat
> > >> Email: cibsen@redhat.com
> > >> Web: http://fusesource.com
> > >> Twitter: davsclaus
> > >> Blog: http://davsclaus.com
> > >> Author of Camel in Action: http://www.manning.com/ibsen
> > >>
> >
> >
> >
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Christian Müller <ch...@gmail.com>.
+1 for an option so the user can decide whether he want the stats or not.
Sent from a mobile device
Am 14.04.2013 13:30 schrieb "Babak Vahdat" <ba...@swissonline.ch>:
>
>
> Am 14.04.13 13:09 schrieb "Raul Kripalani" unter <ra...@evosent.com>:
>
> >Hi Claus
> >
> >+1 to redo the release.
> >
> >These stats are really useful for profiling.
> >
> >I'd rather turn the counters into plain longs and make it clear to users
> >(in the log statements and documentation) that the figures are merely
> >indicative and not fully accurate.
>
> Hi
>
> I think more than accuracy and precision using plain long the main problem
> would be to have really WIRED numbers, that's also NEGATIVE numbers even
> if you would ONLY increment, mostly reproduciable on multi-core boxes
> (verifying/testing this is trivial & straightforward).
>
> Just wonder if we could disable this per default but let the stats get
> enabled somehow through a flag, property or the likes. Then ppl can decide
> on their own what's more important to them: better performance versus
> statistics.
>
> Babak
>
> >
> >Regards,
> >Raúl.
> > On 14 Apr 2013 09:42, "Claus Ibsen" <cl...@gmail.com> wrote:
> >
> >> Hi
> >>
> >> All the examples with those WARN about thread pools on shutdown should
> >> been fixed on trunk.
> >>
> >> I wonder if we should redo the release as I want to fix by removing
> >> the overhead of these stats. Its IMHO better to have higher
> >> performance. And there is no good way to do the counters without the
> >> threads contention. We could use plain long for the counters, but then
> >> they are not accurate as a ++ on a long value is not atomic.
> >>
> >> https://issues.apache.org/jira/browse/CAMEL-6264
> >>
> >>
> >>
> >> On Sat, Apr 13, 2013 at 7:25 PM, Christian Müller
> >> <ch...@gmail.com> wrote:
> >> > I tested the following examples:
> >> >
> >> > camel-example-cxf-blueprint:
> >> > OK
> >> >
> >> > camel-example-cxf-osgi
> >> > FAILED (see CAMEL-6257)
> >> >
> >> > camel-example-aggregate
> >> > OK, but it logged some WARNings by stopping the service:
> >> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
> >> > Waited 10.002 seconds for ExecutorService:
> >> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
> >>
> >>[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%2
> >>8enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> >> > to terminate...
> >> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
> >> > Forcing shutdown of ExecutorService:
> >> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
> >>
> >>[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%2
> >>8enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> >> > due first await termination elapsed.
> >> >
> >> > camel-example-bam
> >> > some ERRORs in the log
> >> >
> >> > camel-example-cafe
> >> > OK
> >> >
> >> > camel-example-cdi
> >> > OK
> >> >
> >> > camel-example-console
> >> > OK, but it logged some WARNings by stopping the service:
> >> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
> >> > Waited 10.002 seconds for ExecutorService:
> >> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
> >> [stream://in?promptMessage=Enter+something%3A+]
> >> > to terminate...
> >> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
> >> > Cannot completely force shutdown of ExecutorService:
> >> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
> >> [stream://in?promptMessage=Enter+something%3A+]
> >> > due second await termination elapsed.
> >> >
> >> > camel-example-cxf
> >> > OK
> >> >
> >> > camel-example-cxf-proxy
> >> > OK, but the README needs an update because we use dynamic ports
> >> (available
> >> > port finder). DONE
> >> >
> >> > camel-example-docs
> >> > Doesn't generated the images for the index.html file
> >> >
> >> > Still testing the other examples...
> >> >
> >> > Best,
> >> > Christain
> >> >
> >> >
> >> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> >> > christian.mueller@gmail.com> wrote:
> >> >
> >> >> After 9 month of development, we have a new minor release candidate
> >> >> apache-camel-2.11.0 ready.
> >> >> It comes with 659 issues resolved: new features, improvements and bug
> >> >> fixes [1]. You can find the release notes here [2].
> >> >>
> >> >> Please find the staging repo here:
> >> >>
> >>https://repository.apache.org/content/repositories/orgapachecamel-092/
> >> >>
> >> >> The tarballs are here
> >> >>
> >> >>
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachecamel-092/org
> >>/apache/camel/apache-camel/2.11.0/
> >> >>
> >> >> Tag:
> >> >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
> >> >>
> >> >> Please review, help out with testing and vote to approve this release
> >> >> binary. Please mention what you tested to prevent duplicate work.
> >>Your
> >> vote
> >> >> counts!
> >> >>
> >> >> [ ] +1 Release the binary as Apache Camel 2.11.0
> >> >> [ ] -1 Veto the release (provide specific comments)
> >> >> Vote is open for at least 72 hours.
> >> >>
> >> >> Thanks in advance,
> >> >> Christian
> >> >>
> >> >> [1]
> >> >>
> >>
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20
> >>fixVersion%20%3D%20%222.11.0%22
> >> >> [2]
> >> >>
> >>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211
> >>&version=12321695
> >> >>
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> Red Hat, Inc.
> >> FuseSource is now part of Red Hat
> >> Email: cibsen@redhat.com
> >> Web: http://fusesource.com
> >> Twitter: davsclaus
> >> Blog: http://davsclaus.com
> >> Author of Camel in Action: http://www.manning.com/ibsen
> >>
>
>
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Babak Vahdat <ba...@swissonline.ch>.
Am 14.04.13 13:09 schrieb "Raul Kripalani" unter <ra...@evosent.com>:
>Hi Claus
>
>+1 to redo the release.
>
>These stats are really useful for profiling.
>
>I'd rather turn the counters into plain longs and make it clear to users
>(in the log statements and documentation) that the figures are merely
>indicative and not fully accurate.
Hi
I think more than accuracy and precision using plain long the main problem
would be to have really WIRED numbers, that's also NEGATIVE numbers even
if you would ONLY increment, mostly reproduciable on multi-core boxes
(verifying/testing this is trivial & straightforward).
Just wonder if we could disable this per default but let the stats get
enabled somehow through a flag, property or the likes. Then ppl can decide
on their own what's more important to them: better performance versus
statistics.
Babak
>
>Regards,
>Raúl.
> On 14 Apr 2013 09:42, "Claus Ibsen" <cl...@gmail.com> wrote:
>
>> Hi
>>
>> All the examples with those WARN about thread pools on shutdown should
>> been fixed on trunk.
>>
>> I wonder if we should redo the release as I want to fix by removing
>> the overhead of these stats. Its IMHO better to have higher
>> performance. And there is no good way to do the counters without the
>> threads contention. We could use plain long for the counters, but then
>> they are not accurate as a ++ on a long value is not atomic.
>>
>> https://issues.apache.org/jira/browse/CAMEL-6264
>>
>>
>>
>> On Sat, Apr 13, 2013 at 7:25 PM, Christian Müller
>> <ch...@gmail.com> wrote:
>> > I tested the following examples:
>> >
>> > camel-example-cxf-blueprint:
>> > OK
>> >
>> > camel-example-cxf-osgi
>> > FAILED (see CAMEL-6257)
>> >
>> > camel-example-aggregate
>> > OK, but it logged some WARNings by stopping the service:
>> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
>> > Waited 10.002 seconds for ExecutorService:
>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
>>
>>[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%2
>>8enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
>> > to terminate...
>> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
>> > Forcing shutdown of ExecutorService:
>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
>>
>>[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%2
>>8enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
>> > due first await termination elapsed.
>> >
>> > camel-example-bam
>> > some ERRORs in the log
>> >
>> > camel-example-cafe
>> > OK
>> >
>> > camel-example-cdi
>> > OK
>> >
>> > camel-example-console
>> > OK, but it logged some WARNings by stopping the service:
>> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
>> > Waited 10.002 seconds for ExecutorService:
>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
>> [stream://in?promptMessage=Enter+something%3A+]
>> > to terminate...
>> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
>> > Cannot completely force shutdown of ExecutorService:
>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
>> [stream://in?promptMessage=Enter+something%3A+]
>> > due second await termination elapsed.
>> >
>> > camel-example-cxf
>> > OK
>> >
>> > camel-example-cxf-proxy
>> > OK, but the README needs an update because we use dynamic ports
>> (available
>> > port finder). DONE
>> >
>> > camel-example-docs
>> > Doesn't generated the images for the index.html file
>> >
>> > Still testing the other examples...
>> >
>> > Best,
>> > Christain
>> >
>> >
>> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
>> > christian.mueller@gmail.com> wrote:
>> >
>> >> After 9 month of development, we have a new minor release candidate
>> >> apache-camel-2.11.0 ready.
>> >> It comes with 659 issues resolved: new features, improvements and bug
>> >> fixes [1]. You can find the release notes here [2].
>> >>
>> >> Please find the staging repo here:
>> >>
>>https://repository.apache.org/content/repositories/orgapachecamel-092/
>> >>
>> >> The tarballs are here
>> >>
>> >>
>>
>>https://repository.apache.org/content/repositories/orgapachecamel-092/org
>>/apache/camel/apache-camel/2.11.0/
>> >>
>> >> Tag:
>> >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>> >>
>> >> Please review, help out with testing and vote to approve this release
>> >> binary. Please mention what you tested to prevent duplicate work.
>>Your
>> vote
>> >> counts!
>> >>
>> >> [ ] +1 Release the binary as Apache Camel 2.11.0
>> >> [ ] -1 Veto the release (provide specific comments)
>> >> Vote is open for at least 72 hours.
>> >>
>> >> Thanks in advance,
>> >> Christian
>> >>
>> >> [1]
>> >>
>>
>>https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20
>>fixVersion%20%3D%20%222.11.0%22
>> >> [2]
>> >>
>>
>>https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211
>>&version=12321695
>> >>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Raul Kripalani <ra...@evosent.com>.
Hi Claus
+1 to redo the release.
These stats are really useful for profiling.
I'd rather turn the counters into plain longs and make it clear to users
(in the log statements and documentation) that the figures are merely
indicative and not fully accurate.
Regards,
Raúl.
On 14 Apr 2013 09:42, "Claus Ibsen" <cl...@gmail.com> wrote:
> Hi
>
> All the examples with those WARN about thread pools on shutdown should
> been fixed on trunk.
>
> I wonder if we should redo the release as I want to fix by removing
> the overhead of these stats. Its IMHO better to have higher
> performance. And there is no good way to do the counters without the
> threads contention. We could use plain long for the counters, but then
> they are not accurate as a ++ on a long value is not atomic.
>
> https://issues.apache.org/jira/browse/CAMEL-6264
>
>
>
> On Sat, Apr 13, 2013 at 7:25 PM, Christian Müller
> <ch...@gmail.com> wrote:
> > I tested the following examples:
> >
> > camel-example-cxf-blueprint:
> > OK
> >
> > camel-example-cxf-osgi
> > FAILED (see CAMEL-6257)
> >
> > camel-example-aggregate
> > OK, but it logged some WARNings by stopping the service:
> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
> > Waited 10.002 seconds for ExecutorService:
> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
> [stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> > to terminate...
> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
> > Forcing shutdown of ExecutorService:
> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
> [stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> > due first await termination elapsed.
> >
> > camel-example-bam
> > some ERRORs in the log
> >
> > camel-example-cafe
> > OK
> >
> > camel-example-cdi
> > OK
> >
> > camel-example-console
> > OK, but it logged some WARNings by stopping the service:
> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
> > Waited 10.002 seconds for ExecutorService:
> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
> [stream://in?promptMessage=Enter+something%3A+]
> > to terminate...
> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
> > Cannot completely force shutdown of ExecutorService:
> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
> [stream://in?promptMessage=Enter+something%3A+]
> > due second await termination elapsed.
> >
> > camel-example-cxf
> > OK
> >
> > camel-example-cxf-proxy
> > OK, but the README needs an update because we use dynamic ports
> (available
> > port finder). DONE
> >
> > camel-example-docs
> > Doesn't generated the images for the index.html file
> >
> > Still testing the other examples...
> >
> > Best,
> > Christain
> >
> >
> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> > christian.mueller@gmail.com> wrote:
> >
> >> After 9 month of development, we have a new minor release candidate
> >> apache-camel-2.11.0 ready.
> >> It comes with 659 issues resolved: new features, improvements and bug
> >> fixes [1]. You can find the release notes here [2].
> >>
> >> Please find the staging repo here:
> >> https://repository.apache.org/content/repositories/orgapachecamel-092/
> >>
> >> The tarballs are here
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
> >>
> >> Tag:
> >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
> >>
> >> Please review, help out with testing and vote to approve this release
> >> binary. Please mention what you tested to prevent duplicate work. Your
> vote
> >> counts!
> >>
> >> [ ] +1 Release the binary as Apache Camel 2.11.0
> >> [ ] -1 Veto the release (provide specific comments)
> >> Vote is open for at least 72 hours.
> >>
> >> Thanks in advance,
> >> Christian
> >>
> >> [1]
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> >> [2]
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
> >>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Christian Müller <ch...@gmail.com>.
I further tested the following examples:
camel-example-etl
FAILED. See CAMEL-6273
camel-example-guice-jms
OK
camel-example-jms-file
OK
camel-example-jmx
OK
camel-example-loadbalancing
OK
camel-example-loan-broker
OK
camel-example-management
OK
camel-example-pojo-messaging
OK
camel-example-reportincident
FAILED. See CAMEL-6274
camel-example-route-throttling
FAILED. See CAMEL-6275
camel-example-simplejiraboot
OK
camel-example-spring
OK
camel-example-spring-javaconfig
OK
camel-example-spring-jms
FAILED. See CAMEL-6276
Still testing the other examples...
Christian
On Sun, Apr 14, 2013 at 12:15 PM, Christian Müller <
christian.mueller@gmail.com> wrote:
> With the attached patch (no regression in Camel) I could successful
> upgrade the Camel in Action source code to Camel 2.11.0.
>
> Best,
> Christian
>
>
> On Sun, Apr 14, 2013 at 10:42 AM, Claus Ibsen <cl...@gmail.com>wrote:
>
>> Hi
>>
>> All the examples with those WARN about thread pools on shutdown should
>> been fixed on trunk.
>>
>> I wonder if we should redo the release as I want to fix by removing
>> the overhead of these stats. Its IMHO better to have higher
>> performance. And there is no good way to do the counters without the
>> threads contention. We could use plain long for the counters, but then
>> they are not accurate as a ++ on a long value is not atomic.
>>
>> https://issues.apache.org/jira/browse/CAMEL-6264
>>
>>
>>
>> On Sat, Apr 13, 2013 at 7:25 PM, Christian Müller
>> <ch...@gmail.com> wrote:
>> > I tested the following examples:
>> >
>> > camel-example-cxf-blueprint:
>> > OK
>> >
>> > camel-example-cxf-osgi
>> > FAILED (see CAMEL-6257)
>> >
>> > camel-example-aggregate
>> > OK, but it logged some WARNings by stopping the service:
>> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
>> > Waited 10.002 seconds for ExecutorService:
>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
>> [stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
>> > to terminate...
>> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
>> > Forcing shutdown of ExecutorService:
>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
>> [stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
>> > due first await termination elapsed.
>> >
>> > camel-example-bam
>> > some ERRORs in the log
>> >
>> > camel-example-cafe
>> > OK
>> >
>> > camel-example-cdi
>> > OK
>> >
>> > camel-example-console
>> > OK, but it logged some WARNings by stopping the service:
>> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
>> > Waited 10.002 seconds for ExecutorService:
>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
>> [stream://in?promptMessage=Enter+something%3A+]
>> > to terminate...
>> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
>> > Cannot completely force shutdown of ExecutorService:
>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
>> [stream://in?promptMessage=Enter+something%3A+]
>> > due second await termination elapsed.
>> >
>> > camel-example-cxf
>> > OK
>> >
>> > camel-example-cxf-proxy
>> > OK, but the README needs an update because we use dynamic ports
>> (available
>> > port finder). DONE
>> >
>> > camel-example-docs
>> > Doesn't generated the images for the index.html file
>> >
>> > Still testing the other examples...
>> >
>> > Best,
>> > Christain
>> >
>> >
>> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
>> > christian.mueller@gmail.com> wrote:
>> >
>> >> After 9 month of development, we have a new minor release candidate
>> >> apache-camel-2.11.0 ready.
>> >> It comes with 659 issues resolved: new features, improvements and bug
>> >> fixes [1]. You can find the release notes here [2].
>> >>
>> >> Please find the staging repo here:
>> >> https://repository.apache.org/content/repositories/orgapachecamel-092/
>> >>
>> >> The tarballs are here
>> >>
>> >>
>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>> >>
>> >> Tag:
>> >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>> >>
>> >> Please review, help out with testing and vote to approve this release
>> >> binary. Please mention what you tested to prevent duplicate work. Your
>> vote
>> >> counts!
>> >>
>> >> [ ] +1 Release the binary as Apache Camel 2.11.0
>> >> [ ] -1 Veto the release (provide specific comments)
>> >> Vote is open for at least 72 hours.
>> >>
>> >> Thanks in advance,
>> >> Christian
>> >>
>> >> [1]
>> >>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>> >> [2]
>> >>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>> >>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Christian Müller <ch...@gmail.com>.
With the attached patch (no regression in Camel) I could successful upgrade
the Camel in Action source code to Camel 2.11.0.
Best,
Christian
On Sun, Apr 14, 2013 at 10:42 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> All the examples with those WARN about thread pools on shutdown should
> been fixed on trunk.
>
> I wonder if we should redo the release as I want to fix by removing
> the overhead of these stats. Its IMHO better to have higher
> performance. And there is no good way to do the counters without the
> threads contention. We could use plain long for the counters, but then
> they are not accurate as a ++ on a long value is not atomic.
>
> https://issues.apache.org/jira/browse/CAMEL-6264
>
>
>
> On Sat, Apr 13, 2013 at 7:25 PM, Christian Müller
> <ch...@gmail.com> wrote:
> > I tested the following examples:
> >
> > camel-example-cxf-blueprint:
> > OK
> >
> > camel-example-cxf-osgi
> > FAILED (see CAMEL-6257)
> >
> > camel-example-aggregate
> > OK, but it logged some WARNings by stopping the service:
> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
> > Waited 10.002 seconds for ExecutorService:
> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
> [stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> > to terminate...
> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
> > Forcing shutdown of ExecutorService:
> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
> [stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> > due first await termination elapsed.
> >
> > camel-example-bam
> > some ERRORs in the log
> >
> > camel-example-cafe
> > OK
> >
> > camel-example-cdi
> > OK
> >
> > camel-example-console
> > OK, but it logged some WARNings by stopping the service:
> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
> > Waited 10.002 seconds for ExecutorService:
> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
> [stream://in?promptMessage=Enter+something%3A+]
> > to terminate...
> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
> > Cannot completely force shutdown of ExecutorService:
> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
> [stream://in?promptMessage=Enter+something%3A+]
> > due second await termination elapsed.
> >
> > camel-example-cxf
> > OK
> >
> > camel-example-cxf-proxy
> > OK, but the README needs an update because we use dynamic ports
> (available
> > port finder). DONE
> >
> > camel-example-docs
> > Doesn't generated the images for the index.html file
> >
> > Still testing the other examples...
> >
> > Best,
> > Christain
> >
> >
> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> > christian.mueller@gmail.com> wrote:
> >
> >> After 9 month of development, we have a new minor release candidate
> >> apache-camel-2.11.0 ready.
> >> It comes with 659 issues resolved: new features, improvements and bug
> >> fixes [1]. You can find the release notes here [2].
> >>
> >> Please find the staging repo here:
> >> https://repository.apache.org/content/repositories/orgapachecamel-092/
> >>
> >> The tarballs are here
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
> >>
> >> Tag:
> >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
> >>
> >> Please review, help out with testing and vote to approve this release
> >> binary. Please mention what you tested to prevent duplicate work. Your
> vote
> >> counts!
> >>
> >> [ ] +1 Release the binary as Apache Camel 2.11.0
> >> [ ] -1 Veto the release (provide specific comments)
> >> Vote is open for at least 72 hours.
> >>
> >> Thanks in advance,
> >> Christian
> >>
> >> [1]
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> >> [2]
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
> >>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Christian Müller <ch...@gmail.com>.
I tested the Camel servlet examples with the following results:
camel-example-cxf-tomcat
FAILED. See CAMEL-6281
camel-example-servlet-tomcat
OK
camel-example-servlet-tomcat-no-spring
OK
camel-example-activemq-tomcat
OK
Best,
Christian
On Sun, Apr 14, 2013 at 5:07 PM, Christian Müller <
christian.mueller@gmail.com> wrote:
> I test test following examles:
>
> camel-example-spring-security
> FAILED. See CAMEL-6277
>
> camel-example-spring-ws
> OK
>
> camel-example-spring-xquery
> OK
>
> camel-example-sql
> OK
>
> camel-example-ssh
> OK
>
> camel-example-tracer
> OK. It logs the WARNings Claus already fixed.
>
> camel-example-twitter-websocket
> OK
>
> camel-example-reportincident-wssecurity
> FAILED. See CAMEL-6278
>
> camel-example-osgi
> OK if your execute "mvn camel:run" but FAILED if you deploy it into Karaf.
> See CAMEL-6280
>
> camel-example-osgi-rmi
> FAILED. See CAMEL-6279
>
> Will now test the servlet examples...
>
> Best,
> Christian
>
>
> On Sun, Apr 14, 2013 at 3:40 PM, Christian Müller <
> christian.mueller@gmail.com> wrote:
>
>> I'm still testing the outstanding examples and some of my projects. At
>> present, I would vote +1 for this release because the issues we found are
>> not critical in my opinion. I favor to have a Camel 2.11.1 release which
>> will fix the issues in 3 - 6 weeks.
>>
>> Best,
>> Christian
>>
>>
>> On Sun, Apr 14, 2013 at 10:42 AM, Claus Ibsen <cl...@gmail.com>wrote:
>>
>>> Hi
>>>
>>> All the examples with those WARN about thread pools on shutdown should
>>> been fixed on trunk.
>>>
>>> I wonder if we should redo the release as I want to fix by removing
>>> the overhead of these stats. Its IMHO better to have higher
>>> performance. And there is no good way to do the counters without the
>>> threads contention. We could use plain long for the counters, but then
>>> they are not accurate as a ++ on a long value is not atomic.
>>>
>>> https://issues.apache.org/jira/browse/CAMEL-6264
>>>
>>>
>>>
>>> On Sat, Apr 13, 2013 at 7:25 PM, Christian Müller
>>> <ch...@gmail.com> wrote:
>>> > I tested the following examples:
>>> >
>>> > camel-example-cxf-blueprint:
>>> > OK
>>> >
>>> > camel-example-cxf-osgi
>>> > FAILED (see CAMEL-6257)
>>> >
>>> > camel-example-aggregate
>>> > OK, but it logged some WARNings by stopping the service:
>>> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
>>> > Waited 10.002 seconds for ExecutorService:
>>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
>>> [stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
>>> > to terminate...
>>> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
>>> > Forcing shutdown of ExecutorService:
>>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
>>> [stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
>>> > due first await termination elapsed.
>>> >
>>> > camel-example-bam
>>> > some ERRORs in the log
>>> >
>>> > camel-example-cafe
>>> > OK
>>> >
>>> > camel-example-cdi
>>> > OK
>>> >
>>> > camel-example-console
>>> > OK, but it logged some WARNings by stopping the service:
>>> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
>>> > Waited 10.002 seconds for ExecutorService:
>>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
>>> [stream://in?promptMessage=Enter+something%3A+]
>>> > to terminate...
>>> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
>>> > Cannot completely force shutdown of ExecutorService:
>>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
>>> [stream://in?promptMessage=Enter+something%3A+]
>>> > due second await termination elapsed.
>>> >
>>> > camel-example-cxf
>>> > OK
>>> >
>>> > camel-example-cxf-proxy
>>> > OK, but the README needs an update because we use dynamic ports
>>> (available
>>> > port finder). DONE
>>> >
>>> > camel-example-docs
>>> > Doesn't generated the images for the index.html file
>>> >
>>> > Still testing the other examples...
>>> >
>>> > Best,
>>> > Christain
>>> >
>>> >
>>> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
>>> > christian.mueller@gmail.com> wrote:
>>> >
>>> >> After 9 month of development, we have a new minor release candidate
>>> >> apache-camel-2.11.0 ready.
>>> >> It comes with 659 issues resolved: new features, improvements and bug
>>> >> fixes [1]. You can find the release notes here [2].
>>> >>
>>> >> Please find the staging repo here:
>>> >>
>>> https://repository.apache.org/content/repositories/orgapachecamel-092/
>>> >>
>>> >> The tarballs are here
>>> >>
>>> >>
>>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>>> >>
>>> >> Tag:
>>> >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>>> >>
>>> >> Please review, help out with testing and vote to approve this release
>>> >> binary. Please mention what you tested to prevent duplicate work.
>>> Your vote
>>> >> counts!
>>> >>
>>> >> [ ] +1 Release the binary as Apache Camel 2.11.0
>>> >> [ ] -1 Veto the release (provide specific comments)
>>> >> Vote is open for at least 72 hours.
>>> >>
>>> >> Thanks in advance,
>>> >> Christian
>>> >>
>>> >> [1]
>>> >>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>>> >> [2]
>>> >>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>>> >>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> Red Hat, Inc.
>>> FuseSource is now part of Red Hat
>>> Email: cibsen@redhat.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>
>>
>>
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Christian Müller <ch...@gmail.com>.
I test test following examles:
camel-example-spring-security
FAILED. See CAMEL-6277
camel-example-spring-ws
OK
camel-example-spring-xquery
OK
camel-example-sql
OK
camel-example-ssh
OK
camel-example-tracer
OK. It logs the WARNings Claus already fixed.
camel-example-twitter-websocket
OK
camel-example-reportincident-wssecurity
FAILED. See CAMEL-6278
camel-example-osgi
OK if your execute "mvn camel:run" but FAILED if you deploy it into Karaf.
See CAMEL-6280
camel-example-osgi-rmi
FAILED. See CAMEL-6279
Will now test the servlet examples...
Best,
Christian
On Sun, Apr 14, 2013 at 3:40 PM, Christian Müller <
christian.mueller@gmail.com> wrote:
> I'm still testing the outstanding examples and some of my projects. At
> present, I would vote +1 for this release because the issues we found are
> not critical in my opinion. I favor to have a Camel 2.11.1 release which
> will fix the issues in 3 - 6 weeks.
>
> Best,
> Christian
>
>
> On Sun, Apr 14, 2013 at 10:42 AM, Claus Ibsen <cl...@gmail.com>wrote:
>
>> Hi
>>
>> All the examples with those WARN about thread pools on shutdown should
>> been fixed on trunk.
>>
>> I wonder if we should redo the release as I want to fix by removing
>> the overhead of these stats. Its IMHO better to have higher
>> performance. And there is no good way to do the counters without the
>> threads contention. We could use plain long for the counters, but then
>> they are not accurate as a ++ on a long value is not atomic.
>>
>> https://issues.apache.org/jira/browse/CAMEL-6264
>>
>>
>>
>> On Sat, Apr 13, 2013 at 7:25 PM, Christian Müller
>> <ch...@gmail.com> wrote:
>> > I tested the following examples:
>> >
>> > camel-example-cxf-blueprint:
>> > OK
>> >
>> > camel-example-cxf-osgi
>> > FAILED (see CAMEL-6257)
>> >
>> > camel-example-aggregate
>> > OK, but it logged some WARNings by stopping the service:
>> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
>> > Waited 10.002 seconds for ExecutorService:
>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
>> [stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
>> > to terminate...
>> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
>> > Forcing shutdown of ExecutorService:
>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
>> [stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
>> > due first await termination elapsed.
>> >
>> > camel-example-bam
>> > some ERRORs in the log
>> >
>> > camel-example-cafe
>> > OK
>> >
>> > camel-example-cdi
>> > OK
>> >
>> > camel-example-console
>> > OK, but it logged some WARNings by stopping the service:
>> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
>> > Waited 10.002 seconds for ExecutorService:
>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
>> [stream://in?promptMessage=Enter+something%3A+]
>> > to terminate...
>> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
>> > Cannot completely force shutdown of ExecutorService:
>> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
>> [stream://in?promptMessage=Enter+something%3A+]
>> > due second await termination elapsed.
>> >
>> > camel-example-cxf
>> > OK
>> >
>> > camel-example-cxf-proxy
>> > OK, but the README needs an update because we use dynamic ports
>> (available
>> > port finder). DONE
>> >
>> > camel-example-docs
>> > Doesn't generated the images for the index.html file
>> >
>> > Still testing the other examples...
>> >
>> > Best,
>> > Christain
>> >
>> >
>> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
>> > christian.mueller@gmail.com> wrote:
>> >
>> >> After 9 month of development, we have a new minor release candidate
>> >> apache-camel-2.11.0 ready.
>> >> It comes with 659 issues resolved: new features, improvements and bug
>> >> fixes [1]. You can find the release notes here [2].
>> >>
>> >> Please find the staging repo here:
>> >> https://repository.apache.org/content/repositories/orgapachecamel-092/
>> >>
>> >> The tarballs are here
>> >>
>> >>
>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>> >>
>> >> Tag:
>> >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>> >>
>> >> Please review, help out with testing and vote to approve this release
>> >> binary. Please mention what you tested to prevent duplicate work. Your
>> vote
>> >> counts!
>> >>
>> >> [ ] +1 Release the binary as Apache Camel 2.11.0
>> >> [ ] -1 Veto the release (provide specific comments)
>> >> Vote is open for at least 72 hours.
>> >>
>> >> Thanks in advance,
>> >> Christian
>> >>
>> >> [1]
>> >>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>> >> [2]
>> >>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>> >>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Christian Müller <ch...@gmail.com>.
I'm still testing the outstanding examples and some of my projects. At
present, I would vote +1 for this release because the issues we found are
not critical in my opinion. I favor to have a Camel 2.11.1 release which
will fix the issues in 3 - 6 weeks.
Best,
Christian
On Sun, Apr 14, 2013 at 10:42 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> All the examples with those WARN about thread pools on shutdown should
> been fixed on trunk.
>
> I wonder if we should redo the release as I want to fix by removing
> the overhead of these stats. Its IMHO better to have higher
> performance. And there is no good way to do the counters without the
> threads contention. We could use plain long for the counters, but then
> they are not accurate as a ++ on a long value is not atomic.
>
> https://issues.apache.org/jira/browse/CAMEL-6264
>
>
>
> On Sat, Apr 13, 2013 at 7:25 PM, Christian Müller
> <ch...@gmail.com> wrote:
> > I tested the following examples:
> >
> > camel-example-cxf-blueprint:
> > OK
> >
> > camel-example-cxf-osgi
> > FAILED (see CAMEL-6257)
> >
> > camel-example-aggregate
> > OK, but it logged some WARNings by stopping the service:
> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
> > Waited 10.002 seconds for ExecutorService:
> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
> [stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> > to terminate...
> > [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
> > Forcing shutdown of ExecutorService:
> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66
> [stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> > due first await termination elapsed.
> >
> > camel-example-bam
> > some ERRORs in the log
> >
> > camel-example-cafe
> > OK
> >
> > camel-example-cdi
> > OK
> >
> > camel-example-console
> > OK, but it logged some WARNings by stopping the service:
> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
> > Waited 10.002 seconds for ExecutorService:
> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
> [stream://in?promptMessage=Enter+something%3A+]
> > to terminate...
> > [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
> > Cannot completely force shutdown of ExecutorService:
> > org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52
> [stream://in?promptMessage=Enter+something%3A+]
> > due second await termination elapsed.
> >
> > camel-example-cxf
> > OK
> >
> > camel-example-cxf-proxy
> > OK, but the README needs an update because we use dynamic ports
> (available
> > port finder). DONE
> >
> > camel-example-docs
> > Doesn't generated the images for the index.html file
> >
> > Still testing the other examples...
> >
> > Best,
> > Christain
> >
> >
> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> > christian.mueller@gmail.com> wrote:
> >
> >> After 9 month of development, we have a new minor release candidate
> >> apache-camel-2.11.0 ready.
> >> It comes with 659 issues resolved: new features, improvements and bug
> >> fixes [1]. You can find the release notes here [2].
> >>
> >> Please find the staging repo here:
> >> https://repository.apache.org/content/repositories/orgapachecamel-092/
> >>
> >> The tarballs are here
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
> >>
> >> Tag:
> >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
> >>
> >> Please review, help out with testing and vote to approve this release
> >> binary. Please mention what you tested to prevent duplicate work. Your
> vote
> >> counts!
> >>
> >> [ ] +1 Release the binary as Apache Camel 2.11.0
> >> [ ] -1 Veto the release (provide specific comments)
> >> Vote is open for at least 72 hours.
> >>
> >> Thanks in advance,
> >> Christian
> >>
> >> [1]
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> >> [2]
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
> >>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
All the examples with those WARN about thread pools on shutdown should
been fixed on trunk.
I wonder if we should redo the release as I want to fix by removing
the overhead of these stats. Its IMHO better to have higher
performance. And there is no good way to do the counters without the
threads contention. We could use plain long for the counters, but then
they are not accurate as a ++ on a long value is not atomic.
https://issues.apache.org/jira/browse/CAMEL-6264
On Sat, Apr 13, 2013 at 7:25 PM, Christian Müller
<ch...@gmail.com> wrote:
> I tested the following examples:
>
> camel-example-cxf-blueprint:
> OK
>
> camel-example-cxf-osgi
> FAILED (see CAMEL-6257)
>
> camel-example-aggregate
> OK, but it logged some WARNings by stopping the service:
> [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
> Waited 10.002 seconds for ExecutorService:
> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> to terminate...
> [amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
> Forcing shutdown of ExecutorService:
> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
> due first await termination elapsed.
>
> camel-example-bam
> some ERRORs in the log
>
> camel-example-cafe
> OK
>
> camel-example-cdi
> OK
>
> camel-example-console
> OK, but it logged some WARNings by stopping the service:
> [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
> Waited 10.002 seconds for ExecutorService:
> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52[stream://in?promptMessage=Enter+something%3A+]
> to terminate...
> [el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
> Cannot completely force shutdown of ExecutorService:
> org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52[stream://in?promptMessage=Enter+something%3A+]
> due second await termination elapsed.
>
> camel-example-cxf
> OK
>
> camel-example-cxf-proxy
> OK, but the README needs an update because we use dynamic ports (available
> port finder). DONE
>
> camel-example-docs
> Doesn't generated the images for the index.html file
>
> Still testing the other examples...
>
> Best,
> Christain
>
>
> On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> christian.mueller@gmail.com> wrote:
>
>> After 9 month of development, we have a new minor release candidate
>> apache-camel-2.11.0 ready.
>> It comes with 659 issues resolved: new features, improvements and bug
>> fixes [1]. You can find the release notes here [2].
>>
>> Please find the staging repo here:
>> https://repository.apache.org/content/repositories/orgapachecamel-092/
>>
>> The tarballs are here
>>
>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>>
>> Tag:
>> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>>
>> Please review, help out with testing and vote to approve this release
>> binary. Please mention what you tested to prevent duplicate work. Your vote
>> counts!
>>
>> [ ] +1 Release the binary as Apache Camel 2.11.0
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Thanks in advance,
>> Christian
>>
>> [1]
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>> [2]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>>
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Christian Müller <ch...@gmail.com>.
I tested the following examples:
camel-example-cxf-blueprint:
OK
camel-example-cxf-osgi
FAILED (see CAMEL-6257)
camel-example-aggregate
OK, but it logged some WARNings by stopping the service:
[amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager INFO
Waited 10.002 seconds for ExecutorService:
org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
to terminate...
[amel) thread #3 - ShutdownTask] DefaultExecutorServiceManager WARN
Forcing shutdown of ExecutorService:
org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@2f971f66[stream://in?promptDelay=1000&promptMessage=Enter+a+number+to+be+added+%28enter+STOP+to+end%2C+and+Ctrl-C+to+shutdown+Camel%29%3A+]
due first await termination elapsed.
camel-example-bam
some ERRORs in the log
camel-example-cafe
OK
camel-example-cdi
OK
camel-example-console
OK, but it logged some WARNings by stopping the service:
[el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
Waited 10.002 seconds for ExecutorService:
org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52[stream://in?promptMessage=Enter+something%3A+]
to terminate...
[el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager WARN
Cannot completely force shutdown of ExecutorService:
org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@1a3a2a52[stream://in?promptMessage=Enter+something%3A+]
due second await termination elapsed.
camel-example-cxf
OK
camel-example-cxf-proxy
OK, but the README needs an update because we use dynamic ports (available
port finder). DONE
camel-example-docs
Doesn't generated the images for the index.html file
Still testing the other examples...
Best,
Christain
On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
christian.mueller@gmail.com> wrote:
> After 9 month of development, we have a new minor release candidate
> apache-camel-2.11.0 ready.
> It comes with 659 issues resolved: new features, improvements and bug
> fixes [1]. You can find the release notes here [2].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-092/
>
> The tarballs are here
>
> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>
> Please review, help out with testing and vote to approve this release
> binary. Please mention what you tested to prevent duplicate work. Your vote
> counts!
>
> [ ] +1 Release the binary as Apache Camel 2.11.0
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks in advance,
> Christian
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> [2]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by akarpe <ak...@yahoo.com>.
+1
On Apr 14, 2013, at 2:25 PM, Christian Müller <ch...@gmail.com> wrote:
> +1
>
> I found a few issues during testing this release, but none of them are
> critical in my opinion (most of them are related to our examples). I prefer
> to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks after
> we fixed the issues.
>
> Because we got only two votes until now, I extend the voting period for
> additional 48 hours.
>
> Best,
> Christian
>
>
> On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> christian.mueller@gmail.com> wrote:
>
>> After 9 month of development, we have a new minor release candidate
>> apache-camel-2.11.0 ready.
>> It comes with 659 issues resolved: new features, improvements and bug
>> fixes [1]. You can find the release notes here [2].
>>
>> Please find the staging repo here:
>> https://repository.apache.org/content/repositories/orgapachecamel-092/
>>
>> The tarballs are here
>>
>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>>
>> Tag:
>> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>>
>> Please review, help out with testing and vote to approve this release
>> binary. Please mention what you tested to prevent duplicate work. Your vote
>> counts!
>>
>> [ ] +1 Release the binary as Apache Camel 2.11.0
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Thanks in advance,
>> Christian
>>
>> [1]
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>> [2]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Christian Müller <ch...@gmail.com>.
I will test the examples you fixed already from trunk and comment on the
JIRA.
Best,
Christian
On Mon, Apr 15, 2013 at 11:58 AM, Willem jiang <wi...@gmail.com>wrote:
>
> I fixed some of the example issues today, please double check them if you
> have time.
> As we don't create the camel 2.11.x branch, it could be much easy if we
> recut the Camel 2.11.0 from the trunk.
>
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Web: http://www.fusesource.com | http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
> (English)
> http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
>
>
> On Monday, April 15, 2013 at 3:18 PM, Claus Ibsen wrote:
>
> > Hi
> >
> > I actually think this RC has too many out of the box issues for new
> > users to Camel.
> > For example all the example issues.
> >
> > Also we have that performance degrade related to the linked ticket from
> > https://issues.apache.org/jira/browse/CAMEL-6282
> >
> > And about 10+ fixes already since the RC.
> >
> > I really do think we should redo the release when we have all the
> > examples fixed.
> > As well that CAMEL-6282.
> >
> > And also in light that Camel 2.11 is a big new release of Camel. And
> > will maybe hit the news etc, as its almost 10 months since Camel 2.10
> > was released.
> > And I prefer Camel this release to be at its best.
> >
> >
> >
> >
> > On Sun, Apr 14, 2013 at 9:25 PM, Christian Müller
> > <christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
> wrote:
> > > +1
> > >
> > > I found a few issues during testing this release, but none of them are
> > > critical in my opinion (most of them are related to our examples). I
> prefer
> > > to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks
> after
> > > we fixed the issues.
> > >
> > > Because we got only two votes until now, I extend the voting period for
> > > additional 48 hours.
> > >
> > > Best,
> > > Christian
> > >
> > >
> > > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> > > christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
> wrote:
> > >
> > > > After 9 month of development, we have a new minor release candidate
> > > > apache-camel-2.11.0 ready.
> > > > It comes with 659 issues resolved: new features, improvements and bug
> > > > fixes [1]. You can find the release notes here [2].
> > > >
> > > > Please find the staging repo here:
> > > >
> https://repository.apache.org/content/repositories/orgapachecamel-092/
> > > >
> > > > The tarballs are here
> > > >
> > > >
> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
> > > >
> > > > Tag:
> > > > http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
> > > >
> > > > Please review, help out with testing and vote to approve this release
> > > > binary. Please mention what you tested to prevent duplicate work.
> Your vote
> > > > counts!
> > > >
> > > > [ ] +1 Release the binary as Apache Camel 2.11.0
> > > > [ ] -1 Veto the release (provide specific comments)
> > > > Vote is open for at least 72 hours.
> > > >
> > > > Thanks in advance,
> > > > Christian
> > > >
> > > > [1]
> > > >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> > > > [2]
> > > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
> > >
> >
> >
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > Red Hat, Inc.
> > FuseSource is now part of Red Hat
> > Email: cibsen@redhat.com (mailto:cibsen@redhat.com)
> > Web: http://fusesource.com
> > Twitter: davsclaus
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I tested all the maven camel archetypes on trunk. They all worked, but
there was a few things to polish. Such as read me files, and a few had
a maven warning about a missing plugin version. So all that has been
polished and committed to trunk.
On Mon, Apr 15, 2013 at 9:27 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> I will give the archetypes a test run tomorrow morning as well the
> ones we have on trunk.
>
>
>
> On Mon, Apr 15, 2013 at 7:51 PM, Christian Müller
> <ch...@gmail.com> wrote:
>> I didn't test the archetypes (and don't have the time to do it in the next
>> two days). It would be great if somebody could do this before we may re-cut
>> this release.
>> I do not have any problems to re-cut the release if it's in the right shape
>> in a few days (this week). I think this will be the case. I have free
>> cycles on Wednesday and may be on the late Thursday.
>>
>> Other thoughts?
>>
>> Best,
>> Christian
>>
>>
>> On Mon, Apr 15, 2013 at 3:17 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>
>>> Hi
>>>
>>> Did anyone test the maven archetypes to create new Camel projects?
>>> They are really valuable for new users to Camel and existing for
>>> creating new projects.
>>>
>>> IMHO we should give them a test spin to see if they create projects
>>> that works out of the box.
>>>
>>>
>>> On Mon, Apr 15, 2013 at 11:58 AM, Willem jiang <wi...@gmail.com>
>>> wrote:
>>> >
>>> > I fixed some of the example issues today, please double check them if
>>> you have time.
>>> > As we don't create the camel 2.11.x branch, it could be much easy if we
>>> recut the Camel 2.11.0 from the trunk.
>>> >
>>> >
>>> > --
>>> > Willem Jiang
>>> >
>>> > Red Hat, Inc.
>>> > FuseSource is now part of Red Hat
>>> > Web: http://www.fusesource.com | http://www.redhat.com
>>> > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
>>> (English)
>>> > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
>>> > Twitter: willemjiang
>>> > Weibo: 姜宁willem
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Monday, April 15, 2013 at 3:18 PM, Claus Ibsen wrote:
>>> >
>>> >> Hi
>>> >>
>>> >> I actually think this RC has too many out of the box issues for new
>>> >> users to Camel.
>>> >> For example all the example issues.
>>> >>
>>> >> Also we have that performance degrade related to the linked ticket from
>>> >> https://issues.apache.org/jira/browse/CAMEL-6282
>>> >>
>>> >> And about 10+ fixes already since the RC.
>>> >>
>>> >> I really do think we should redo the release when we have all the
>>> >> examples fixed.
>>> >> As well that CAMEL-6282.
>>> >>
>>> >> And also in light that Camel 2.11 is a big new release of Camel. And
>>> >> will maybe hit the news etc, as its almost 10 months since Camel 2.10
>>> >> was released.
>>> >> And I prefer Camel this release to be at its best.
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> On Sun, Apr 14, 2013 at 9:25 PM, Christian Müller
>>> >> <christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
>>> wrote:
>>> >> > +1
>>> >> >
>>> >> > I found a few issues during testing this release, but none of them are
>>> >> > critical in my opinion (most of them are related to our examples). I
>>> prefer
>>> >> > to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks
>>> after
>>> >> > we fixed the issues.
>>> >> >
>>> >> > Because we got only two votes until now, I extend the voting period
>>> for
>>> >> > additional 48 hours.
>>> >> >
>>> >> > Best,
>>> >> > Christian
>>> >> >
>>> >> >
>>> >> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
>>> >> > christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
>>> wrote:
>>> >> >
>>> >> > > After 9 month of development, we have a new minor release candidate
>>> >> > > apache-camel-2.11.0 ready.
>>> >> > > It comes with 659 issues resolved: new features, improvements and
>>> bug
>>> >> > > fixes [1]. You can find the release notes here [2].
>>> >> > >
>>> >> > > Please find the staging repo here:
>>> >> > >
>>> https://repository.apache.org/content/repositories/orgapachecamel-092/
>>> >> > >
>>> >> > > The tarballs are here
>>> >> > >
>>> >> > >
>>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>>> >> > >
>>> >> > > Tag:
>>> >> > > http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>>> >> > >
>>> >> > > Please review, help out with testing and vote to approve this
>>> release
>>> >> > > binary. Please mention what you tested to prevent duplicate work.
>>> Your vote
>>> >> > > counts!
>>> >> > >
>>> >> > > [ ] +1 Release the binary as Apache Camel 2.11.0
>>> >> > > [ ] -1 Veto the release (provide specific comments)
>>> >> > > Vote is open for at least 72 hours.
>>> >> > >
>>> >> > > Thanks in advance,
>>> >> > > Christian
>>> >> > >
>>> >> > > [1]
>>> >> > >
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>>> >> > > [2]
>>> >> > >
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Claus Ibsen
>>> >> -----------------
>>> >> Red Hat, Inc.
>>> >> FuseSource is now part of Red Hat
>>> >> Email: cibsen@redhat.com (mailto:cibsen@redhat.com)
>>> >> Web: http://fusesource.com
>>> >> Twitter: davsclaus
>>> >> Blog: http://davsclaus.com
>>> >> Author of Camel in Action: http://www.manning.com/ibsen
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> Red Hat, Inc.
>>> FuseSource is now part of Red Hat
>>> Email: cibsen@redhat.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I will give the archetypes a test run tomorrow morning as well the
ones we have on trunk.
On Mon, Apr 15, 2013 at 7:51 PM, Christian Müller
<ch...@gmail.com> wrote:
> I didn't test the archetypes (and don't have the time to do it in the next
> two days). It would be great if somebody could do this before we may re-cut
> this release.
> I do not have any problems to re-cut the release if it's in the right shape
> in a few days (this week). I think this will be the case. I have free
> cycles on Wednesday and may be on the late Thursday.
>
> Other thoughts?
>
> Best,
> Christian
>
>
> On Mon, Apr 15, 2013 at 3:17 PM, Claus Ibsen <cl...@gmail.com> wrote:
>
>> Hi
>>
>> Did anyone test the maven archetypes to create new Camel projects?
>> They are really valuable for new users to Camel and existing for
>> creating new projects.
>>
>> IMHO we should give them a test spin to see if they create projects
>> that works out of the box.
>>
>>
>> On Mon, Apr 15, 2013 at 11:58 AM, Willem jiang <wi...@gmail.com>
>> wrote:
>> >
>> > I fixed some of the example issues today, please double check them if
>> you have time.
>> > As we don't create the camel 2.11.x branch, it could be much easy if we
>> recut the Camel 2.11.0 from the trunk.
>> >
>> >
>> > --
>> > Willem Jiang
>> >
>> > Red Hat, Inc.
>> > FuseSource is now part of Red Hat
>> > Web: http://www.fusesource.com | http://www.redhat.com
>> > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
>> (English)
>> > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
>> > Twitter: willemjiang
>> > Weibo: 姜宁willem
>> >
>> >
>> >
>> >
>> >
>> > On Monday, April 15, 2013 at 3:18 PM, Claus Ibsen wrote:
>> >
>> >> Hi
>> >>
>> >> I actually think this RC has too many out of the box issues for new
>> >> users to Camel.
>> >> For example all the example issues.
>> >>
>> >> Also we have that performance degrade related to the linked ticket from
>> >> https://issues.apache.org/jira/browse/CAMEL-6282
>> >>
>> >> And about 10+ fixes already since the RC.
>> >>
>> >> I really do think we should redo the release when we have all the
>> >> examples fixed.
>> >> As well that CAMEL-6282.
>> >>
>> >> And also in light that Camel 2.11 is a big new release of Camel. And
>> >> will maybe hit the news etc, as its almost 10 months since Camel 2.10
>> >> was released.
>> >> And I prefer Camel this release to be at its best.
>> >>
>> >>
>> >>
>> >>
>> >> On Sun, Apr 14, 2013 at 9:25 PM, Christian Müller
>> >> <christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
>> wrote:
>> >> > +1
>> >> >
>> >> > I found a few issues during testing this release, but none of them are
>> >> > critical in my opinion (most of them are related to our examples). I
>> prefer
>> >> > to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks
>> after
>> >> > we fixed the issues.
>> >> >
>> >> > Because we got only two votes until now, I extend the voting period
>> for
>> >> > additional 48 hours.
>> >> >
>> >> > Best,
>> >> > Christian
>> >> >
>> >> >
>> >> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
>> >> > christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
>> wrote:
>> >> >
>> >> > > After 9 month of development, we have a new minor release candidate
>> >> > > apache-camel-2.11.0 ready.
>> >> > > It comes with 659 issues resolved: new features, improvements and
>> bug
>> >> > > fixes [1]. You can find the release notes here [2].
>> >> > >
>> >> > > Please find the staging repo here:
>> >> > >
>> https://repository.apache.org/content/repositories/orgapachecamel-092/
>> >> > >
>> >> > > The tarballs are here
>> >> > >
>> >> > >
>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>> >> > >
>> >> > > Tag:
>> >> > > http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>> >> > >
>> >> > > Please review, help out with testing and vote to approve this
>> release
>> >> > > binary. Please mention what you tested to prevent duplicate work.
>> Your vote
>> >> > > counts!
>> >> > >
>> >> > > [ ] +1 Release the binary as Apache Camel 2.11.0
>> >> > > [ ] -1 Veto the release (provide specific comments)
>> >> > > Vote is open for at least 72 hours.
>> >> > >
>> >> > > Thanks in advance,
>> >> > > Christian
>> >> > >
>> >> > > [1]
>> >> > >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>> >> > > [2]
>> >> > >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>> >> >
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Claus Ibsen
>> >> -----------------
>> >> Red Hat, Inc.
>> >> FuseSource is now part of Red Hat
>> >> Email: cibsen@redhat.com (mailto:cibsen@redhat.com)
>> >> Web: http://fusesource.com
>> >> Twitter: davsclaus
>> >> Blog: http://davsclaus.com
>> >> Author of Camel in Action: http://www.manning.com/ibsen
>> >
>> >
>> >
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Hmm seems working testing with a fresh Karaf 2.3.1
karaf@root> camel:context-list
Name Status Uptime
[ blueprintContext ] [ Started ] [ 2 minutes ]
Also I installed a Camel spring-dm app, and it was also listed.
On Tue, Apr 16, 2013 at 4:40 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> The camel karaf commands may have a problem. Just noticed
> camel:context-list didn't return any data, when I had a Camel app in
> karaf.
>
>
>
> On Tue, Apr 16, 2013 at 3:14 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> Yeah it would be lovely to re-cut the release tomorrow.
>>
>> I will give the examples on trunk a test spin as well, to see if they
>> are working all.
>>
>>
>>
>> On Mon, Apr 15, 2013 at 7:51 PM, Christian Müller
>> <ch...@gmail.com> wrote:
>>> I didn't test the archetypes (and don't have the time to do it in the next
>>> two days). It would be great if somebody could do this before we may re-cut
>>> this release.
>>> I do not have any problems to re-cut the release if it's in the right shape
>>> in a few days (this week). I think this will be the case. I have free
>>> cycles on Wednesday and may be on the late Thursday.
>>>
>>> Other thoughts?
>>>
>>> Best,
>>> Christian
>>>
>>>
>>> On Mon, Apr 15, 2013 at 3:17 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>>
>>>> Hi
>>>>
>>>> Did anyone test the maven archetypes to create new Camel projects?
>>>> They are really valuable for new users to Camel and existing for
>>>> creating new projects.
>>>>
>>>> IMHO we should give them a test spin to see if they create projects
>>>> that works out of the box.
>>>>
>>>>
>>>> On Mon, Apr 15, 2013 at 11:58 AM, Willem jiang <wi...@gmail.com>
>>>> wrote:
>>>> >
>>>> > I fixed some of the example issues today, please double check them if
>>>> you have time.
>>>> > As we don't create the camel 2.11.x branch, it could be much easy if we
>>>> recut the Camel 2.11.0 from the trunk.
>>>> >
>>>> >
>>>> > --
>>>> > Willem Jiang
>>>> >
>>>> > Red Hat, Inc.
>>>> > FuseSource is now part of Red Hat
>>>> > Web: http://www.fusesource.com | http://www.redhat.com
>>>> > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
>>>> (English)
>>>> > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
>>>> > Twitter: willemjiang
>>>> > Weibo: 姜宁willem
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > On Monday, April 15, 2013 at 3:18 PM, Claus Ibsen wrote:
>>>> >
>>>> >> Hi
>>>> >>
>>>> >> I actually think this RC has too many out of the box issues for new
>>>> >> users to Camel.
>>>> >> For example all the example issues.
>>>> >>
>>>> >> Also we have that performance degrade related to the linked ticket from
>>>> >> https://issues.apache.org/jira/browse/CAMEL-6282
>>>> >>
>>>> >> And about 10+ fixes already since the RC.
>>>> >>
>>>> >> I really do think we should redo the release when we have all the
>>>> >> examples fixed.
>>>> >> As well that CAMEL-6282.
>>>> >>
>>>> >> And also in light that Camel 2.11 is a big new release of Camel. And
>>>> >> will maybe hit the news etc, as its almost 10 months since Camel 2.10
>>>> >> was released.
>>>> >> And I prefer Camel this release to be at its best.
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> On Sun, Apr 14, 2013 at 9:25 PM, Christian Müller
>>>> >> <christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
>>>> wrote:
>>>> >> > +1
>>>> >> >
>>>> >> > I found a few issues during testing this release, but none of them are
>>>> >> > critical in my opinion (most of them are related to our examples). I
>>>> prefer
>>>> >> > to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks
>>>> after
>>>> >> > we fixed the issues.
>>>> >> >
>>>> >> > Because we got only two votes until now, I extend the voting period
>>>> for
>>>> >> > additional 48 hours.
>>>> >> >
>>>> >> > Best,
>>>> >> > Christian
>>>> >> >
>>>> >> >
>>>> >> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
>>>> >> > christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
>>>> wrote:
>>>> >> >
>>>> >> > > After 9 month of development, we have a new minor release candidate
>>>> >> > > apache-camel-2.11.0 ready.
>>>> >> > > It comes with 659 issues resolved: new features, improvements and
>>>> bug
>>>> >> > > fixes [1]. You can find the release notes here [2].
>>>> >> > >
>>>> >> > > Please find the staging repo here:
>>>> >> > >
>>>> https://repository.apache.org/content/repositories/orgapachecamel-092/
>>>> >> > >
>>>> >> > > The tarballs are here
>>>> >> > >
>>>> >> > >
>>>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>>>> >> > >
>>>> >> > > Tag:
>>>> >> > > http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>>>> >> > >
>>>> >> > > Please review, help out with testing and vote to approve this
>>>> release
>>>> >> > > binary. Please mention what you tested to prevent duplicate work.
>>>> Your vote
>>>> >> > > counts!
>>>> >> > >
>>>> >> > > [ ] +1 Release the binary as Apache Camel 2.11.0
>>>> >> > > [ ] -1 Veto the release (provide specific comments)
>>>> >> > > Vote is open for at least 72 hours.
>>>> >> > >
>>>> >> > > Thanks in advance,
>>>> >> > > Christian
>>>> >> > >
>>>> >> > > [1]
>>>> >> > >
>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>>>> >> > > [2]
>>>> >> > >
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>>>> >> >
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Claus Ibsen
>>>> >> -----------------
>>>> >> Red Hat, Inc.
>>>> >> FuseSource is now part of Red Hat
>>>> >> Email: cibsen@redhat.com (mailto:cibsen@redhat.com)
>>>> >> Web: http://fusesource.com
>>>> >> Twitter: davsclaus
>>>> >> Blog: http://davsclaus.com
>>>> >> Author of Camel in Action: http://www.manning.com/ibsen
>>>> >
>>>> >
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> Red Hat, Inc.
>>>> FuseSource is now part of Red Hat
>>>> Email: cibsen@redhat.com
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus
>>>> Blog: http://davsclaus.com
>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
The camel karaf commands may have a problem. Just noticed
camel:context-list didn't return any data, when I had a Camel app in
karaf.
On Tue, Apr 16, 2013 at 3:14 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Yeah it would be lovely to re-cut the release tomorrow.
>
> I will give the examples on trunk a test spin as well, to see if they
> are working all.
>
>
>
> On Mon, Apr 15, 2013 at 7:51 PM, Christian Müller
> <ch...@gmail.com> wrote:
>> I didn't test the archetypes (and don't have the time to do it in the next
>> two days). It would be great if somebody could do this before we may re-cut
>> this release.
>> I do not have any problems to re-cut the release if it's in the right shape
>> in a few days (this week). I think this will be the case. I have free
>> cycles on Wednesday and may be on the late Thursday.
>>
>> Other thoughts?
>>
>> Best,
>> Christian
>>
>>
>> On Mon, Apr 15, 2013 at 3:17 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>
>>> Hi
>>>
>>> Did anyone test the maven archetypes to create new Camel projects?
>>> They are really valuable for new users to Camel and existing for
>>> creating new projects.
>>>
>>> IMHO we should give them a test spin to see if they create projects
>>> that works out of the box.
>>>
>>>
>>> On Mon, Apr 15, 2013 at 11:58 AM, Willem jiang <wi...@gmail.com>
>>> wrote:
>>> >
>>> > I fixed some of the example issues today, please double check them if
>>> you have time.
>>> > As we don't create the camel 2.11.x branch, it could be much easy if we
>>> recut the Camel 2.11.0 from the trunk.
>>> >
>>> >
>>> > --
>>> > Willem Jiang
>>> >
>>> > Red Hat, Inc.
>>> > FuseSource is now part of Red Hat
>>> > Web: http://www.fusesource.com | http://www.redhat.com
>>> > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
>>> (English)
>>> > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
>>> > Twitter: willemjiang
>>> > Weibo: 姜宁willem
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Monday, April 15, 2013 at 3:18 PM, Claus Ibsen wrote:
>>> >
>>> >> Hi
>>> >>
>>> >> I actually think this RC has too many out of the box issues for new
>>> >> users to Camel.
>>> >> For example all the example issues.
>>> >>
>>> >> Also we have that performance degrade related to the linked ticket from
>>> >> https://issues.apache.org/jira/browse/CAMEL-6282
>>> >>
>>> >> And about 10+ fixes already since the RC.
>>> >>
>>> >> I really do think we should redo the release when we have all the
>>> >> examples fixed.
>>> >> As well that CAMEL-6282.
>>> >>
>>> >> And also in light that Camel 2.11 is a big new release of Camel. And
>>> >> will maybe hit the news etc, as its almost 10 months since Camel 2.10
>>> >> was released.
>>> >> And I prefer Camel this release to be at its best.
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> On Sun, Apr 14, 2013 at 9:25 PM, Christian Müller
>>> >> <christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
>>> wrote:
>>> >> > +1
>>> >> >
>>> >> > I found a few issues during testing this release, but none of them are
>>> >> > critical in my opinion (most of them are related to our examples). I
>>> prefer
>>> >> > to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks
>>> after
>>> >> > we fixed the issues.
>>> >> >
>>> >> > Because we got only two votes until now, I extend the voting period
>>> for
>>> >> > additional 48 hours.
>>> >> >
>>> >> > Best,
>>> >> > Christian
>>> >> >
>>> >> >
>>> >> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
>>> >> > christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
>>> wrote:
>>> >> >
>>> >> > > After 9 month of development, we have a new minor release candidate
>>> >> > > apache-camel-2.11.0 ready.
>>> >> > > It comes with 659 issues resolved: new features, improvements and
>>> bug
>>> >> > > fixes [1]. You can find the release notes here [2].
>>> >> > >
>>> >> > > Please find the staging repo here:
>>> >> > >
>>> https://repository.apache.org/content/repositories/orgapachecamel-092/
>>> >> > >
>>> >> > > The tarballs are here
>>> >> > >
>>> >> > >
>>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>>> >> > >
>>> >> > > Tag:
>>> >> > > http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>>> >> > >
>>> >> > > Please review, help out with testing and vote to approve this
>>> release
>>> >> > > binary. Please mention what you tested to prevent duplicate work.
>>> Your vote
>>> >> > > counts!
>>> >> > >
>>> >> > > [ ] +1 Release the binary as Apache Camel 2.11.0
>>> >> > > [ ] -1 Veto the release (provide specific comments)
>>> >> > > Vote is open for at least 72 hours.
>>> >> > >
>>> >> > > Thanks in advance,
>>> >> > > Christian
>>> >> > >
>>> >> > > [1]
>>> >> > >
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>>> >> > > [2]
>>> >> > >
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Claus Ibsen
>>> >> -----------------
>>> >> Red Hat, Inc.
>>> >> FuseSource is now part of Red Hat
>>> >> Email: cibsen@redhat.com (mailto:cibsen@redhat.com)
>>> >> Web: http://fusesource.com
>>> >> Twitter: davsclaus
>>> >> Blog: http://davsclaus.com
>>> >> Author of Camel in Action: http://www.manning.com/ibsen
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> Red Hat, Inc.
>>> FuseSource is now part of Red Hat
>>> Email: cibsen@redhat.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Yeah it would be lovely to re-cut the release tomorrow.
I will give the examples on trunk a test spin as well, to see if they
are working all.
On Mon, Apr 15, 2013 at 7:51 PM, Christian Müller
<ch...@gmail.com> wrote:
> I didn't test the archetypes (and don't have the time to do it in the next
> two days). It would be great if somebody could do this before we may re-cut
> this release.
> I do not have any problems to re-cut the release if it's in the right shape
> in a few days (this week). I think this will be the case. I have free
> cycles on Wednesday and may be on the late Thursday.
>
> Other thoughts?
>
> Best,
> Christian
>
>
> On Mon, Apr 15, 2013 at 3:17 PM, Claus Ibsen <cl...@gmail.com> wrote:
>
>> Hi
>>
>> Did anyone test the maven archetypes to create new Camel projects?
>> They are really valuable for new users to Camel and existing for
>> creating new projects.
>>
>> IMHO we should give them a test spin to see if they create projects
>> that works out of the box.
>>
>>
>> On Mon, Apr 15, 2013 at 11:58 AM, Willem jiang <wi...@gmail.com>
>> wrote:
>> >
>> > I fixed some of the example issues today, please double check them if
>> you have time.
>> > As we don't create the camel 2.11.x branch, it could be much easy if we
>> recut the Camel 2.11.0 from the trunk.
>> >
>> >
>> > --
>> > Willem Jiang
>> >
>> > Red Hat, Inc.
>> > FuseSource is now part of Red Hat
>> > Web: http://www.fusesource.com | http://www.redhat.com
>> > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
>> (English)
>> > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
>> > Twitter: willemjiang
>> > Weibo: 姜宁willem
>> >
>> >
>> >
>> >
>> >
>> > On Monday, April 15, 2013 at 3:18 PM, Claus Ibsen wrote:
>> >
>> >> Hi
>> >>
>> >> I actually think this RC has too many out of the box issues for new
>> >> users to Camel.
>> >> For example all the example issues.
>> >>
>> >> Also we have that performance degrade related to the linked ticket from
>> >> https://issues.apache.org/jira/browse/CAMEL-6282
>> >>
>> >> And about 10+ fixes already since the RC.
>> >>
>> >> I really do think we should redo the release when we have all the
>> >> examples fixed.
>> >> As well that CAMEL-6282.
>> >>
>> >> And also in light that Camel 2.11 is a big new release of Camel. And
>> >> will maybe hit the news etc, as its almost 10 months since Camel 2.10
>> >> was released.
>> >> And I prefer Camel this release to be at its best.
>> >>
>> >>
>> >>
>> >>
>> >> On Sun, Apr 14, 2013 at 9:25 PM, Christian Müller
>> >> <christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
>> wrote:
>> >> > +1
>> >> >
>> >> > I found a few issues during testing this release, but none of them are
>> >> > critical in my opinion (most of them are related to our examples). I
>> prefer
>> >> > to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks
>> after
>> >> > we fixed the issues.
>> >> >
>> >> > Because we got only two votes until now, I extend the voting period
>> for
>> >> > additional 48 hours.
>> >> >
>> >> > Best,
>> >> > Christian
>> >> >
>> >> >
>> >> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
>> >> > christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
>> wrote:
>> >> >
>> >> > > After 9 month of development, we have a new minor release candidate
>> >> > > apache-camel-2.11.0 ready.
>> >> > > It comes with 659 issues resolved: new features, improvements and
>> bug
>> >> > > fixes [1]. You can find the release notes here [2].
>> >> > >
>> >> > > Please find the staging repo here:
>> >> > >
>> https://repository.apache.org/content/repositories/orgapachecamel-092/
>> >> > >
>> >> > > The tarballs are here
>> >> > >
>> >> > >
>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>> >> > >
>> >> > > Tag:
>> >> > > http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>> >> > >
>> >> > > Please review, help out with testing and vote to approve this
>> release
>> >> > > binary. Please mention what you tested to prevent duplicate work.
>> Your vote
>> >> > > counts!
>> >> > >
>> >> > > [ ] +1 Release the binary as Apache Camel 2.11.0
>> >> > > [ ] -1 Veto the release (provide specific comments)
>> >> > > Vote is open for at least 72 hours.
>> >> > >
>> >> > > Thanks in advance,
>> >> > > Christian
>> >> > >
>> >> > > [1]
>> >> > >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>> >> > > [2]
>> >> > >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>> >> >
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Claus Ibsen
>> >> -----------------
>> >> Red Hat, Inc.
>> >> FuseSource is now part of Red Hat
>> >> Email: cibsen@redhat.com (mailto:cibsen@redhat.com)
>> >> Web: http://fusesource.com
>> >> Twitter: davsclaus
>> >> Blog: http://davsclaus.com
>> >> Author of Camel in Action: http://www.manning.com/ibsen
>> >
>> >
>> >
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Christian Müller <ch...@gmail.com>.
I didn't test the archetypes (and don't have the time to do it in the next
two days). It would be great if somebody could do this before we may re-cut
this release.
I do not have any problems to re-cut the release if it's in the right shape
in a few days (this week). I think this will be the case. I have free
cycles on Wednesday and may be on the late Thursday.
Other thoughts?
Best,
Christian
On Mon, Apr 15, 2013 at 3:17 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Did anyone test the maven archetypes to create new Camel projects?
> They are really valuable for new users to Camel and existing for
> creating new projects.
>
> IMHO we should give them a test spin to see if they create projects
> that works out of the box.
>
>
> On Mon, Apr 15, 2013 at 11:58 AM, Willem jiang <wi...@gmail.com>
> wrote:
> >
> > I fixed some of the example issues today, please double check them if
> you have time.
> > As we don't create the camel 2.11.x branch, it could be much easy if we
> recut the Camel 2.11.0 from the trunk.
> >
> >
> > --
> > Willem Jiang
> >
> > Red Hat, Inc.
> > FuseSource is now part of Red Hat
> > Web: http://www.fusesource.com | http://www.redhat.com
> > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
> (English)
> > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> >
> >
> >
> >
> > On Monday, April 15, 2013 at 3:18 PM, Claus Ibsen wrote:
> >
> >> Hi
> >>
> >> I actually think this RC has too many out of the box issues for new
> >> users to Camel.
> >> For example all the example issues.
> >>
> >> Also we have that performance degrade related to the linked ticket from
> >> https://issues.apache.org/jira/browse/CAMEL-6282
> >>
> >> And about 10+ fixes already since the RC.
> >>
> >> I really do think we should redo the release when we have all the
> >> examples fixed.
> >> As well that CAMEL-6282.
> >>
> >> And also in light that Camel 2.11 is a big new release of Camel. And
> >> will maybe hit the news etc, as its almost 10 months since Camel 2.10
> >> was released.
> >> And I prefer Camel this release to be at its best.
> >>
> >>
> >>
> >>
> >> On Sun, Apr 14, 2013 at 9:25 PM, Christian Müller
> >> <christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
> wrote:
> >> > +1
> >> >
> >> > I found a few issues during testing this release, but none of them are
> >> > critical in my opinion (most of them are related to our examples). I
> prefer
> >> > to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks
> after
> >> > we fixed the issues.
> >> >
> >> > Because we got only two votes until now, I extend the voting period
> for
> >> > additional 48 hours.
> >> >
> >> > Best,
> >> > Christian
> >> >
> >> >
> >> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> >> > christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)>
> wrote:
> >> >
> >> > > After 9 month of development, we have a new minor release candidate
> >> > > apache-camel-2.11.0 ready.
> >> > > It comes with 659 issues resolved: new features, improvements and
> bug
> >> > > fixes [1]. You can find the release notes here [2].
> >> > >
> >> > > Please find the staging repo here:
> >> > >
> https://repository.apache.org/content/repositories/orgapachecamel-092/
> >> > >
> >> > > The tarballs are here
> >> > >
> >> > >
> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
> >> > >
> >> > > Tag:
> >> > > http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
> >> > >
> >> > > Please review, help out with testing and vote to approve this
> release
> >> > > binary. Please mention what you tested to prevent duplicate work.
> Your vote
> >> > > counts!
> >> > >
> >> > > [ ] +1 Release the binary as Apache Camel 2.11.0
> >> > > [ ] -1 Veto the release (provide specific comments)
> >> > > Vote is open for at least 72 hours.
> >> > >
> >> > > Thanks in advance,
> >> > > Christian
> >> > >
> >> > > [1]
> >> > >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> >> > > [2]
> >> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
> >> >
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> Red Hat, Inc.
> >> FuseSource is now part of Red Hat
> >> Email: cibsen@redhat.com (mailto:cibsen@redhat.com)
> >> Web: http://fusesource.com
> >> Twitter: davsclaus
> >> Blog: http://davsclaus.com
> >> Author of Camel in Action: http://www.manning.com/ibsen
> >
> >
> >
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Did anyone test the maven archetypes to create new Camel projects?
They are really valuable for new users to Camel and existing for
creating new projects.
IMHO we should give them a test spin to see if they create projects
that works out of the box.
On Mon, Apr 15, 2013 at 11:58 AM, Willem jiang <wi...@gmail.com> wrote:
>
> I fixed some of the example issues today, please double check them if you have time.
> As we don't create the camel 2.11.x branch, it could be much easy if we recut the Camel 2.11.0 from the trunk.
>
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Web: http://www.fusesource.com | http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
> http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
>
>
> On Monday, April 15, 2013 at 3:18 PM, Claus Ibsen wrote:
>
>> Hi
>>
>> I actually think this RC has too many out of the box issues for new
>> users to Camel.
>> For example all the example issues.
>>
>> Also we have that performance degrade related to the linked ticket from
>> https://issues.apache.org/jira/browse/CAMEL-6282
>>
>> And about 10+ fixes already since the RC.
>>
>> I really do think we should redo the release when we have all the
>> examples fixed.
>> As well that CAMEL-6282.
>>
>> And also in light that Camel 2.11 is a big new release of Camel. And
>> will maybe hit the news etc, as its almost 10 months since Camel 2.10
>> was released.
>> And I prefer Camel this release to be at its best.
>>
>>
>>
>>
>> On Sun, Apr 14, 2013 at 9:25 PM, Christian Müller
>> <christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)> wrote:
>> > +1
>> >
>> > I found a few issues during testing this release, but none of them are
>> > critical in my opinion (most of them are related to our examples). I prefer
>> > to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks after
>> > we fixed the issues.
>> >
>> > Because we got only two votes until now, I extend the voting period for
>> > additional 48 hours.
>> >
>> > Best,
>> > Christian
>> >
>> >
>> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
>> > christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)> wrote:
>> >
>> > > After 9 month of development, we have a new minor release candidate
>> > > apache-camel-2.11.0 ready.
>> > > It comes with 659 issues resolved: new features, improvements and bug
>> > > fixes [1]. You can find the release notes here [2].
>> > >
>> > > Please find the staging repo here:
>> > > https://repository.apache.org/content/repositories/orgapachecamel-092/
>> > >
>> > > The tarballs are here
>> > >
>> > > https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>> > >
>> > > Tag:
>> > > http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>> > >
>> > > Please review, help out with testing and vote to approve this release
>> > > binary. Please mention what you tested to prevent duplicate work. Your vote
>> > > counts!
>> > >
>> > > [ ] +1 Release the binary as Apache Camel 2.11.0
>> > > [ ] -1 Veto the release (provide specific comments)
>> > > Vote is open for at least 72 hours.
>> > >
>> > > Thanks in advance,
>> > > Christian
>> > >
>> > > [1]
>> > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>> > > [2]
>> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>> >
>>
>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com (mailto:cibsen@redhat.com)
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Willem jiang <wi...@gmail.com>.
I fixed some of the example issues today, please double check them if you have time.
As we don't create the camel 2.11.x branch, it could be much easy if we recut the Camel 2.11.0 from the trunk.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Monday, April 15, 2013 at 3:18 PM, Claus Ibsen wrote:
> Hi
>
> I actually think this RC has too many out of the box issues for new
> users to Camel.
> For example all the example issues.
>
> Also we have that performance degrade related to the linked ticket from
> https://issues.apache.org/jira/browse/CAMEL-6282
>
> And about 10+ fixes already since the RC.
>
> I really do think we should redo the release when we have all the
> examples fixed.
> As well that CAMEL-6282.
>
> And also in light that Camel 2.11 is a big new release of Camel. And
> will maybe hit the news etc, as its almost 10 months since Camel 2.10
> was released.
> And I prefer Camel this release to be at its best.
>
>
>
>
> On Sun, Apr 14, 2013 at 9:25 PM, Christian Müller
> <christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)> wrote:
> > +1
> >
> > I found a few issues during testing this release, but none of them are
> > critical in my opinion (most of them are related to our examples). I prefer
> > to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks after
> > we fixed the issues.
> >
> > Because we got only two votes until now, I extend the voting period for
> > additional 48 hours.
> >
> > Best,
> > Christian
> >
> >
> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> > christian.mueller@gmail.com (mailto:christian.mueller@gmail.com)> wrote:
> >
> > > After 9 month of development, we have a new minor release candidate
> > > apache-camel-2.11.0 ready.
> > > It comes with 659 issues resolved: new features, improvements and bug
> > > fixes [1]. You can find the release notes here [2].
> > >
> > > Please find the staging repo here:
> > > https://repository.apache.org/content/repositories/orgapachecamel-092/
> > >
> > > The tarballs are here
> > >
> > > https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
> > >
> > > Tag:
> > > http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
> > >
> > > Please review, help out with testing and vote to approve this release
> > > binary. Please mention what you tested to prevent duplicate work. Your vote
> > > counts!
> > >
> > > [ ] +1 Release the binary as Apache Camel 2.11.0
> > > [ ] -1 Veto the release (provide specific comments)
> > > Vote is open for at least 72 hours.
> > >
> > > Thanks in advance,
> > > Christian
> > >
> > > [1]
> > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> > > [2]
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
> >
>
>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com (mailto:cibsen@redhat.com)
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Guillaume Nodet <gn...@apache.org>.
Yeah, having a clean 2.11 release would be better obviously.
2013/4/15 Claus Ibsen <cl...@gmail.com>
> Hi
>
> I actually think this RC has too many out of the box issues for new
> users to Camel.
> For example all the example issues.
>
> Also we have that performance degrade related to the linked ticket from
> https://issues.apache.org/jira/browse/CAMEL-6282
>
> And about 10+ fixes already since the RC.
>
> I really do think we should redo the release when we have all the
> examples fixed.
> As well that CAMEL-6282.
>
> And also in light that Camel 2.11 is a big new release of Camel. And
> will maybe hit the news etc, as its almost 10 months since Camel 2.10
> was released.
> And I prefer Camel this release to be at its best.
>
>
>
>
> On Sun, Apr 14, 2013 at 9:25 PM, Christian Müller
> <ch...@gmail.com> wrote:
> > +1
> >
> > I found a few issues during testing this release, but none of them are
> > critical in my opinion (most of them are related to our examples). I
> prefer
> > to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks
> after
> > we fixed the issues.
> >
> > Because we got only two votes until now, I extend the voting period for
> > additional 48 hours.
> >
> > Best,
> > Christian
> >
> >
> > On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> > christian.mueller@gmail.com> wrote:
> >
> >> After 9 month of development, we have a new minor release candidate
> >> apache-camel-2.11.0 ready.
> >> It comes with 659 issues resolved: new features, improvements and bug
> >> fixes [1]. You can find the release notes here [2].
> >>
> >> Please find the staging repo here:
> >> https://repository.apache.org/content/repositories/orgapachecamel-092/
> >>
> >> The tarballs are here
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
> >>
> >> Tag:
> >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
> >>
> >> Please review, help out with testing and vote to approve this release
> >> binary. Please mention what you tested to prevent duplicate work. Your
> vote
> >> counts!
> >>
> >> [ ] +1 Release the binary as Apache Camel 2.11.0
> >> [ ] -1 Veto the release (provide specific comments)
> >> Vote is open for at least 72 hours.
> >>
> >> Thanks in advance,
> >> Christian
> >>
> >> [1]
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> >> [2]
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
> >>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I actually think this RC has too many out of the box issues for new
users to Camel.
For example all the example issues.
Also we have that performance degrade related to the linked ticket from
https://issues.apache.org/jira/browse/CAMEL-6282
And about 10+ fixes already since the RC.
I really do think we should redo the release when we have all the
examples fixed.
As well that CAMEL-6282.
And also in light that Camel 2.11 is a big new release of Camel. And
will maybe hit the news etc, as its almost 10 months since Camel 2.10
was released.
And I prefer Camel this release to be at its best.
On Sun, Apr 14, 2013 at 9:25 PM, Christian Müller
<ch...@gmail.com> wrote:
> +1
>
> I found a few issues during testing this release, but none of them are
> critical in my opinion (most of them are related to our examples). I prefer
> to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks after
> we fixed the issues.
>
> Because we got only two votes until now, I extend the voting period for
> additional 48 hours.
>
> Best,
> Christian
>
>
> On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> christian.mueller@gmail.com> wrote:
>
>> After 9 month of development, we have a new minor release candidate
>> apache-camel-2.11.0 ready.
>> It comes with 659 issues resolved: new features, improvements and bug
>> fixes [1]. You can find the release notes here [2].
>>
>> Please find the staging repo here:
>> https://repository.apache.org/content/repositories/orgapachecamel-092/
>>
>> The tarballs are here
>>
>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>>
>> Tag:
>> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>>
>> Please review, help out with testing and vote to approve this release
>> binary. Please mention what you tested to prevent duplicate work. Your vote
>> counts!
>>
>> [ ] +1 Release the binary as Apache Camel 2.11.0
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Thanks in advance,
>> Christian
>>
>> [1]
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>> [2]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>>
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Guillaume Nodet <gn...@gmail.com>.
On Sun, Apr 14, 2013 at 9:25 PM, Christian Müller <
christian.mueller@gmail.com> wrote:
> +1
>
> I found a few issues during testing this release, but none of them are
> critical in my opinion (most of them are related to our examples). I prefer
> to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks after
> we fixed the issues.
>
> Because we got only two votes until now, I extend the voting period for
> additional 48 hours.
>
> Best,
> Christian
>
>
> On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> christian.mueller@gmail.com> wrote:
>
> > After 9 month of development, we have a new minor release candidate
> > apache-camel-2.11.0 ready.
> > It comes with 659 issues resolved: new features, improvements and bug
> > fixes [1]. You can find the release notes here [2].
> >
> > Please find the staging repo here:
> > https://repository.apache.org/content/repositories/orgapachecamel-092/
> >
> > The tarballs are here
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
> >
> > Tag:
> > http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
> >
> > Please review, help out with testing and vote to approve this release
> > binary. Please mention what you tested to prevent duplicate work. Your
> vote
> > counts!
> >
> > [ ] +1 Release the binary as Apache Camel 2.11.0
> > [ ] -1 Veto the release (provide specific comments)
> > Vote is open for at least 72 hours.
> >
> > Thanks in advance,
> > Christian
> >
> > [1]
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> > [2]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
> >
>
--
------------------------
Guillaume Nodet
------------------------
Red Hat, Open Source Integration
Email: gnodet@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Christian Müller <ch...@gmail.com>.
+1
I found a few issues during testing this release, but none of them are
critical in my opinion (most of them are related to our examples). I prefer
to deliver Camel 2.11.0 now and a Camel 2.11.1 release in 3 - 6 weeks after
we fixed the issues.
Because we got only two votes until now, I extend the voting period for
additional 48 hours.
Best,
Christian
On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
christian.mueller@gmail.com> wrote:
> After 9 month of development, we have a new minor release candidate
> apache-camel-2.11.0 ready.
> It comes with 659 issues resolved: new features, improvements and bug
> fixes [1]. You can find the release notes here [2].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-092/
>
> The tarballs are here
>
> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>
> Please review, help out with testing and vote to approve this release
> binary. Please mention what you tested to prevent duplicate work. Your vote
> counts!
>
> [ ] +1 Release the binary as Apache Camel 2.11.0
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks in advance,
> Christian
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> [2]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Claus Ibsen <cl...@gmail.com>.
The camel-example-console has some WARN logs when shutting down the jvm
[ Thread-1] DefaultShutdownStrategy INFO
Starting to graceful shutdown 1 routes (timeout 300 seconds)
[el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
Waited 2.001 seconds for ExecutorService:
org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@48b4da9b[Shutting
down, pool size = 1, active threads = 1, queued tasks = 0, completed
tasks = 0][stream://in?promptMessage=Enter+something%3A+] to
terminate...
[el-1) thread #2 - ShutdownTask] DefaultExecutorServiceManager INFO
Waited 4.002 seconds for ExecutorService:
org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@48b4da9b[Shutting
down, pool size = 1, active threads = 1, queued tasks = 0, completed
tasks = 0][stream://in?promptMessage=Enter+something%3A+] to
terminate...
On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller
<ch...@gmail.com> wrote:
> After 9 month of development, we have a new minor release candidate
> apache-camel-2.11.0 ready.
> It comes with 659 issues resolved: new features, improvements and bug fixes
> [1]. You can find the release notes here [2].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-092/
>
> The tarballs are here
> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>
> Please review, help out with testing and vote to approve this release
> binary. Please mention what you tested to prevent duplicate work. Your vote
> counts!
>
> [ ] +1 Release the binary as Apache Camel 2.11.0
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks in advance,
> Christian
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> [2]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I fixed the camel-jclouds installation problem
https://issues.apache.org/jira/browse/CAMEL-6270
On Fri, Apr 12, 2013 at 7:08 PM, Christian Müller
<ch...@gmail.com> wrote:
> Still testing but want to let you know the installation of the following
> features in Karaf 2.3.1 failed for me (I guess the last two are issues in
> Karaf/Felix):
>
> camel-jclouds
> Error executing command: Could not start bundle
> mvn:org.apache.camel/camel-jclouds/2.11.0 in feature(s)
> camel-jclouds-2.11.0: Unresolved constraint in bundle
> org.apache.camel.camel-jclouds [79]: Unable to resolve 79.0: missing
> requirement [79.0] osgi.wiring.package;
> (&(osgi.wiring.package=com.google.common.base)(version>=14.0.0)(!(version>=15.0.0)))
>
>
> camel-leveldb
> Error executing command: Could not start bundle
> wrap:mvn:org.fusesource.leveldbjni/leveldbjni-all/1.6$Bundle-Version=1.6&Export-Package=*;-noimport:=true;version="1.6"
> in feature(s) camel-leveldb-2.11.0: Unresolved constraint in bundle
> org.fusesource.leveldbjni.leveldbjni-all [80]: No matching native libraries
> found.
>
>
> camel-mybatis (Karaf hangs - no log entry)
>
>
> camel-dozer + camel-eventadmin
> ERROR: Bundle org.ops4j.pax.web.pax-web-runtime [82] EventDispatcher: Error
> during dispatch. (java.lang.NoClassDefFoundError:
> org/osgi/service/event/EventAdmin)
> java.lang.NoClassDefFoundError: org/osgi/service/event/EventAdmin
> at
> org.ops4j.pax.web.service.internal.Activator$EventServiceCustomizer.addingService(Activator.java:418)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:932)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:1)
> at
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:894)
> at
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)
> at
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)
> at
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4260)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3275)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:320)
> at
> org.apache.felix.eventadmin.impl.Configuration.startOrUpdate(Configuration.java:324)
> at
> org.apache.felix.eventadmin.impl.Configuration.<init>(Configuration.java:142)
> at org.apache.felix.eventadmin.impl.Activator.start(Activator.java:65)
> at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1977)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1895)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:944)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:931)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:479)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:396)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:392)
> at
> org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)
> at
> org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:41)
> at
> org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)
> at
> org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)
> at
> org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)
> at
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> at
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> at org.apache.karaf.shell.console.jline.Console.run(Console.java:174)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: java.lang.ClassNotFoundException:
> org.osgi.service.event.EventAdmin not found by
> org.ops4j.pax.web.pax-web-runtime [82]
> at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1460)
> at
> org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 37 more
> ERROR: Bundle org.ops4j.pax.web.pax-web-extender-war [88] EventDispatcher:
> Error during dispatch. (java.lang.NoClassDefFoundError:
> org/osgi/service/event/EventAdmin)
> java.lang.NoClassDefFoundError: org/osgi/service/event/EventAdmin
> at
> org.ops4j.pax.web.extender.war.internal.Activator$EventServiceCustomizer.addingService(Activator.java:189)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:932)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:1)
> at
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:894)
> at
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)
> at
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)
> at
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4260)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3275)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:320)
> at
> org.apache.felix.eventadmin.impl.Configuration.startOrUpdate(Configuration.java:324)
> at
> org.apache.felix.eventadmin.impl.Configuration.<init>(Configuration.java:142)
> at org.apache.felix.eventadmin.impl.Activator.start(Activator.java:65)
> at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1977)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1895)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:944)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:931)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:479)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:396)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:392)
> at
> org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)
> at
> org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:41)
> at
> org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)
> at
> org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)
> at
> org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)
> at
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> at
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> at org.apache.karaf.shell.console.jline.Console.run(Console.java:174)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: java.lang.ClassNotFoundException:
> org.osgi.service.event.EventAdmin not found by
> org.ops4j.pax.web.pax-web-extender-war [88]
> at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1460)
> at
> org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 37 more
>
>
> I also miss a "camel-leveldb" WIKI page. Couldn't find one...
>
> Best,
> Christian
>
>
> On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> christian.mueller@gmail.com> wrote:
>
>> After 9 month of development, we have a new minor release candidate
>> apache-camel-2.11.0 ready.
>> It comes with 659 issues resolved: new features, improvements and bug
>> fixes [1]. You can find the release notes here [2].
>>
>> Please find the staging repo here:
>> https://repository.apache.org/content/repositories/orgapachecamel-092/
>>
>> The tarballs are here
>>
>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>>
>> Tag:
>> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>>
>> Please review, help out with testing and vote to approve this release
>> binary. Please mention what you tested to prevent duplicate work. Your vote
>> counts!
>>
>> [ ] +1 Release the binary as Apache Camel 2.11.0
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Thanks in advance,
>> Christian
>>
>> [1]
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>> [2]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>>
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I was able to install camel-mybatis with no problems
karaf@root> features:install camel-mybatis
karaf@root> list
START LEVEL 100 , List Threshold: 50
ID State Blueprint Spring Level Name
[ 60] [Active ] [ ] [ ] [ 50] camel-core (2.11.0)
[ 61] [Active ] [Created ] [ ] [ 50]
camel-karaf-commands (2.11.0)
[ 76] [Active ] [ ] [ ] [ 50]
geronimo-jta_1.1_spec (1.1.1)
[ 77] [Active ] [ ] [ ] [ 50] camel-spring (2.11.0)
[ 78] [Active ] [Created ] [ ] [ 50] camel-blueprint (2.11.0)
[ 79] [Active ] [ ] [ ] [ 50] Commons Pool (1.6.0)
[ 80] [Active ] [ ] [ ] [ 50]
geronimo-servlet_2.5_spec (1.2)
[ 81] [Active ] [ ] [ ] [ 50] Apache
ServiceMix :: Bundles :: commons-dbcp (1.4.0.3)
[ 82] [Active ] [ ] [ ] [ 50] Apache
ServiceMix :: Bundles :: cglib (2.1.0.3_7)
[ 83] [Active ] [ ] [ ] [ 50] MyBatis (3.2.2)
[ 84] [Active ] [ ] [ ] [ 50] camel-mybatis (2.11.0)
On Fri, Apr 12, 2013 at 7:08 PM, Christian Müller
<ch...@gmail.com> wrote:
> Still testing but want to let you know the installation of the following
> features in Karaf 2.3.1 failed for me (I guess the last two are issues in
> Karaf/Felix):
>
> camel-jclouds
> Error executing command: Could not start bundle
> mvn:org.apache.camel/camel-jclouds/2.11.0 in feature(s)
> camel-jclouds-2.11.0: Unresolved constraint in bundle
> org.apache.camel.camel-jclouds [79]: Unable to resolve 79.0: missing
> requirement [79.0] osgi.wiring.package;
> (&(osgi.wiring.package=com.google.common.base)(version>=14.0.0)(!(version>=15.0.0)))
>
>
> camel-leveldb
> Error executing command: Could not start bundle
> wrap:mvn:org.fusesource.leveldbjni/leveldbjni-all/1.6$Bundle-Version=1.6&Export-Package=*;-noimport:=true;version="1.6"
> in feature(s) camel-leveldb-2.11.0: Unresolved constraint in bundle
> org.fusesource.leveldbjni.leveldbjni-all [80]: No matching native libraries
> found.
>
>
> camel-mybatis (Karaf hangs - no log entry)
>
>
> camel-dozer + camel-eventadmin
> ERROR: Bundle org.ops4j.pax.web.pax-web-runtime [82] EventDispatcher: Error
> during dispatch. (java.lang.NoClassDefFoundError:
> org/osgi/service/event/EventAdmin)
> java.lang.NoClassDefFoundError: org/osgi/service/event/EventAdmin
> at
> org.ops4j.pax.web.service.internal.Activator$EventServiceCustomizer.addingService(Activator.java:418)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:932)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:1)
> at
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:894)
> at
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)
> at
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)
> at
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4260)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3275)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:320)
> at
> org.apache.felix.eventadmin.impl.Configuration.startOrUpdate(Configuration.java:324)
> at
> org.apache.felix.eventadmin.impl.Configuration.<init>(Configuration.java:142)
> at org.apache.felix.eventadmin.impl.Activator.start(Activator.java:65)
> at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1977)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1895)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:944)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:931)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:479)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:396)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:392)
> at
> org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)
> at
> org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:41)
> at
> org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)
> at
> org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)
> at
> org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)
> at
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> at
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> at org.apache.karaf.shell.console.jline.Console.run(Console.java:174)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: java.lang.ClassNotFoundException:
> org.osgi.service.event.EventAdmin not found by
> org.ops4j.pax.web.pax-web-runtime [82]
> at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1460)
> at
> org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 37 more
> ERROR: Bundle org.ops4j.pax.web.pax-web-extender-war [88] EventDispatcher:
> Error during dispatch. (java.lang.NoClassDefFoundError:
> org/osgi/service/event/EventAdmin)
> java.lang.NoClassDefFoundError: org/osgi/service/event/EventAdmin
> at
> org.ops4j.pax.web.extender.war.internal.Activator$EventServiceCustomizer.addingService(Activator.java:189)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:932)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:1)
> at
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
> at
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:894)
> at
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)
> at
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)
> at
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4260)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3275)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:320)
> at
> org.apache.felix.eventadmin.impl.Configuration.startOrUpdate(Configuration.java:324)
> at
> org.apache.felix.eventadmin.impl.Configuration.<init>(Configuration.java:142)
> at org.apache.felix.eventadmin.impl.Activator.start(Activator.java:65)
> at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1977)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1895)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:944)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:931)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:479)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:396)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:392)
> at
> org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)
> at
> org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:41)
> at
> org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)
> at
> org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)
> at
> org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)
> at
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> at
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> at org.apache.karaf.shell.console.jline.Console.run(Console.java:174)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: java.lang.ClassNotFoundException:
> org.osgi.service.event.EventAdmin not found by
> org.ops4j.pax.web.pax-web-extender-war [88]
> at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1460)
> at
> org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 37 more
>
>
> I also miss a "camel-leveldb" WIKI page. Couldn't find one...
>
> Best,
> Christian
>
>
> On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
> christian.mueller@gmail.com> wrote:
>
>> After 9 month of development, we have a new minor release candidate
>> apache-camel-2.11.0 ready.
>> It comes with 659 issues resolved: new features, improvements and bug
>> fixes [1]. You can find the release notes here [2].
>>
>> Please find the staging repo here:
>> https://repository.apache.org/content/repositories/orgapachecamel-092/
>>
>> The tarballs are here
>>
>> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>>
>> Tag:
>> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>>
>> Please review, help out with testing and vote to approve this release
>> binary. Please mention what you tested to prevent duplicate work. Your vote
>> counts!
>>
>> [ ] +1 Release the binary as Apache Camel 2.11.0
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Thanks in advance,
>> Christian
>>
>> [1]
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
>> [2]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>>
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Christian Müller <ch...@gmail.com>.
Still testing but want to let you know the installation of the following
features in Karaf 2.3.1 failed for me (I guess the last two are issues in
Karaf/Felix):
camel-jclouds
Error executing command: Could not start bundle
mvn:org.apache.camel/camel-jclouds/2.11.0 in feature(s)
camel-jclouds-2.11.0: Unresolved constraint in bundle
org.apache.camel.camel-jclouds [79]: Unable to resolve 79.0: missing
requirement [79.0] osgi.wiring.package;
(&(osgi.wiring.package=com.google.common.base)(version>=14.0.0)(!(version>=15.0.0)))
camel-leveldb
Error executing command: Could not start bundle
wrap:mvn:org.fusesource.leveldbjni/leveldbjni-all/1.6$Bundle-Version=1.6&Export-Package=*;-noimport:=true;version="1.6"
in feature(s) camel-leveldb-2.11.0: Unresolved constraint in bundle
org.fusesource.leveldbjni.leveldbjni-all [80]: No matching native libraries
found.
camel-mybatis (Karaf hangs - no log entry)
camel-dozer + camel-eventadmin
ERROR: Bundle org.ops4j.pax.web.pax-web-runtime [82] EventDispatcher: Error
during dispatch. (java.lang.NoClassDefFoundError:
org/osgi/service/event/EventAdmin)
java.lang.NoClassDefFoundError: org/osgi/service/event/EventAdmin
at
org.ops4j.pax.web.service.internal.Activator$EventServiceCustomizer.addingService(Activator.java:418)
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:932)
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:1)
at
org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
at
org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:894)
at
org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)
at
org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)
at
org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)
at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4260)
at org.apache.felix.framework.Felix.registerService(Felix.java:3275)
at
org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)
at
org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:320)
at
org.apache.felix.eventadmin.impl.Configuration.startOrUpdate(Configuration.java:324)
at
org.apache.felix.eventadmin.impl.Configuration.<init>(Configuration.java:142)
at org.apache.felix.eventadmin.impl.Activator.start(Activator.java:65)
at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1977)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1895)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:944)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:931)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:479)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:396)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:392)
at
org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)
at
org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:41)
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)
at
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)
at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
at org.apache.karaf.shell.console.jline.Console.run(Console.java:174)
at java.lang.Thread.run(Thread.java:680)
Caused by: java.lang.ClassNotFoundException:
org.osgi.service.event.EventAdmin not found by
org.ops4j.pax.web.pax-web-runtime [82]
at
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1460)
at
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
at
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
... 37 more
ERROR: Bundle org.ops4j.pax.web.pax-web-extender-war [88] EventDispatcher:
Error during dispatch. (java.lang.NoClassDefFoundError:
org/osgi/service/event/EventAdmin)
java.lang.NoClassDefFoundError: org/osgi/service/event/EventAdmin
at
org.ops4j.pax.web.extender.war.internal.Activator$EventServiceCustomizer.addingService(Activator.java:189)
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:932)
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:1)
at
org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
at
org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:894)
at
org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)
at
org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)
at
org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)
at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4260)
at org.apache.felix.framework.Felix.registerService(Felix.java:3275)
at
org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)
at
org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:320)
at
org.apache.felix.eventadmin.impl.Configuration.startOrUpdate(Configuration.java:324)
at
org.apache.felix.eventadmin.impl.Configuration.<init>(Configuration.java:142)
at org.apache.felix.eventadmin.impl.Activator.start(Activator.java:65)
at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1977)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1895)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:944)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:931)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:479)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:396)
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:392)
at
org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)
at
org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:41)
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)
at
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)
at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
at org.apache.karaf.shell.console.jline.Console.run(Console.java:174)
at java.lang.Thread.run(Thread.java:680)
Caused by: java.lang.ClassNotFoundException:
org.osgi.service.event.EventAdmin not found by
org.ops4j.pax.web.pax-web-extender-war [88]
at
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1460)
at
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
at
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
... 37 more
I also miss a "camel-leveldb" WIKI page. Couldn't find one...
Best,
Christian
On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
christian.mueller@gmail.com> wrote:
> After 9 month of development, we have a new minor release candidate
> apache-camel-2.11.0 ready.
> It comes with 659 issues resolved: new features, improvements and bug
> fixes [1]. You can find the release notes here [2].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-092/
>
> The tarballs are here
>
> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>
> Please review, help out with testing and vote to approve this release
> binary. Please mention what you tested to prevent duplicate work. Your vote
> counts!
>
> [ ] +1 Release the binary as Apache Camel 2.11.0
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks in advance,
> Christian
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> [2]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>
Re: [VOTE] Release Apache Camel 2.11.0 (take 3)
Posted by Charles Moulliard <ch...@gmail.com>.
+1 (done tests with new simple language functionalities, ...)
On Thu, Apr 11, 2013 at 12:50 PM, Christian Müller <
christian.mueller@gmail.com> wrote:
> After 9 month of development, we have a new minor release candidate
> apache-camel-2.11.0 ready.
> It comes with 659 issues resolved: new features, improvements and bug fixes
> [1]. You can find the release notes here [2].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-092/
>
> The tarballs are here
>
> https://repository.apache.org/content/repositories/orgapachecamel-092/org/apache/camel/apache-camel/2.11.0/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>
> Please review, help out with testing and vote to approve this release
> binary. Please mention what you tested to prevent duplicate work. Your vote
> counts!
>
> [ ] +1 Release the binary as Apache Camel 2.11.0
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks in advance,
> Christian
>
> [1]
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22
> [2]
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695
>
--
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat)
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com