activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: Pooled connection factory does not work
Date Fri, 08 Apr 2016 04:00:08 GMT
Although I've only used the string-based syntax (e.g.
from("jms:MyQueue?concurrentConsumers=10") ) to specify the number of
concurrent consumers when I've used Camel, I assumed that <property
name="concurrentConsumers" value="10"/> specified in the XML DSL would have
the same effect.

On Thu, Apr 7, 2016 at 9:21 AM, Quinn Stevenson <quinn@pronoia-solutions.com
> wrote:

> Looking at the Camel route, I only see once consumer on the queue - am I
> missing something?
>
>
>
> > On Apr 7, 2016, at 4:17 AM, Michele <michele.mazzilli@finconsgroup.com>
> wrote:
> >
> > Hi Tim,
> >
> > sorry, but I'm a bit confused.
> >
> > My use case is to create a Camel Route that it is capable:
> >
> > 1. Read large number of lines in File (approx. 50000)
> > 2. Split, Process and store every line in AMQ (Simple hash map)
> > 3. Retrieve message from queue and invoke with POST a Rest Service that
> is
> > bottleneck (I need to process messages stored in AMQ slowly in order to
> > don't overload a Rest Service Interface).
> >
> > <route id="FileReader_Route">
> >    <from uri="file:incoming?....." />
> >     <split streaming="true" parallelProcessing="true">
> >           <tokenize token="\n" />
> >           <unmarshal ref="IncomingCSVFileDataFormat" />
> >           <process ref="DataProcessor" />
> >           <marshal ref="Gson" />
> >           <to uri="activemq:queue:incomingTickets" />
> >     </split>
> > </route>
> >
> > <route id="ProcessTicket_Route">
> >     <from
> > uri="activemq:queue:incomingTickets?destination.consumer.prefetchSize=0"
> />
> >     <throttle timePeriodMillis="10000" asyncDelayed="true">
> >          <constant>5</constant>
> >           <to
> > uri="jetty:
> http://host/rs/v1.0/ticket?jettyHttpBindingRef=CustomJettyHttpBinding"
> > />
> >     </throttle>
> > </route>
> >
> > I don't understand well how Producer and Consumer work on the broker. My
> > idea is that Producer pust message in Queue and Consumer pop message from
> > queue to dispatch. Is it right?
> > So, I configured  a pooled connection factory to handle efficiently
> > connections, sessions, producers and consumers.
> > As you can see bt attached picture  pooled-connection.png
> > <
> http://activemq.2283324.n4.nabble.com/file/n4710461/pooled-connection.png>
> > , why is there only one consumer that works on Queue?
> >
> > I hope i was clear.
> >
> > Thanks a lot again
> >
> > Kind greetings
> >
> > Michele
> >
> >
> >
> > --
> > View this message in context:
> http://activemq.2283324.n4.nabble.com/Pooled-connection-factory-does-not-work-tp4710421p4710461.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message