Mailing-List: contact commits-help@ace.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ace.apache.org
Date: Mon, 27 May 2013 07:45:48 +0000 (UTC)
From: "Bram de Kruijff (JIRA)" <jira@apache.org>
To: commits@ace.apache.org
Message-ID: <JIRA.12613901.1351521348302.25203.1369640748730@arcas>
In-Reply-To: <JIRA.12613901.1351521348302@arcas>
References: <JIRA.12613901.1351521348302@arcas>
Subject: [jira] [Closed] (ACE-296) ACE log contains stack trace from its
 nodelauncher component
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bram de Kruijff closed ACE-296.
-------------------------------

    Fix Version/s: 1.0.0
       Resolution: Fixed

Bulk update to fix version 1.0
                
> ACE log contains stack trace from its nodelauncher component
> ------------------------------------------------------------
>
>                 Key: ACE-296
>                 URL: https://issues.apache.org/jira/browse/ACE-296
>             Project: ACE
>          Issue Type: Improvement
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>             Fix For: 1.0.0
>
>
> As the node launcher in ACE (used when you use ACE in a cloud) does come with a configuration, but this configuration has some placeholders, ConfigurationAdmin does try to deliver the configuration to this component, and it will start, but not work. Instead, let's not provide a configuration at all, which means this stack trace will go away as the component will no longer start.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira