You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "Marcel Offermans (JIRA)" <ji...@apache.org> on 2012/10/29 15:36:12 UTC
[jira] [Created] (ACE-296) ACE log contains stack trace from its
nodelauncher component
Marcel Offermans created ACE-296:
------------------------------------
Summary: 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
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
[jira] [Assigned] (ACE-296) ACE log contains stack trace from its
nodelauncher component
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans reassigned ACE-296:
------------------------------------
Assignee: Marcel Offermans
> 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
>
> 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
[jira] [Resolved] (ACE-296) ACE log contains stack trace from its
nodelauncher component
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans resolved ACE-296.
----------------------------------
Resolution: Fixed
Just committed a fix for this.
> 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
>
> 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