Rob, just drop it. You know very well James is right. A similar
complaint was made just a few days ago about Fuse's behavior. This is
nothing new, there is a long list of abuses from Fuse over quite a few
years.
James, I would not include RedHat here. RedHat employees are involved in
other AS
James - that's a strong statement. I think the Camel PMC is more diligent than
most in protecting its diversity and marks.
On 1 Feb 2013, at 14:44, James Carman wrote:
> I'm not a Camel committer or PMC member, but I *am* an ASF member and I find
> it troubling how much Fuse/RedHat uses these
I'm not a Camel committer or PMC member, but I *am* an ASF member and I find it
troubling how much Fuse/RedHat uses these lists to promote themselves (like a
picture of a camel wearing a red hat). Hopefully they don't use their
influence in any other inappropriate ways.
On Feb 1, 2013, at 9:09
I will try using Camel 2.11-SNAPSHOT.
I am more worry about maxTotalConnections connection. If i have 100 routes
and each create 2 connections. we reach the maxTotalConnections. Since we
are not setting connTTL( connection lifetime, <=0 implies "infinity"), so
connection is not remove from connec
Yeah - probably best Charles doesn't use his profile picture for the Apache
Camel group - the Apache Camel logo should be OK.
On 1 Feb 2013, at 14:23, Daniel Kulp wrote:
>
> On Feb 1, 2013, at 9:09 AM, James Carman wrote:
>
>> A picture of a camel with a red hat on with the words "Apache Cam
Please don't use this Google Plus community for project-related discussions
(design discussions, etc.), though. That needs to be on the mailing lists in
order to keep the community in-the-loop.
On Feb 1, 2013, at 8:59 AM, Charles Moulliard wrote:
> Hi,
>
> For our supporters/fans and peopl
On Feb 1, 2013, at 9:09 AM, James Carman wrote:
> A picture of a camel with a red hat on with the words "Apache Camel."
> Really?
Agreed. That NEEDS to change.
Dan
>
> On Feb 1, 2013, at 8:59 AM, Charles Moulliard wrote:
>
>> Hi,
>>
>> For our supporters/fans and people who bel
+1
On 1 Feb 2013, at 14:02, James Carman wrote:
> Please don't use this Google Plus community for project-related discussions
> (design discussions, etc.), though. That needs to be on the mailing lists in
> order to keep the community in-the-loop.
>
>
> On Feb 1, 2013, at 8:59 AM, Charles Mo
Am 01.02.13 10:31 schrieb "Claus Ibsen" unter :
>On Fri, Feb 1, 2013 at 9:58 AM, Claus Ibsen wrote:
>> On Fri, Feb 1, 2013 at 9:40 AM, Babak Vahdat
>> wrote:
>>>
>>>
>>> Am 01.02.13 08:44 schrieb "Claus Ibsen" unter :
>>>
Hi
We released 2.10.3 in the middle of December 2012.
On Fri, Feb 1, 2013 at 9:58 AM, Claus Ibsen wrote:
> On Fri, Feb 1, 2013 at 9:40 AM, Babak Vahdat
> wrote:
>>
>>
>> Am 01.02.13 08:44 schrieb "Claus Ibsen" unter :
>>
>>>Hi
>>>
>>>We released 2.10.3 in the middle of December 2012.
>>>
>>>Since this release we have resolved 78 tickets in JIRA.
>>>
On Fri, Feb 1, 2013 at 9:40 AM, Babak Vahdat
wrote:
>
>
> Am 01.02.13 08:44 schrieb "Claus Ibsen" unter :
>
>>Hi
>>
>>We released 2.10.3 in the middle of December 2012.
>>
>>Since this release we have resolved 78 tickets in JIRA.
>>https://issues.apache.org/jira/browse/CAMEL/fixforversion/12323558
The default max connection per route is 20 , if we don't set it the http client
will set it to be 2.
I'm not sure what's kind of use case you need more than 20 connections at the
same time.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | htt
Am 01.02.13 08:44 schrieb "Claus Ibsen" unter :
>Hi
>
>We released 2.10.3 in the middle of December 2012.
>
>Since this release we have resolved 78 tickets in JIRA.
>https://issues.apache.org/jira/browse/CAMEL/fixforversion/12323558#selecte
>dTab=com.atlassian.jira.plugin.system.project%3Aversio
+1.
this also fixes the validator regression.
2013/2/1 Claus Ibsen :
> Hi
>
> We released 2.10.3 in the middle of December 2012.
>
> Since this release we have resolved 78 tickets in JIRA.
> https://issues.apache.org/jira/browse/CAMEL/fixforversion/12323558#selectedTab=com.atlassian.jira.plugin.s
+1 for retiring the Camel 2.9.x branch.
As CXF has a new release, it could be good we do an new release of the Camel
2.10.4.
--
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://wil
Just a heads up. We upgrade the http client to 4.2.x in Camel 2.11.x,
We are using the PoolingClientConnectionManager instead, as it has much better
default options setting.
Can you try to run you camel route with latest Camel 2.11-SNAPSHOT to see if
the issue is till there?
BTW, I will try to
16 matches
Mail list logo
