Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sat, 25 Jun 2011 12:06:47 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <1350632734.40322.1309003607411.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2009471385.40204.1308995447428.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CAMEL-4153) Allow seda consumers to be
 suspended/resumed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CAMEL-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-4153.
--------------------------------

    Resolution: Fixed

> Allow seda consumers to be suspended/resumed
> --------------------------------------------
>
>                 Key: CAMEL-4153
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4153
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.8.0
>
>
> We should allow seda consumers to be suspended/resumed which may be a more gentle way instead of using start/stop. The reason is that start/stop creates/shutdown thread pools etc. And you may not want to do that. Instead you may prefer to just have the consumer not poll in new exchanges from the seda queue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira