ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bram de Kruijff (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (ACE-296) ACE log contains stack trace from its nodelauncher component
Date Mon, 27 May 2013 07:40:52 GMT

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

Bram de Kruijff reopened ACE-296:
---------------------------------

    
> 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

Mime
View raw message