You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Gaurav Sehgal <ga...@yahoo.com> on 2013/09/03 12:08:13 UTC
SEDA queue in Camel blocks.
Hi,
I am using Camel's implementation of SEDA queue inside JBOSS FUSE; though at times the consumer does not get all the messages and when I restart the camel context the messages seem to flow through. This seems like the messages are blocked for some reason and the consumer is not processing them. Also; the load on the queue is not very large; I tested this with payload 80 messages.
Has anyone expreienced this issue and if so is there any configuration that needs to be done to overcome this?
Cheers!
Gaurav
Re: SEDA queue in Camel blocks.
Posted by Raul Kripalani <ra...@evosent.com>.
Is it possible that one of your beans is blocking for some reason, and all
of your 6 concurrent consumers become occupied waiting at the blocking
point?
When you restart your context, do you see any log statements about inflight
exchanges?
Regards,
Raúl.
On 5 Sep 2013 13:59, "Gaurav Sehgal" <ga...@yahoo.com> wrote:
> Hi Christina;
> This does not happen everytime; though it happens
> preodically; will post the thread dump once I see it.
>
> Though; I am posting the camel routes I use in my application:
>
> context.addRoutes(new RouteBuilder() {
> public void configure() {
> from("vm:interactions?concurrentConsumers=6")
>
> .bean(interProcessing,"processInteraction")
> .multicast()
> .parallelProcessing()
> .to("direct:index")
> .to("direct:cassandra")
> .to("direct:blobStore")
> .end()
>
> .bean(delTempStorage,"processTempStorage");
> }
> });
>
> context.addRoutes(new RouteBuilder() {
> public void configure() {
> from("direct:index").threads(5).
> bean(indexProcessor,
> "processIndexStore");
> }
> });
>
> context.addRoutes(new RouteBuilder() {
> public void configure() {
> from("direct:cassandra").threads(5)
> .bean(cassandraProcessing,
> "processCassandraStore");
> }
> });
>
> context.addRoutes(new RouteBuilder() {
> public void configure() {
> from("direct:blobStore").threads(5)
> .bean(blobStoreProcessing,
> "processBlobStore");
> }
> });
>
>
> Cheers!
> Gaurav
>
>
>
> ________________________________
> From: Christian Posta <ch...@gmail.com>
> To: "users@camel.apache.org" <us...@camel.apache.org>; Gaurav Sehgal <
> gaurav_sehgal@yahoo.com>
> Sent: Tuesday, September 3, 2013 7:18 PM
> Subject: Re: SEDA queue in Camel blocks.
>
>
>
> I've never seen something like that. What does your route look like (ie,
> what other endpoints are after the seda endpoints? how many consumers do
> you have for the seda endpoints?).
>
> Your best bet is to recreate this and take a thread dump. Or recreate it
> and post it as a test here.
>
>
>
> On Tue, Sep 3, 2013 at 3:08 AM, Gaurav Sehgal <ga...@yahoo.com>
> wrote:
>
> Hi,
> > I am using Camel's implementation of SEDA queue inside JBOSS FUSE;
> though at times the consumer does not get all the messages and when I
> restart the camel context the messages seem to flow through. This seems
> like the messages are blocked for some reason and the consumer is not
> processing them. Also; the load on the queue is not very large; I tested
> this with payload 80 messages.
> >
> > Has anyone expreienced this issue and if so is there any configuration
> that needs to be done to overcome this?
> >
> >Cheers!
> >Gaurav
> >
>
>
> --
> Christian Posta
>
> http://www.christianposta.com/blog
> twitter: @christianposta
Re: SEDA queue in Camel blocks.
Posted by Gaurav Sehgal <ga...@yahoo.com>.
I got the thread dump; and there seem to be a lot of waiting threads; though I am not sure if that is the reason for the queue not processing the messages. Can you please give me some pointers to look for in the thread dump.
________________________________
From: Christian Posta <ch...@gmail.com>
To: Gaurav Sehgal <ga...@yahoo.com>
Sent: Thursday, September 5, 2013 9:39 PM
Subject: Re: SEDA queue in Camel blocks.
Yah best bet is to get a thread dump. I wonder if any of the beans downstream are blocking the threads that the seda consumers use.
On Thu, Sep 5, 2013 at 5:58 AM, Gaurav Sehgal <ga...@yahoo.com> wrote:
Hi Christina;
> This does not happen everytime; though it happens preodically; will post the thread dump once I see it.
>
>
>Though; I am posting the camel routes I use in my application:
>
>
> context.addRoutes(new RouteBuilder() {
>public void configure() {
> from("vm:interactions?concurrentConsumers=6")
>
>.bean(interProcessing,"processInteraction")
>.multicast()
>.parallelProcessing()
>.to("direct:index")
>.to("direct:cassandra")
>.to("direct:blobStore")
>.end()
>
>.bean(delTempStorage,"processTempStorage");
>}
>});
>
>
>context.addRoutes(new RouteBuilder() {
>public void configure() {
>from("direct:index").threads(5).
> bean(indexProcessor, "processIndexStore");
>}
>});
>
>
>context.addRoutes(new RouteBuilder() {
>public void configure() {
>from("direct:cassandra").threads(5)
> .bean(cassandraProcessing, "processCassandraStore");
>}
>});
>
>
>context.addRoutes(new RouteBuilder() {
>public void configure() {
>from("direct:blobStore").threads(5)
> .bean(blobStoreProcessing, "processBlobStore");
>}
>});
>
>
>
>
>Cheers!Gaurav
>
>
>
>
>
>________________________________
> From: Christian Posta <ch...@gmail.com>
>To: "users@camel.apache.org" <us...@camel.apache.org>; Gaurav Sehgal <ga...@yahoo.com>
>Sent: Tuesday, September 3, 2013 7:18 PM
>Subject: Re: SEDA queue in Camel blocks.
>
>
>
>I've never seen something like that. What does your route look like (ie, what other endpoints are after the seda endpoints? how many consumers do you have for the seda endpoints?).
>
>
>Your best bet is to recreate this and take a thread dump. Or recreate it and post it as a test here.
>
>
>
>On Tue, Sep 3, 2013 at 3:08 AM, Gaurav Sehgal <ga...@yahoo.com> wrote:
>
>Hi,
>> I am using Camel's implementation of SEDA queue inside JBOSS FUSE; though at times the consumer does not get all the messages and when I restart the camel context the messages seem to flow through. This seems like the messages are blocked for some reason and the consumer is not processing them. Also; the load on the queue is not very large; I tested this with payload 80 messages.
>>
>> Has anyone expreienced this issue and if so is there any configuration that needs to be done to overcome this?
>>
>>Cheers!
>>Gaurav
>>
>
>
>
>--
>Christian Posta
>
>http://www.christianposta.com/blog
>twitter: @christianposta
>
>
--
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta
Re: SEDA queue in Camel blocks.
Posted by Gaurav Sehgal <ga...@yahoo.com>.
Hi Christina;
This does not happen everytime; though it happens preodically; will post the thread dump once I see it.
Though; I am posting the camel routes I use in my application:
context.addRoutes(new RouteBuilder() {
public void configure() {
from("vm:interactions?concurrentConsumers=6")
.bean(interProcessing,"processInteraction")
.multicast()
.parallelProcessing()
.to("direct:index")
.to("direct:cassandra")
.to("direct:blobStore")
.end()
.bean(delTempStorage,"processTempStorage");
}
});
context.addRoutes(new RouteBuilder() {
public void configure() {
from("direct:index").threads(5).
bean(indexProcessor, "processIndexStore");
}
});
context.addRoutes(new RouteBuilder() {
public void configure() {
from("direct:cassandra").threads(5)
.bean(cassandraProcessing, "processCassandraStore");
}
});
context.addRoutes(new RouteBuilder() {
public void configure() {
from("direct:blobStore").threads(5)
.bean(blobStoreProcessing, "processBlobStore");
}
});
Cheers!
Gaurav
________________________________
From: Christian Posta <ch...@gmail.com>
To: "users@camel.apache.org" <us...@camel.apache.org>; Gaurav Sehgal <ga...@yahoo.com>
Sent: Tuesday, September 3, 2013 7:18 PM
Subject: Re: SEDA queue in Camel blocks.
I've never seen something like that. What does your route look like (ie, what other endpoints are after the seda endpoints? how many consumers do you have for the seda endpoints?).
Your best bet is to recreate this and take a thread dump. Or recreate it and post it as a test here.
On Tue, Sep 3, 2013 at 3:08 AM, Gaurav Sehgal <ga...@yahoo.com> wrote:
Hi,
> I am using Camel's implementation of SEDA queue inside JBOSS FUSE; though at times the consumer does not get all the messages and when I restart the camel context the messages seem to flow through. This seems like the messages are blocked for some reason and the consumer is not processing them. Also; the load on the queue is not very large; I tested this with payload 80 messages.
>
> Has anyone expreienced this issue and if so is there any configuration that needs to be done to overcome this?
>
>Cheers!
>Gaurav
>
--
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta
Re: SEDA queue in Camel blocks.
Posted by Christian Posta <ch...@gmail.com>.
I've never seen something like that. What does your route look like (ie,
what other endpoints are after the seda endpoints? how many consumers do
you have for the seda endpoints?).
Your best bet is to recreate this and take a thread dump. Or recreate it
and post it as a test here.
On Tue, Sep 3, 2013 at 3:08 AM, Gaurav Sehgal <ga...@yahoo.com>wrote:
> Hi,
> I am using Camel's implementation of SEDA queue inside JBOSS FUSE;
> though at times the consumer does not get all the messages and when I
> restart the camel context the messages seem to flow through. This seems
> like the messages are blocked for some reason and the consumer is not
> processing them. Also; the load on the queue is not very large; I tested
> this with payload 80 messages.
>
> Has anyone expreienced this issue and if so is there any configuration
> that needs to be done to overcome this?
>
> Cheers!
> Gaurav
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta