It is related to the CPUs on the machine:
minimum maxThreads = 1 + Connectors*(1 + Cores/16 + Cores).
So the make the code works on the CI machine we need to use a bigger maxThreads
parameter.
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committe
Sure.
I'm looking at it :-)
When I tested locally the number of required threads was 11 but I see 15 is
needed on the CI Server.
I'll investigate a bit.
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: anc
Hi
Andrea great work on migrating to jetty9.
I wonder if there is a way to configure less threads the tests are
using as the CI server fails. You can see the tests errors from this
link
https://builds.apache.org/job/Camel.trunk.fulltest.java8/746/#showFailuresLink
java.lang.IllegalStateException
The Apache Jenkins build system has built Camel.trunk.notest (build #2728)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2728/
to view the results.
Hello,
I had some troubles recently making camel-hazelcast working on karaf
because of a problem very similar to
https://github.com/hazelcast/hazelcast/issues/2233.
It appears that the root cause is the package javax.scripting exported
by bot the System Bundle as well as
org.apache.servicemix.spe
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/953
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Hi all,
Actually you'll find in some components the directory src/main/docs.
Each component should have his own .adoc in that directory.
Actually we have this project from Hiram Chirino
https://github.com/chirino/cxf-web/tree/master
we are using it to migrate the html documentation from conflu
Arnaud, Charles,
here is what Claus sent to me & the list:
>>>
Hi Thomas
Just a heads up that if you find spelling mistakes and other
corrections to the Camel components, then correcting in wiki becomes
obsolete.
We keep the documentation in the source code in the javadoc for the
setter method
On Thu, Apr 21, 2016 at 11:00 AM, Jan Matèrne (jhm) wrote:
>> > I like the idea of adding the implementation in such a way.
>> > Does the component just implement that one EIP?
>> > Otherwise: which component is used when multiple implementations are
>> on the classpath?
>> >
>>
>> Yes only that E
> > I like the idea of adding the implementation in such a way.
> > Does the component just implement that one EIP?
> > Otherwise: which component is used when multiple implementations are
> on the classpath?
> >
>
> Yes only that EIP. There is a marker file in the camel-hystrix that
> tells Camel
GitHub user frankfarrell opened a pull request:
https://github.com/apache/camel/pull/953
AWS Kinesis Consumer support for Sequence Number and Shard Id
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/frankfarrell/camel master
Alt
Github user frankfarrell closed the pull request at:
https://github.com/apache/camel/pull/952
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Hi,
+1.
I've made a pull request for async with servlet (see
https://github.com/apache/camel/pull/949) and I don't know how do I have to
do to update the documentation as the asciidoc doesn't exist yet. It's not
clear to me too.
Regards
On Thu, Apr 21, 2016 at 7:50 AM Charles Moulliard wrote:
13 matches
Mail list logo
