[
https://issues.apache.org/jira/browse/KARAF-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved KARAF-3513.
---------------------------------
Resolution: Fixed
Fix Version/s: 3.0.4
2.4.2
4.0.0
commit fix
http://git-wip-us.apache.org/repos/asf/karaf/commit/330b7ca1 for karaf-2.x
branch
http://git-wip-us.apache.org/repos/asf/karaf/commit/23d6d1d6 for karaf-3.0.x
branch
http://git-wip-us.apache.org/repos/asf/karaf/commit/141bf0c9 for master
> JMXConnectorServer should be able to pick up the new KeystoreInstance
> available in container
> --------------------------------------------------------------------------------------------
>
> Key: KARAF-3513
> URL: https://issues.apache.org/jira/browse/KARAF-3513
> Project: Karaf
> Issue Type: Improvement
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 4.0.0, 2.4.2, 3.0.4
>
>
> when we configure the JMX Connector with SSL enabled, if there's no valid
> keystore available in the first place when start the "Apache Karaf ::
> Management" bundle, that bundle can't pick up any KeystoreInstance available
> afterwards.
> For an instance, if we drop a keystore.xml file like
> {code}
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";
> xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0";>
> <jaas:keystore name="sample_keystore"
> rank="1"
> path="..."
> keystorePassword="..."
> keyPasswords="..." />
> </blueprint>
> {code}
> into etc folder after we start karaf, a bundle created accordingly and a
> KeystoreInstance get published, however, the JMX Connector won't be able to
> pick up this new KeystoreInstance, unless we manually refresh "Apache Karaf
> :: Management" bundle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
