camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Cosentino <ancosen1...@yahoo.com.INVALID>
Subject Re: [camel 2.17] limited performance (not more than 20 req/s)
Date Fri, 15 Jul 2016 11:08:42 GMT
It should be included in 2.17.2
 --
Andrea Cosentino 
----------------------------------
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, July 15, 2016 1:06 PM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
Hi

I found the ticket
https://issues.apache.org/jira/browse/CAMEL-10043

On Fri, Jul 15, 2016 at 1:04 PM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
> Hi
>
> Ah yeah there was a bug in camel-jaxb that could impact the
> performance. Try with 2.17.2 or the 2.17.3-SNAPSHOT as I cannot
> remember if the fix made it into the 2.17.2 release.
>
>
> On Fri, Jul 15, 2016 at 12:56 PM, Tarek Jarraya <tarekjarraya@gmail.com> wrote:
>> More info:
>>
>> I saw this log appearing many times:
>> [http-bio-8080-exec-373] DEBUG org.apache.camel.util.ObjectHelper: Cannot
>> find class: java.lang.ObjectFactory
>>
>> The log disappears with 2.16.1.
>>
>> The same log saw by others:
>> http://camel.465427.n5.nabble.com/ClassNotFoundException-ObjectFactory-td5782443.html
>>
>> Similar Performance topic (they use rabbitmq client):
>> https://issues.apache.org/jira/browse/CAMEL-9786
>>
>> Thanks,
>> Tarek
>>
>>
>> On Fri, Jul 15, 2016 at 12:27 PM, Tarek Jarraya <tarekjarraya@gmail.com>
>> wrote:
>>
>>> Hi Claus,
>>>
>>> Sorry for late reply.
>>>
>>> When I downgraded to camel 2.16.1/3 the performance issue disappears.
>>>
>>> Regards,
>>> Tarek
>>>
>>> Le mardi 14 juin 2016, Tarek Jarraya <tarekjarraya@gmail.com> a écrit
:
>>>
>>>> Hi Both,
>>>>
>>>> Thanks for your interest.
>>>>
>>>> @Claus,
>>>>
>>>> this toD generates only one endpoint. I try to change it to "to" format
>>>> and let you know.
>>>>
>>>> One more thing, our exposed endpoint is using camel servlet.
>>>>
>>>>         <endpoint id="esb-pricing-v1.1-endpoint"
>>>> uri="servlet://offer/pricing/v1.1">
>>>>             <property key="servletName" value="CamelServlet" />
>>>>             <property key="httpMethodRestrict" value="POST" />
>>>>             <property key="matchOnUriPrefix" value="true" />
>>>>         </endpoint>
>>>>
>>>> I saw in the http4 page that if we want to expose an endpoint and attach
>>>> it to route, we use camel-jetty.
>>>> Should we change our exposition?
>>>>
>>>> Some people said that we expose mostly web services with CXF.
>>>> But in that case, we have to implement a class for each endpoint.
>>>> However, with servlet we don't do it, so no more java code.
>>>>
>>>> Any recommendation if the servlet exposition is not adapted for
>>>> concurrent context?
>>>>
>>>> Regards,
>>>> Tarek
>>>>
>>>> On Tue, Jun 14, 2016 at 5:20 PM, Claus Ibsen <claus.ibsen@gmail.com>
>>>> wrote:
>>>>
>>>>> On Tue, Jun 14, 2016 at 4:38 PM, owain <owain@integration.technology>
>>>>> wrote:
>>>>> > Is there a typo toD in here?
>>>>> >
>>>>> > <toD
>>>>> >
>>>>> uri="{{pricing-wsrest-endpoint}}&bridgeEndpoint=true&throwExceptionOnFailure=true"
>>>>> > />
>>>>> >
>>>>>
>>>>> toD is a dynamic to.
>>>>>
>>>>> How many unique endpoints does {{pricing-wsrest-endpoint}} generate in
>>>>> your test?
>>>>>
>>>>> If the dynamic part is the context-path and/or uri parameters its
>>>>> better to use <to> and then use a header (HTTP_PART / HTTP_QUERY
etc)
>>>>> to provide the dynamic context-path / uri parameters. Then you reuse
>>>>> same endpoint/producers.
>>>>> http://camel.apache.org/http4
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > View this message in context:
>>>>> http://camel.465427.n5.nabble.com/camel-2-17-limited-performance-not-more-than-20-req-s-tp5783980p5784041.html
>>>>> > Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Mime
View raw message