You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by dgomesbr <di...@bemobi.com.br> on 2015/03/04 18:09:17 UTC
Diff between configuring maxConcurrentConsumers in JMSComponent,
Route URI or per JMSEndpoint
Hey there, I'm currently puzzled by how maxConcurrentConsumers set in
different points may have different behaviors (or not, I might be doing
something wrong).According the documentation:
http://camel.apache.org/jms.html*You can configure this option in one of the
following ways:On the JmsComponent,On the endpoint URI or,By invoking
setConcurrentConsumers() directly on the JmsEndpoint.*Whenever I do it via
DSL:https://gist.github.com/dgomesbr/17f029c9a649ce6656f4The activemq queue,
shows only the max consumers set for the endpoint correctly, in this case
15.but when I explicitly set the maxConsumers as the parameter on the route
"?MaxConcurre...", the maxConcurrent consumers is now the sum of the
machines where the camelcontext is deployed, in this example 3 x 15 =
45.Could someone elaborate on that or point me where the implementation
varies per local where the configuration is made?Thanks!
--
View this message in context: http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Diff between configuring maxConcurrentConsumers in
JMSComponent, Route URI or per JMSEndpoint
Posted by yogu13 <yo...@gmail.com>.
Hello,
To the best of my knowledge
1. activemq connection is first established and then consumers / sessions
are created based on maxConcurrentConsumers property.
2. The value of this property when overwritten by the endpoint uri takes in
the effect as its more for the container and not a property of the queue
(activemq in this case).
3. Camel internally uses spring jms for this and trickles down the property
to DefaultMessageListenerContainer
<http://docs.spring.io/spring/docs/3.0.x/javadoc-api/org/springframework/jms/listener/DefaultMessageListenerContainer.html>
Hope this helps!
Regards,
-Yogesh
--
View this message in context: http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763852.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Diff between configuring maxConcurrentConsumers in
JMSComponent, Route URI or per JMSEndpoint
Posted by dgomesbr <di...@bemobi.com.br>.
Yogu,
The configuration given is for the activemq component, which configures the
connection with the broker. The routes are configured to overwrite this
value whenever needed.
The problem with that is that the amq component configuration is valid for
all server with that deploy, but whenever I configure the property on the
URI it'll be cumulative.
Eg.:
- configured activemq component puts all queues with 15
maxConcurrentConsumers
- endpoint URI configured with maxConcurrentConsumers 1 within 3 servers
put maxConcurrentConsumers by 3 instead of 1
I think that behavior is correct although strange, since no server knows
each other they all connect to activemq and register themselves with 1
maxConcurrentConsumers, but should they get the maxConcurrentConsumers or
check it on the route if it exists on the Activemq server?
Scenario
- Server 1 creates activemq with maxConcurrentConsumers set to 15
- Server 1 connects to activemq
- Server 1 create an route with endpointURI configured
with maxConcurrentConsumers set to 1
- ActiveMQ Acks that and creates a queue with maxConcurrentConsumers set
to 1
- Server 2 creates activemq with maxConcurrentConsumers set to 15
- Server 2 connects to activemq
- Server 2 create an route with endpointURI configured
with maxConcurrentConsumers set to 1
- ActiveMQ Acks that and ?
Right now I don't know if this is a desired behavior or not and that is
puzzling me.
On Mar 6, 2015 11:12 AM, "yogu13 [via Camel]" <
ml-node+s465427n5763739h81@n5.nabble.com> wrote:
> Apologies ..l i m confused where does your endpoint uri fit into all this
> ? is it a different project ? if yes can you let us know the configuration
> / route for the same ?
>
> Regards,
> -Yogesh
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763739.html
> To unsubscribe from Diff between configuring maxConcurrentConsumers in
> JMSComponent, Route URI or per JMSEndpoint, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5763599&code=ZGllZ28ubWFnYWxoYWVzQGJlbW9iaS5jb20uYnJ8NTc2MzU5OXwxNjY4NjQxNjYy>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763791.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Diff between configuring maxConcurrentConsumers in
JMSComponent, Route URI or per JMSEndpoint
Posted by yogu13 <yo...@gmail.com>.
Apologies ..l i m confused where does your endpoint uri fit into all this ?
is it a different project ? if yes can you let us know the configuration /
route for the same ?
Regards,
-Yogesh
--
View this message in context: http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763739.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Diff between configuring maxConcurrentConsumers in JMSComponent,
Route URI or per JMSEndpoint
Posted by Diego Magalhaes <di...@bemobi.com.br>.
Sure,
@Configuration
public class AppCommonsActiveMQContext
{
private static final String BROKER_URL = "nio://
activemq01.bemobi.com.br:61616?keepAlive=true&jms.prefetchPolicy.queuePrefetch=10
";
@Bean
public PooledConnectionFactory pooledConnectionFactory()
{
PooledConnectionFactory factory = new
PooledConnectionFactory(BROKER_URL);
factory.setMaxConnections(100);
factory.setMaximumActiveSessionPerConnection(250);
return factory;
}
@Bean
public JmsConfiguration jmsConfig(PooledConnectionFactory
pooledConnectionFactory)
{
JmsConfiguration config = new
JmsConfiguration(pooledConnectionFactory);
config.setTransacted(false);
* config.setConcurrentConsumers(1);*
* config.setMaxConcurrentConsumers(15);*
config.setDisableReplyTo(true);
config.setPreserveMessageQos(true);
return config;
}
@Bean
@Scope("singleton")
public ActiveMQComponent activemq(JmsConfiguration jmsConfiguration)
{
* ActiveMQComponent component = new ActiveMQComponent();*
* component.setConfiguration(jmsConfiguration);*
* return component;*
}
}
Atenciosamente,
*Diego Magalhães*
Gerencia de Desenvolvimento
Diretoria de tecnologia da Informação
[image: email_assinatura.jpg]
+55 (21) 3529-9019
*www.bemobi.com.br <http://www.bemobi.com.br/>**þ*Antes de imprimir, pense
em sua responsabilidade e compromisso com o Meio Ambiente.
*O conteúdo desta mensagem é confidencial e pode ser privilegiado. *
*É vedada a sua cópia ou divulgação.The contents of this message are
confidential and may be privileged. Copying or disclosing is prohibited.*
On Fri, Mar 6, 2015 at 8:10 AM, yogu13 <yo...@gmail.com> wrote:
> this looks good ...
>
> can you also share the activemq bean configuration ?
>
> Regards,
> -Yogesh
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763732.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: Diff between configuring maxConcurrentConsumers in
JMSComponent, Route URI or per JMSEndpoint
Posted by yogu13 <yo...@gmail.com>.
this looks good ...
can you also share the activemq bean configuration ?
Regards,
-Yogesh
--
View this message in context: http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763732.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Diff between configuring maxConcurrentConsumers in
JMSComponent, Route URI or per JMSEndpoint
Posted by dgomesbr <di...@bemobi.com.br>.
Here you go Yogu13,
activemq://ctpubnews-dsjdbc-dllocalsms.DESTINATION?maxConcurrentConsumers=1
With that set, I have the queue created on activeMQ with 3 consumers (cause
we have three servers)
Atenciosamente,
*Diego Magalhães*
Gerencia de Desenvolvimento
Diretoria de tecnologia da Informação
[image: email_assinatura.jpg]
+55 (21) 3529-9019
*www.bemobi.com.br <http://www.bemobi.com.br/>**þ*Antes de imprimir, pense
em sua responsabilidade e compromisso com o Meio Ambiente.
*O conteúdo desta mensagem é confidencial e pode ser privilegiado. *
*É vedada a sua cópia ou divulgação.The contents of this message are
confidential and may be privileged. Copying or disclosing is prohibited.*
On Thu, Mar 5, 2015 at 8:04 AM, yogu13 [via Camel] <
ml-node+s465427n5763656h8@n5.nabble.com> wrote:
> can you show us the route where you have set the max concurrent consumer
> option ?
>
> Regards,
> -Yogesh
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763656.html
> To unsubscribe from Diff between configuring maxConcurrentConsumers in
> JMSComponent, Route URI or per JMSEndpoint, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5763599&code=ZGllZ28ubWFnYWxoYWVzQGJlbW9iaS5jb20uYnJ8NTc2MzU5OXwxNjY4NjQxNjYy>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
image001.gif (2K) <http://camel.465427.n5.nabble.com/attachment/5763677/0/image001.gif>
--
View this message in context: http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763677.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Diff between configuring maxConcurrentConsumers in
JMSComponent, Route URI or per JMSEndpoint
Posted by yogu13 <yo...@gmail.com>.
can you show us the route where you have set the max concurrent consumer
option ?
Regards,
-Yogesh
--
View this message in context: http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763656.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Diff between configuring maxConcurrentConsumers in JMSComponent,
Route URI or per JMSEndpoint
Posted by Diego Magalhaes <di...@bemobi.com.br>.
A view of the problem of concept understanding can be seen here:
http://imgur.com/LUgyeZc
Atenciosamente,
*Diego Magalhães*
Gerencia de Desenvolvimento
Diretoria de tecnologia da Informação
[image: email_assinatura.jpg]
+55 (21) 3529-9019
*www.bemobi.com.br <http://www.bemobi.com.br/>**þ*Antes de imprimir, pense
em sua responsabilidade e compromisso com o Meio Ambiente.
*O conteúdo desta mensagem é confidencial e pode ser privilegiado. *
*É vedada a sua cópia ou divulgação.The contents of this message are
confidential and may be privileged. Copying or disclosing is prohibited.*
On Wed, Mar 4, 2015 at 3:27 PM, dgomesbr <di...@bemobi.com.br>
wrote:
> That's is the situation.
> On Mar 4, 2015 3:25 PM, "Thiago Kronig [via Camel]" <
> ml-node+s465427n5763601h3@n5.nabble.com> wrote:
>
> > Diego,
> > You have three JVM instances running each 15 consumers?
> > Your BROKER_URL points to a fourth JVM, running only ActiveMQ Broker?
> >
> > On Wed, Mar 4, 2015 at 2:15 PM Diego Magalhaes <
> > [hidden email] <http:///user/SendEmail.jtp?type=node&node=5763601&i=0>>
> > wrote:
> >
> > > Hmmm... the message went all broken.
> > >
> > >
> > > Hey there,
> > >
> > > I'm currently puzzled by how maxConcurrentConsumers set in
> different
> > > points may have different behaviors (or not, I might be doing something
> > > wrong).
> > >
> > >
> > > According the documentation: http://camel.apache.org/jms.html
> > >
> > >
> > >
> > > *You can configure this option in one of the following ways: On the
> > > JmsComponent, On the endpoint URI or, By invoking
> > setConcurrentConsumers()
> > > directly on the JmsEndpoint.*
> > >
> > > Whenever I do it via DSL:
> > > https://gist.github.com/dgomesbr/17f029c9a649ce6656f4
> > >
> > > The activemq queue, shows only the max consumers set for the endpoint
> > > correctly, in this case 15.
> > >
> > > but when I explicitly set the maxConsumers as the parameter on the
> route
> > > "?MaxConcurre...", the maxConcurrent consumers is now the sum of the
> > > machines where the camelcontext is deployed, in this example 3 x 15 =
> > 45.
> > >
> > > Could someone elaborate on that or point me where the implementation
> > > varies per local where the configuration is made?
> > >
> > >
> > > Thanks!
> > >
> > >
> > >
> > > Atenciosamente,
> > >
> > > *Diego Magalhães*
> > > Gerencia de Desenvolvimento
> > > Diretoria de tecnologia da Informação
> > > [image: email_assinatura.jpg]
> > > +55 (21) 3529-9019
> > >
> > >
> > > *www.bemobi.com.br <http://www.bemobi.com.br/>**þ*Antes de imprimir,
> > > pense em sua responsabilidade e compromisso com o Meio Ambiente.
> > > *O conteúdo desta mensagem é confidencial e pode ser privilegiado. *
> > > *É vedada a sua cópia ou divulgação.The contents of this message are
> > > confidential and may be privileged. Copying or disclosing is
> > prohibited.*
> > >
> > > On Wed, Mar 4, 2015 at 2:09 PM, dgomesbr <[hidden email]
> > <http:///user/SendEmail.jtp?type=node&node=5763601&i=1>>
> > > wrote:
> > >
> > >> Hey there, I'm currently puzzled by how maxConcurrentConsumers set
> > in
> > >> different points may have different behaviors (or not, I might be
> doing
> > >> something wrong).According the documentation:
> > >> http://camel.apache.org/jms.html*You can configure this option in one
> > of
> > >> the
> > >> following ways:On the JmsComponent,On the endpoint URI or,By invoking
> > >> setConcurrentConsumers() directly on the JmsEndpoint.*Whenever I do it
> > via
> > >> DSL:https://gist.github.com/dgomesbr/17f029c9a649ce6656f4The activemq
> > >> queue,
> > >> shows only the max consumers set for the endpoint correctly, in this
> > case
> > >> 15.but when I explicitly set the maxConsumers as the parameter on the
> > >> route
> > >> "?MaxConcurre...", the maxConcurrent consumers is now the sum of the
> > >> machines where the camelcontext is deployed, in this example 3 x 15 =
> > >> 45.Could someone elaborate on that or point me where the
> implementation
> > >> varies per local where the configuration is made?Thanks!
> > >>
> > >>
> > >>
> > >> --
> > >> View this message in context:
> > >>
> >
> http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599.html
> > >> Sent from the Camel - Users mailing list archive at Nabble.com.
> > >
> > >
> > >
> >
> >
> > ------------------------------
> > If you reply to this email, your message will be added to the discussion
> > below:
> >
> >
> http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763601.html
> > To unsubscribe from Diff between configuring maxConcurrentConsumers in
> > JMSComponent, Route URI or per JMSEndpoint, click here
> > <
> http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5763599&code=ZGllZ28ubWFnYWxoYWVzQGJlbW9iaS5jb20uYnJ8NTc2MzU5OXwxNjY4NjQxNjYy
> >
> > .
> > NAML
> > <
> http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763602.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: Diff between configuring maxConcurrentConsumers in
JMSComponent, Route URI or per JMSEndpoint
Posted by dgomesbr <di...@bemobi.com.br>.
That's is the situation.
On Mar 4, 2015 3:25 PM, "Thiago Kronig [via Camel]" <
ml-node+s465427n5763601h3@n5.nabble.com> wrote:
> Diego,
> You have three JVM instances running each 15 consumers?
> Your BROKER_URL points to a fourth JVM, running only ActiveMQ Broker?
>
> On Wed, Mar 4, 2015 at 2:15 PM Diego Magalhaes <
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=5763601&i=0>>
> wrote:
>
> > Hmmm... the message went all broken.
> >
> >
> > Hey there,
> >
> > I'm currently puzzled by how maxConcurrentConsumers set in different
> > points may have different behaviors (or not, I might be doing something
> > wrong).
> >
> >
> > According the documentation: http://camel.apache.org/jms.html
> >
> >
> >
> > *You can configure this option in one of the following ways: On the
> > JmsComponent, On the endpoint URI or, By invoking
> setConcurrentConsumers()
> > directly on the JmsEndpoint.*
> >
> > Whenever I do it via DSL:
> > https://gist.github.com/dgomesbr/17f029c9a649ce6656f4
> >
> > The activemq queue, shows only the max consumers set for the endpoint
> > correctly, in this case 15.
> >
> > but when I explicitly set the maxConsumers as the parameter on the route
> > "?MaxConcurre...", the maxConcurrent consumers is now the sum of the
> > machines where the camelcontext is deployed, in this example 3 x 15 =
> 45.
> >
> > Could someone elaborate on that or point me where the implementation
> > varies per local where the configuration is made?
> >
> >
> > Thanks!
> >
> >
> >
> > Atenciosamente,
> >
> > *Diego Magalhães*
> > Gerencia de Desenvolvimento
> > Diretoria de tecnologia da Informação
> > [image: email_assinatura.jpg]
> > +55 (21) 3529-9019
> >
> >
> > *www.bemobi.com.br <http://www.bemobi.com.br/>**þ*Antes de imprimir,
> > pense em sua responsabilidade e compromisso com o Meio Ambiente.
> > *O conteúdo desta mensagem é confidencial e pode ser privilegiado. *
> > *É vedada a sua cópia ou divulgação.The contents of this message are
> > confidential and may be privileged. Copying or disclosing is
> prohibited.*
> >
> > On Wed, Mar 4, 2015 at 2:09 PM, dgomesbr <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=5763601&i=1>>
> > wrote:
> >
> >> Hey there, I'm currently puzzled by how maxConcurrentConsumers set
> in
> >> different points may have different behaviors (or not, I might be doing
> >> something wrong).According the documentation:
> >> http://camel.apache.org/jms.html*You can configure this option in one
> of
> >> the
> >> following ways:On the JmsComponent,On the endpoint URI or,By invoking
> >> setConcurrentConsumers() directly on the JmsEndpoint.*Whenever I do it
> via
> >> DSL:https://gist.github.com/dgomesbr/17f029c9a649ce6656f4The activemq
> >> queue,
> >> shows only the max consumers set for the endpoint correctly, in this
> case
> >> 15.but when I explicitly set the maxConsumers as the parameter on the
> >> route
> >> "?MaxConcurre...", the maxConcurrent consumers is now the sum of the
> >> machines where the camelcontext is deployed, in this example 3 x 15 =
> >> 45.Could someone elaborate on that or point me where the implementation
> >> varies per local where the configuration is made?Thanks!
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599.html
> >> Sent from the Camel - Users mailing list archive at Nabble.com.
> >
> >
> >
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763601.html
> To unsubscribe from Diff between configuring maxConcurrentConsumers in
> JMSComponent, Route URI or per JMSEndpoint, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5763599&code=ZGllZ28ubWFnYWxoYWVzQGJlbW9iaS5jb20uYnJ8NTc2MzU5OXwxNjY4NjQxNjYy>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599p5763602.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Diff between configuring maxConcurrentConsumers in JMSComponent,
Route URI or per JMSEndpoint
Posted by Thiago Kronig <th...@gmail.com>.
Diego,
You have three JVM instances running each 15 consumers?
Your BROKER_URL points to a fourth JVM, running only ActiveMQ Broker?
On Wed, Mar 4, 2015 at 2:15 PM Diego Magalhaes <
diego.magalhaes@bemobi.com.br> wrote:
> Hmmm... the message went all broken.
>
>
> Hey there,
>
> I'm currently puzzled by how maxConcurrentConsumers set in different
> points may have different behaviors (or not, I might be doing something
> wrong).
>
>
> According the documentation: http://camel.apache.org/jms.html
>
>
>
> *You can configure this option in one of the following ways: On the
> JmsComponent, On the endpoint URI or, By invoking setConcurrentConsumers()
> directly on the JmsEndpoint.*
>
> Whenever I do it via DSL:
> https://gist.github.com/dgomesbr/17f029c9a649ce6656f4
>
> The activemq queue, shows only the max consumers set for the endpoint
> correctly, in this case 15.
>
> but when I explicitly set the maxConsumers as the parameter on the route
> "?MaxConcurre...", the maxConcurrent consumers is now the sum of the
> machines where the camelcontext is deployed, in this example 3 x 15 = 45.
>
> Could someone elaborate on that or point me where the implementation
> varies per local where the configuration is made?
>
>
> Thanks!
>
>
>
> Atenciosamente,
>
> *Diego Magalhães*
> Gerencia de Desenvolvimento
> Diretoria de tecnologia da Informação
> [image: email_assinatura.jpg]
> +55 (21) 3529-9019
>
>
> *www.bemobi.com.br <http://www.bemobi.com.br/>**þ*Antes de imprimir,
> pense em sua responsabilidade e compromisso com o Meio Ambiente.
> *O conteúdo desta mensagem é confidencial e pode ser privilegiado. *
> *É vedada a sua cópia ou divulgação.The contents of this message are
> confidential and may be privileged. Copying or disclosing is prohibited.*
>
> On Wed, Mar 4, 2015 at 2:09 PM, dgomesbr <di...@bemobi.com.br>
> wrote:
>
>> Hey there, I'm currently puzzled by how maxConcurrentConsumers set in
>> different points may have different behaviors (or not, I might be doing
>> something wrong).According the documentation:
>> http://camel.apache.org/jms.html*You can configure this option in one of
>> the
>> following ways:On the JmsComponent,On the endpoint URI or,By invoking
>> setConcurrentConsumers() directly on the JmsEndpoint.*Whenever I do it via
>> DSL:https://gist.github.com/dgomesbr/17f029c9a649ce6656f4The activemq
>> queue,
>> shows only the max consumers set for the endpoint correctly, in this case
>> 15.but when I explicitly set the maxConsumers as the parameter on the
>> route
>> "?MaxConcurre...", the maxConcurrent consumers is now the sum of the
>> machines where the camelcontext is deployed, in this example 3 x 15 =
>> 45.Could someone elaborate on that or point me where the implementation
>> varies per local where the configuration is made?Thanks!
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
Re: Diff between configuring maxConcurrentConsumers in JMSComponent,
Route URI or per JMSEndpoint
Posted by Diego Magalhaes <di...@bemobi.com.br>.
Hmmm... the message went all broken.
Hey there,
I'm currently puzzled by how maxConcurrentConsumers set in different
points may have different behaviors (or not, I might be doing something
wrong).
According the documentation: http://camel.apache.org/jms.html
*You can configure this option in one of the following ways: On the
JmsComponent, On the endpoint URI or, By invoking setConcurrentConsumers()
directly on the JmsEndpoint.*
Whenever I do it via DSL:
https://gist.github.com/dgomesbr/17f029c9a649ce6656f4
The activemq queue, shows only the max consumers set for the endpoint
correctly, in this case 15.
but when I explicitly set the maxConsumers as the parameter on the route
"?MaxConcurre...", the maxConcurrent consumers is now the sum of the
machines where the camelcontext is deployed, in this example 3 x 15 = 45.
Could someone elaborate on that or point me where the implementation varies
per local where the configuration is made?
Thanks!
Atenciosamente,
*Diego Magalhães*
Gerencia de Desenvolvimento
Diretoria de tecnologia da Informação
[image: email_assinatura.jpg]
+55 (21) 3529-9019
*www.bemobi.com.br <http://www.bemobi.com.br/>**þ*Antes de imprimir, pense
em sua responsabilidade e compromisso com o Meio Ambiente.
*O conteúdo desta mensagem é confidencial e pode ser privilegiado. *
*É vedada a sua cópia ou divulgação.The contents of this message are
confidential and may be privileged. Copying or disclosing is prohibited.*
On Wed, Mar 4, 2015 at 2:09 PM, dgomesbr <di...@bemobi.com.br>
wrote:
> Hey there, I'm currently puzzled by how maxConcurrentConsumers set in
> different points may have different behaviors (or not, I might be doing
> something wrong).According the documentation:
> http://camel.apache.org/jms.html*You can configure this option in one of
> the
> following ways:On the JmsComponent,On the endpoint URI or,By invoking
> setConcurrentConsumers() directly on the JmsEndpoint.*Whenever I do it via
> DSL:https://gist.github.com/dgomesbr/17f029c9a649ce6656f4The activemq
> queue,
> shows only the max consumers set for the endpoint correctly, in this case
> 15.but when I explicitly set the maxConsumers as the parameter on the route
> "?MaxConcurre...", the maxConcurrent consumers is now the sum of the
> machines where the camelcontext is deployed, in this example 3 x 15 =
> 45.Could someone elaborate on that or point me where the implementation
> varies per local where the configuration is made?Thanks!
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Diff-between-configuring-maxConcurrentConsumers-in-JMSComponent-Route-URI-or-per-JMSEndpoint-tp5763599.html
> Sent from the Camel - Users mailing list archive at Nabble.com.