Camel.2.19.x.notest - Build # 152 - Still Failing
The Apache Jenkins build system has built Camel.2.19.x.notest (build #152) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/152/ to view the results.
Camel.trunk.notest - Build # 3574 - Still Failing
The Apache Jenkins build system has built Camel.trunk.notest (build #3574) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.trunk.notest/3574/ to view the results.
Camel.2.19.x.notest - Build # 151 - Failure
The Apache Jenkins build system has built Camel.2.19.x.notest (build #151) Status: Failure Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/151/ to view the results.
Camel.trunk.notest - Build # 3573 - Still Failing
The Apache Jenkins build system has built Camel.trunk.notest (build #3573) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.trunk.notest/3573/ to view the results.
[GitHub] camel pull request #1924: CAMEL-11695: Add security and advanced properties ...
GitHub user dmvolod opened a pull request: https://github.com/apache/camel/pull/1924 CAMEL-11695: Add security and advanced properties to the camel-grpc component Added following options to the component: 1. Additional channel and server options (message size, max concurrent connections, agent name, etc) 2. Standard security features with TLS/SSL 3. Advanced security with custom JSON Web Token implementation You can merge this pull request into a Git repository by running: $ git pull https://github.com/dmvolod/camel CAMEL-11695 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1924.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1924 commit 9bb1c3393ea7bf5655434349c052c8c835b1aaa0 Author: Dmitry VolodinDate: 2017-08-28T16:54:50Z CAMEL-11695: Add security and advanced properties to the camel-grpc component ---
Camel.2.18.x.notest - Build # 185 - Still Failing
The Apache Jenkins build system has built Camel.2.18.x.notest (build #185) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.2.18.x.notest/185/ to view the results.
Camel.2.18.x.notest - Build # 184 - Still Failing
The Apache Jenkins build system has built Camel.2.18.x.notest (build #184) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.2.18.x.notest/184/ to view the results.
Camel.trunk.notest - Build # 3572 - Still Failing
The Apache Jenkins build system has built Camel.trunk.notest (build #3572) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.trunk.notest/3572/ to view the results.
[GitHub] camel pull request #1923: CAMEL-11383: Replace Jersey JAX-RS client with CXF...
Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/1923 ---
[GitHub] camel pull request #1923: CAMEL-11383: Replace Jersey JAX-RS client with CXF...
GitHub user jamesnetherton opened a pull request: https://github.com/apache/camel/pull/1923 CAMEL-11383: Replace Jersey JAX-RS client with CXF in Bonita component https://issues.apache.org/jira/browse/CAMEL-11383 You can merge this pull request into a Git repository by running: $ git pull https://github.com/jamesnetherton/camel CAMEL-11383 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1923.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1923 commit b94fd971fd9664fa52b5d8ac7acc93bd97ee92fd Author: James NethertonDate: 2017-09-07T09:28:37Z CAMEL-11383: Replace Jersey JAX-RS client with CXF in Bonita component commit bd06490b9d377f828c16247f5552c9ed422e47c0 Author: James Netherton Date: 2017-09-07T09:29:34Z CAMEL-11383: Add Bonita integration test ---
[GitHub] camel pull request #1918: CAMEL-11757: Upgraded CometD library
Github user vrlgohel closed the pull request at: https://github.com/apache/camel/pull/1918 ---
[GitHub] camel pull request #1922: CAMEL-11750: Camel route with multicast (parallel)...
GitHub user leofromgroza opened a pull request: https://github.com/apache/camel/pull/1922 CAMEL-11750: Camel route with multicast (parallel) generate huge CPU ⦠â¦load Fixed issue with huge CPU load: added 1 second delay for a task that is 2nd in the queue order, 2sec for 3rd task, 3sec for 4th taks, etc. That helps to decrease CPU load and does not broke previous logic. You can merge this pull request into a Git repository by running: $ git pull https://github.com/leofromgroza/camel patch-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1922.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1922 commit 089b64ae85d76230d647eb646d806400e1df4b21 Author: leofromgrozaDate: 2017-09-07T08:15:02Z CAMEL-11750: Camel route with multicast (parallel) generate huge CPU load Fixed issue with huge CPU load: added 1 second delay for a task that is 2nd in the queue order, 2sec for 3rd task, 3sec for 4th taks, etc. That helps to decrease CPU load and does not broke previous logic. ---
[GitHub] camel pull request #1920: CAMEL-11759: camel-itest-karaf - CamelNagiosTest f...
Github user tadayosi closed the pull request at: https://github.com/apache/camel/pull/1920 ---
[GitHub] camel pull request #1921: CAMEL-11760: camel-itest-karaf - CamelServicenowTe...
Github user tadayosi closed the pull request at: https://github.com/apache/camel/pull/1921 ---
Re: Re: Apache Camel 2.19.3 Release
Hi Just a heads up that I moved the unresolved 2.19.3 tickets to 2.19.4. On Wed, Sep 6, 2017 at 5:19 PM, Gregor Zurowskiwrote: > Yes, I can cut the 2.19.3 release this weekend. > > When are we ready for 2.20.0? > > Thanks, > Gregor > > > On Wed, Sep 6, 2017 at 5:13 PM, Andrea Cosentino > wrote: >> Gregor, do you think you can take care of this release? >> Thanks >> >> Il mer, 6 set, 2017 alle 15:50, Claus Ibsen ha >> scritto: +1 >> >> I will create a 2.19.4 version so if we wont get time to fix all the >> remainder 2.19.3 tickets we can move them to the next. >> >> On Wed, Sep 6, 2017 at 2:58 PM, Andrea Cosentino >> wrote: >>> Hi all, >>> >>> I guess we can think about releasing a patch release for 2.19.3. From >>> 2.19.2 about one month has passed. I guess we need to release a bit more >>> frequently. >>> >>> So maybe it would be good to release this patch by the end of this month, >>> maybe with 2.20.0 >>> >>> What do you think guys? >>> >>> Thanks. >>> >>> -- >>> Andrea Cosentino >>> -- >>> Apache Camel PMC Member >>> Apache Karaf Committer >>> Apache Servicemix PMC Member >>> Email: ancosen1...@yahoo.com >>> Twitter: @oscerd2 >>> Github: oscerd >> >> >> >> -- >> Claus Ibsen >> - >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
[GitHub] camel pull request #1919: CAMEL-11726: Fixed the Elsql producer inconsistent...
Github user bonbonmark closed the pull request at: https://github.com/apache/camel/pull/1919 ---
Re: Re: CamelBeanValidatorTest is failing
No, it's not related to the Karaf feature. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, September 7, 2017, 4:53:50 AM GMT+2, Tadayoshi Satowrote: Hi Andrea, Yeah, it doesn't reproduce locally in my laptop, either. The last commit that the camel-itest-karaf ran successfully on Jenkins was this on Aug 1: https://github.com/apache/camel/commit/0b243a48aea3f30fba8460c7b26f7b184b3c6456 so it could be that any changes that were committed right after the commit may have caused the itest failures. (It's also possible that any external factors such as changes on the maven central repo that happened right after Aug 1 could have caused it though.) However the original failed build history #2210 is already gone on Jenkins: https://builds.apache.org/job/Camel.trunk.itest.karaf/ so it's hard to detect which one is the culprit. I found this ticket. Was this itest failure the original motivation for the task? https://issues.apache.org/jira/browse/CAMEL-11650 On Thu, Sep 7, 2017 at 10:24 AM, Tadayoshi Sato wrote: > Filed the JIRA: https://issues.apache.org/jira/browse/CAMEL-11758 > I'll look into it. > > On Wed, Sep 6, 2017 at 3:02 PM, Andrea Cosentino > wrote: > >> Tested locally it seems to work. >> >> [org.ops4j.store.intern.TemporaryStore] : Exit store(): >> 8e7251cf3141ec0862eb074f2466f6df6820a6d0 >> [org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : Preparing and >> Installing bundle (from stream ).. >> [org.ops4j.pax.exam.rbc.client.RemoteBundleContextClient] : Packing >> probe into memory for true RMI. Hopefully things will fill in.. >> [org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : Installed bundle >> (from stream) as ID: 80 >> [org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : call >> [[TestAddress:PaxExam-d99f7da4-022e-4e50-8778-4ec519603761 >> root:PaxExam-5408707c-548d-485f-b49e-98d07bdbbdfc]] >> [org.ops4j.pax.exam.karaf.container.internal.KarafTestContainer] : >> Shutting down the test container (Pax Runner) >> [org.ops4j.pax.exam.spi.reactors.ReactorManager] : suite finished >> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.461 >> sec - in org.apache.camel.itest.karaf.CamelBeanValidatorTest >> >> >> >> -- >> Andrea Cosentino >> -- >> Apache Camel PMC Member >> Apache Karaf Committer >> Apache Servicemix PMC Member >> Email: ancosen1...@yahoo.com >> Twitter: @oscerd2 >> Github: oscerd >> >> >> >> >> >> >> >> On Wednesday, September 6, 2017, 6:43:22 AM GMT+2, Tadayoshi Sato < >> sato.tadayo...@gmail.com> wrote: >> >> >> >> >> >> Looks like CamelBeanValidatorTest in camel-itest-karaf is failing: >> >> https://builds.apache.org/job/Camel.trunk.itest.karaf/2397/console >> >> >> Tests in error: >> CamelBeanValidatorTest.test » WrappedTestContainer >> [test(org.apache.camel.ites... >> >> >> Best regards, >> Tadayoshi >> >> >