Return-Path: X-Original-To: apmail-brooklyn-dev-archive@minotaur.apache.org Delivered-To: apmail-brooklyn-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 70C9918C28 for ; Wed, 23 Dec 2015 10:29:50 +0000 (UTC) Received: (qmail 14513 invoked by uid 500); 23 Dec 2015 10:29:47 -0000 Delivered-To: apmail-brooklyn-dev-archive@brooklyn.apache.org Received: (qmail 14462 invoked by uid 500); 23 Dec 2015 10:29:47 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 14406 invoked by uid 99); 23 Dec 2015 10:29:47 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Dec 2015 10:29:47 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CC90C2C1F5C for ; Wed, 23 Dec 2015 10:29:46 +0000 (UTC) Date: Wed, 23 Dec 2015 10:29:46 +0000 (UTC) From: "Graeme Miller (JIRA)" To: dev@brooklyn.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (BROOKLYN-208) Config resolution on shutdown MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/BROOKLYN-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069487#comment-15069487 ] Graeme Miller commented on BROOKLYN-208: ---------------------------------------- Thanks Sam. Before Mikes change, this issue was slightly different, in that the application would hang forever and never shut down. Now the app will shutdown, but somewhat ungracefully. > Config resolution on shutdown > ----------------------------- > > Key: BROOKLYN-208 > URL: https://issues.apache.org/jira/browse/BROOKLYN-208 > Project: Brooklyn > Issue Type: Bug > Affects Versions: 0.9.0 > Reporter: Graeme Miller > Priority: Minor > > Consider a blueprint that has two entities, Entity1 and Entity2. Entity1 has a brooklyn.config value Conf1. Entity2 has a brookyln.config value Conf2, which uses attributeWhenReady to get the value of Conf1. > When Entity2 is shutting down, it attempts to get Conf2 (for example because it is a 'shell.env' parameter). Brooklyn then creates a task to get the value of Conf1 to populate it, however, Entity1 has already shutdown. Entity2 now waits for the value until a timeout and then cancels resolving Conf2. > To fix this situation, I would like to suggest that config values should be immutable, I.E. should be resolved once before the entity starts and never again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)