You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Hao Zhong (JIRA)" <ji...@apache.org> on 2017/10/12 00:32:00 UTC
[jira] [Created] (ARIES-1747) A potential error in
BundleFrameworkConfigurationFactoryImpl or BundleFrameworkManagerImpl
Hao Zhong created ARIES-1747:
--------------------------------
Summary: A potential error in BundleFrameworkConfigurationFactoryImpl or BundleFrameworkManagerImpl
Key: ARIES-1747
URL: https://issues.apache.org/jira/browse/ARIES-1747
Project: Aries
Issue Type: Bug
Reporter: Hao Zhong
I notice that the BundleFrameworkConfigurationFactoryImpl_createBundleFrameworkConfig method has the following code:
{code:java}
Properties frameworkConfig = new Properties();
// Problems occur if the parent framework has osgi.console set because the child framework
// will also attempt to listen on the same port which will cause port clashs. Setting this
// to null essentially turns the console off.
frameworkConfig.put("osgi.console", "none");
{code}
A previous version of the BundleFrameworkManagerImpl_isolatedInstall method calls similar APIs:
{code:java}
Properties frameworkConfig = new Properties();
frameworkConfig.put("osgi.console", "0");
{code}
However, in a bug fix (https://issues.apache.org/jira/browse/ARIES-453), the above code was modified to:
{code:java}
Properties frameworkConfig = new Properties();
{code}
Please recheck whether calling or not calling frameworkConfig.put("osgi.console", "0") can introduce bugs in this context.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)