Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sat, 1 Mar 2014 06:57:19 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12698063.1393634533223.129783.1393657039511@arcas>
In-Reply-To: <JIRA.12698063.1393634533223@arcas>
References: <JIRA.12698063.1393634533223@arcas>
Subject: [jira] [Commented] (CAMEL-7259) ProducerTemplate is not aligned
 with the lifecycle of CamelContext and therefore it's possible to have a
 Producer that's never shutdown correctly.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-7259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916965#comment-13916965 ] 

Claus Ibsen commented on CAMEL-7259:
------------------------------------

If you want Camel to stop the template when you stop CamelContext, then use the addService API on CamelContext.

> ProducerTemplate is not aligned with the lifecycle of CamelContext and therefore it's possible to have a Producer that's never shutdown correctly.
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7259
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7259
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.12.3
>            Reporter: Aaron Whiteside
>            Priority: Minor
>             Fix For: 2.13.0
>
>
> ProducerTemplate is not aligned with the lifecycle of CamelContext and therefore it's possible to have a Producer that's never shutdown correctly.
> {code}
>         context.start();
>         ProducerTemplate template = context.createProducerTemplate();
>         template.sendBody("test://test", "Hello");
>         context.stop();
> {code}
> If I never call template.stop() the Producer for the test component (or indeed any other component in it's place) will never receive a call to doStop. But the Endpoint that the Producer is associated with will be stopped.. which is a weird situation/state to be in..?
> context.stop() should cleanup any and all Producers, even those created by a ProducerTemplate.. after such time a ProducerTemplate should become invalid and perhaps throw an exception that the camel context has been shutdown?


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)