[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Concurrent consumers from SEDA to CXF


Can you try to explain the numbers a bit more, maybe with some example numbers?

For http connections etc, then CXF has its own set of limitations,
specially if you call the same remote server via the same client, eg
same cxf-endpoint in Camel.
That may have limitations on number of concurrent requests, that can
be lower. So try to look at the CXF documentation about this.

On Wed, Jul 25, 2018 at 9:16 PM, Mirek Borsky <geraltofr@xxxxxxxx> wrote:
> Greetings,
> I have encountered a strange behavior with a simple camel route and I would
> like to ask for help of more experienced users. First, let me quickly show
> the route:
> The relevant part:
>             <from uri="" />
>             <to uri="MonitoringService" />
> The whole blueprint:
> <?xml version="1.0" encoding="UTF-8"?>
> <osgi:blueprint xsi:schemaLocation="
> 1.0.0"; xmlns:xsi=
> ""; xmlns:cxf="http://camel.apache.
> org/schema/blueprint/cxf" xmlns:osgi="
> 1.0.0">
>     <camelContext id="TestSAMLoggerSeda-ctx" xmlns="
> schema/blueprint" streamCache="true">
>         <route>
>             <from uri="" />
>             <to uri="MonitoringService" />
>         </route>
>     </camelContext>
>     <cxf:cxfEndpoint xmlns:tns="
> MonitoringService/v1" id="MonitoringService" address="http://localhost:8042/
> MonitoringMock" serviceName="tns:MonitoringWebServiceService" endpointName=
> "tns:MonitoringWebServicePort" wsdlURL="deploy/MonitoringService.wsdl">
>         <cxf:properties>
>             <osgi:entry key="dataFormat" value="PAYLOAD"/>
>         </cxf:properties>
>     </cxf:cxfEndpoint>
> </osgi:blueprint>
> Now the expected behavior:
> What I want to achieve is a queue from which 10 parallel threads are
> processing messages, calling the cxf endpoint. The cxf endpoint takes
> several seconds to answer, so I am expecting the speed of processing
> somewhere about 1-2 messages per second.
> Observed behavior:
> Using JMX I can see X+N inflight messages in the route, where X is the
> maximum number of concurrent http connections to the cxf endpoint and N is
> the number of concurrent users. For some reason, the workers that are
> waiting for the cxf endpoint to answer are not counted against the
> concurrentConsumers limit. Only the workers that are waiting for the
> connection to be established are counted against the limit of
> concurrentConsumers.
> Questions:
> What is the correct behavior for the route?
> If my configuration is incorrect, how can I achieve my target behavior?
> The camel version used is 2.20.
> If someone would be able to help me, and explain what I did wrong, I would
> very much appreciate it.
> thank you for help
> kind regards
> Miroslav Borský

Claus Ibsen
----------------- @davsclaus
Camel in Action 2: